Trying to update Avast, manually, for the 081215-1 update to get rid of that pesky ‘suspicious file suspected’ alert.
I thought I had it downloaded last night, but this morning when I checked the version (‘about Avast’), it reverted back to -0. ?? It’s not updating automatically and I have no idea why.
I’m right-clicking, hitting updating, then VPS. Why won’t the update stay on my computer? The update ‘does not’ show in the ‘about Avast’ or in the ‘notice log’…only on the screen immediately after the update. Any advice? I’d really appreciate any help.
Try a repair of avast. Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow. Then try a manual update again.
What OS are you using ?
Though it shouldn’t matter for the VPS update, are you running an account with administrator privileges ?
I don’t know what you are talking about Tech, we are talking about a VPS update here and what for whatever reason appears to be a failure of the update.
So that isn’t the fault of the actual VPS update but the update process, I had no problem with the 081215-1 vps update, along with many, many, thousands of others.
So before we jump to any conclusions we need feedback from the original poster.
Of course I read the first post which is why I responded to your post as this has nothing to do with what went on previously ‘Can’t update Avast VPS’ nothing other than that. I’m trying to find why the update failed, I’m not concerned with why the update was required.
You said “Man… this latest vps update bring nothing than troubles…” and I see very little to show there is a problem with the 081215-1 vps update (only this topic and we have to wait for more information) or the contents of a previous vps update that made this -1 release necessary.
Nothing about what you can or can’t post, I just don’t see these problems with 081215-1 vps update that you mention ?
So nothing wrong with the update then, no troubles brought by this update, other than your bored with it. A bit hard to read between the lines when there is only one line.
Just wanted to let all that replied know that I’ve been off this computer all day. Just turned it on and it ‘did’ automatically update. Yay!!! No more ‘suspicious file’ alerts. (I’m using Windows XP Home Edition Service Pack 2…worried about updating.)
The funny thing is (and I’m certainly not complaining) the update totally skipped the 081215-1 update. It’s still not on the log. It went straight to the 081216-0 update. But at least my computer seems to be OK now. Hope everyone else is having good luck, too.
Thanks for the replies…sorry it turned out the thread got a little ‘heated’.
The auto updates function checks what vps version have and what the latest version is and downloads those that you don’t have, so it didn’t actually skip 081215-1, it just reports what you had before the update and what you have now.
Tech I keep up with what is going on in the forums and I simply didn’t see any problems with not being able to install the 081215-1 vps update (other than this one, which I believe had nothing to do with 081215-1, just a hiccup with the update process) and that is why I said so.
After having had the Rootkit FP problem, I re-installed Avast. So, I am now running 4.8.1296. Updating VPS seems to work fine (see log content), however the “About Avast” screen as well as the residentprotection.txt file indicate it is still working with VPS version 081204-0. I have tried uninstall / re-install and also repair from control panel-add/remove progarms, but with no result.
I am logged on as administrator
OS = XP Pro SP3
Is there anything that I can do ? Everything had worked fine with the version previous to 4.8.1296.
Thank you for your help.
You seem to have tried everything but a manual update (right click the avast ‘a’ icon, select Updating, iAVS Update).
An uninstall/reinstall would only bribg the VPS that was contained in the installation file, which could be out of date. A Repair would only fix any problem with say a corrupt or missing file, but not the version of the VPS.
Though the avast_log.txt file you attached shows 081218-0 completed. Interestingly I didn’t have that version of the VPS so I did a manual update and it completed successfully and is reported in about avast. Though you shouldn’t need to have you rebooted since the VPS update ?
Thank you for your quick reply, DavidR.
Sorry, I forgot yo mention that I also tried the manual update, which I tried again 1 minute ago to make sure I had done it and whose result is “VPS alreay up to date”. The other trials (uniinstall/re-install, repair) were mostly as a hope to unlock the situation. I installed 4.8.1296 at the beginning of the week after a fourtnight holiday and because after having received the 081215-0 update with the rootkit FP, I could not install 081215-1, neither automatically nor manually (the current database version remained at 081215-0).
The problem looks as if the place where the “current databse version” is kept could not be updated.
What surprises me is that the Windows Security Center hasn’t had a whinge as the VPS if more than 7 days old would trigger that, so something must be reporting that correctly. So what version of the VPS does the WSC say you have ?
I have in the past seen the repair (I know you tried it) resolve this out of synch version numbers.
