Windows 7 Ultimate 64Bit: manual update does not work since Dec 16th.

[PMaff]

I tried manual update from today at
http://www.avast.com/download-update
"avast! 5 & 6 series VPS update, size 31MB"
md5sum of update file: 5b42c5301af3c71357441d877c2b6a3a
but Avast only says that the last successful update
was Dec 16th.
Reboot did not change that.
I am using 6.0.1367 on windows 7 Ulitmate 64 Bit.

Tried uninstall and got that "setiface error has occured:2"
but was able to uninstall and reinstall 6.0.1367.
Installed manual updates from Dec 16th and today and still Avast says that
the last update was Dec 16th.
Update file from Dec 16th has md5sum :  8c160d30c01b2bd5b199ba6bf104c13e
 
What is going on here?

[PMaff]

I also tried the manual update from yesterday on a
XP SP3 machine and got:


Any ideas?

[Lisandro]

Are you in an offline computer?
The manual updates suffer a bug in December. Maybe it's not completely solve (yet).
Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair).

[PMaff]

Are you in an offline computer?
The manual updates suffer a bug in December. Maybe it's not completely solve (yet).
Can you try to repair your installation?
Go to Control Panel > Add/Remove programs > avast! antivirus > Remove. Then choose Repair function in the popup window (Repair).

For various reasons I am currently offline with both machines.
I tried the repair already with the Win 7 installation (I wrote that in my
previous posting). That did not help.

It looks like the manual update (avupdate-files or 6.0.1367)
are buggy, at least since Dec 16th.
I hope the Avast people take care of that otherwise I will have to
take another AV solution when my Avast abo ends next month.

[Lisandro]

It looks like the manual update (avupdate-files or 6.0.1367)
are buggy, at least since Dec 16th.

Yes, the offline updater suffered from a bug and, maybe, it's not fully solved (yet).

[ady4um]

I tried the repair already with the Win 7 installation (I wrote that in my
previous posting). That did not help.

Just to make it clear, you need to reboot after the repair before testing or getting to any conclusions.

It looks like the manual update (avupdate-files or 6.0.1367)
are buggy, at least since Dec 16th.

I also tried the manual update from yesterday on a XP SP3 machine

Have you tried downloading a more recent full VPS from the official site http://www.avast.com/download-update? I mean, yesterday's VPS failed, but maybe a new VPS could be working correctly.

There are other few reports that the VPS are failing again, but downloading a newer VPS from the official site should be also part of the tests. Please delete the browser's cache before you download the file, and reboot before applying (running) it.

[PMaff]

I tried the repair already with the Win 7 installation (I wrote that in my
previous posting). That did not help.

Just to make it clear, you need to reboot after the repair before testing or getting to any conclusions.

It looks like the manual update (avupdate-files or 6.0.1367)
are buggy, at least since Dec 16th.

I also tried the manual update from yesterday on a XP SP3 machine

Have you tried downloading a more recent full VPS from the official site http://www.avast.com/download-update? I mean, yesterday's VPS failed, but maybe a new VPS could be working correctly.

There are other few reports that the VPS are failing again, but downloading a newer VPS from the official site should be also part of the tests. Please delete the browser's cache before you download the file, and reboot before applying (running) it.

I always reboot after uninstalling or installing any AV software.
I also rebooted this time after reinstall and before installing new updates manually.


I tried the current vpsupd.exe with md5
c7d3d9581c644053bf5bc9b9a3dc91e5
The XP machine gives an error (see above).
The Win 7 Ultimate machine does not give an error but Avast still says
that the last update is from Dec 16th and that all is ok.

[ady4um]

Several different comments.

First, please stop using the "quote" when unnecessary.

I mentioned the reboot for the repair action, since many users simply report "it doesn't work" but they forget to reboot after the repair. If you indeed rebooted after the repair (which is similar but not exactly the same as an installation), then we move on.

About the MD5, it is not necessary for use. We are all common users trying to help, and the MD5 is not officially published.

The picture you posted is not in English, so the exact error message is not understandable for me.

There is a simple way to be sure the download itself is not corrupted, which is the first step even before trying to apply the update. Just like with the MD5, instead use the valid certificate.

Select the vps installer file, right click -> properties -> digital signatures. Is the valid signature of avast there? Review the dates, both in the certificate and in the properties.

Only if the data in those places is valid, then the download is valid.

About the date of the current definitions in your avast, if you are not able to apply updates since 2011DEC16, then that's the date avast would report to you.

If I understood correctly, you can't perform a normal on-line update in this same system, so if the VPS has a valid certificate with a valid date but it still can't be applied (and you OS is working correctly), then only some Avast Team member has to answer if indeed the full VPS for off-line updates is working correctly or not.

[Lisandro]

PMaff, please, upload (attach) the avast log:
C:\ProgramData\AVAST Software\Avast\log\Setup.log
or C:\Program Files\Alwil Software\Avast5\Setup\setup.log

If the file is too big for the forum, post the last 400-500 lines of it.

[PMaff]

@quote: I simply used the "Quote" button of the forum in the above case.
        If that is wrong, then the "Quote" button does something wrong.
        I left away the quote this time to be sure.

@md5: ok, it was just me trying to help, simply forget it.

@signature: checked the signature for the update from Dec 29th and it seems to be ok.
The vpsupd.exe from yesterday also did not work.

@reboot: I rebooted after uninstall and after install. I did not repair!

Yesterday I tried repair and this did not work with 6.0.1367.
So I uninstalled 6.0.1367,
rebootet,
installed an older version that was ok: 6.0.1289.
Rebooted.
Installed the vpsupd.exe from Dec 16th, all was ok.
Then I installed 6.0.1367,
rebooted.
Installed vpsupd.exe from Dec 16th.
Rebooted just to be on the safe side.
Now version 6.0.1367 showed me that the update from Dec 16th is too old (red)
which was not shown before!
But 6.0.1367 said that my computer is safe. 
I tried to install the vpsupd.exe from Dec 18th and I got the following error:


Today I tried repair with 6.0.1367 and this time it worked.
Now vpsupd.exe from Dec 16th is shown as ok=green. (?)

If I try the update vpsupd.exe from Dec 29th nothing happens.
Same thing for todays vpsupd.exe.

[ady4um]

If I try the update vpsupd.exe from Dec 29th nothing happens.
Same thing for todays vpsupd.exe.

So, to summarize, for the VPS of 2011DEC18, it shows you the above error, and the current VPS 2011DEC29 shows you nothing, but it doesn't apply the update either.

AVAST TEAM NEEDS TO GET INVOLVED!!!

[PMaff]

PMaff, please, upload (attach) the avast log:
C:\ProgramData\AVAST Software\Avast\log\Setup.log
or C:\Program Files\Alwil Software\Avast5\Setup\setup.log

If the file is too big for the forum, post the last 400-500 lines of it.

I take the last items from today

[ady4um]

Using Windows Vista: install SP2!!!! (and other Windows Updates).

[PMaff]

Using Windows Vista: install SP2!!!! (and other Windows Updates).

It is Windows 7 Ultimate SP1 with some updates:


Maybe Avast does not recognize the correct Windows version?

[ady4um]

Maybe Avast does not recognize the correct Windows version?

I don't know. The setup should identify the correct Windows version, since according to the Windows version avast behaves differently (some features are exclusive for Windows Seven, for example).

Pleas open a cmd prompt and run "ver". Which exact version do you get?

(Note that it is still possible that the full VPS is failing anyway, and this might be an additional issue.)