Avast 4.8 update trouble

[PRB]

On a stock system (Win98SE, 1ghz P3, 512mb RAM), if you try to install any of the Avast virus database files that are over 200mb (those from about 2015-10-03 onwards) you get an error message -

 

Can't install VPS update. Please, report following errorcodes:

Ver: 4.8.1368

SI: 0x00000005

ST: 0x00000008

LE: 0x00000000

 

On a system with patchmem and kernelex (WinME, 2.8ghz P4 2gb RAM), the latest update will install but on reboot you'll find that the On-access providers fail to start, leaving Avast useless...

 

NT4, 2000 etc are unaffected.

 

Has anybody found (or can suggest) a workaround to continue updating Avast 4.8 on 9x?

[Commodore]

Just an (maybe) illogical idea. I am wondering if it works also in NT or 2000 or XP with FAT32.

I cannot try it.

[sdfox7]

On a stock system (Win98SE, 1ghz P3, 512mb RAM), if you try to install any of the Avast virus database files that are over 200mb (those from about 2015-10-03 onwards) you get an error message -

 

Can't install VPS update. Please, report following errorcodes:

Ver: 4.8.1368

SI: 0x00000005

ST: 0x00000008

LE: 0x00000000

 

On a system with patchmem and kernelex (WinME, 2.8ghz P4 2gb RAM), the latest update will install but on reboot you'll find that the On-access providers fail to start, leaving Avast useless...

 

NT4, 2000 etc are unaffected.

 

Has anybody found (or can suggest) a workaround to continue updating Avast 4.8 on 9x?

 

Are you using the correct VPS update? Avast 4.x uses a different update module (VPSUPD4.EXE) than 5.x and later (VPSUPD.EXE).

https://www.avast.com/download-update

[schwups]

The automatic and manual vps update of Avast Home 5.1.889 failed on XP SP2 since 29th October, too. Same message: Not enough storage to process this command. I had tested successfully 4.8.1368 on XP SP2 after the 04 October. The update worked. But I suspect that it no longer works now.

[sdfox7]

Avast's website states that "using Microsoft operating systems without the latest service pack may not be supported."

 

Historical web faq shows Avast 8.0 was the first version to push SP3 as a requirement: https://web.archive.org/web/20130818062931/http://www.avast.com/en-us/faq.php?article=AVKB3

 

The previous 7.0 version in 2012 was the last branch requiring a minimum Windows 2000 SP4 and a Pentium 3 with 256MB RAM: https://web.archive.org/web/20120715035726/http://www.avast.com/en-us/pro-antivirus#tab2

 

I certainly can confirm that several updates are needed to get Avast running on Windows 2000: https://forum.avast.com/index.php?topic=94069.msg749148#msg749148.

[PRB]

 

Are you using the correct VPS update? Avast 4.x uses a different update module (VPSUPD4.EXE) than 5.x and later (VPSUPD.EXE).

https://www.avast.com/download-update

 

 

Yes, definitely attempting to use the correct exe.

 

If there's nothing else to be done, I was wondering if it's possible to modify the file that contains the virus definitions (400.vps) by removing the oldest entries, thus bringing the size back under 200mb (assuming that's the limiting factor). I've no idea if that's achievable, though.

 

 

 

I had tested successfully 4.8.1368 on XP SP2 after the 04 October. The update worked. But I suspect that it no longer works now.

 

FWIW, I've just successfully updated NT4 with the latest 4.8.1368 virus database.

Edited November 23, 2015 by PRB

[Commodore]

Same message: Not enough storage to process this command.

Hello Schwups, try this method.

Open the Avast interface and uncheck "enable avast self-defense module" in program settings -> troubleshooting.

Therefore, in the Avast5 setup folder, search the file vps_32-11xx.vpx (about 260MB), rename or put it into the recycle bin, then launch the update.

Please, let me know your results.

[Commodore]

This is interesting!

I just noticed that the actual VPS is again plenty under the critical (and so bloated) threshold of 200 MB. Now is 105,1 MB!!!

https://www.avast.com/download-thank-you.php?product=VPS4&locale=en-ww

[Commodore]

For those interested, Avast update certainly works again!

Last december i unistalled Avast, therefore i could not try before today.

Now, i reinstalled it and, with the last definitions, proceeded a manual update without problems.

Edit: add a screenshot

Edit 2: for the record, also the auto-update is ok, as for patclash

Edited February 8, 2016 by Commodore

[patclash]

Yes , I can confirm ;

I just rerun my old pc that I haven't run since November last Year

(I must first get on new Avast free licence)

I manualy update de vps from 05/02 that I have downloaded with an other pc, then Avast update automatically with today update

[Commodore]

I noticed that the last VPS on my installation is the following: 160331-2. A more recent version seems not avalaible.
Has anyone tried an update of the own definitions after this date on a pc with different OS? I cannot establish if it's about an issue and this depends from windows 98 or the support was dropped for all and the 160331-2 was the last definitive definition for Avast 4.8

[sdfox7]

Please download the 4.8.0 update on Avast's standalone update page, and let me know if this works for you:

Avast Software Updates

The fact that this has not been removed leads me to believe you experiencing a specific issue not related to Avast. Are you using the latest Avast 4.8.1368 installer? http://sdfox7.com/avast/4.x/setupeng.exe

[patclash]

On 04/04/2016 at 2:28 PM, Commodore said:

I noticed that the last VPS on my installation is the following: 160331-2. A more recent version seems not avalaible.
Has anyone tried an update of the own definitions after this date on a pc with different OS? I cannot establish if it's about an issue and this depends from windows 98 or the support was dropped for all and the 160331-2 was the last definitive definition for Avast 4.8

I confirm, I just have the same

On 04/04/2016 at 7:23 PM, sdfox7 said:

Please download the 4.8.0 update on Avast's standalone update page, and let me know if this works for you:

Avast Software Updates

The fact that this has not been removed leads me to believe you experiencing a specific issue not related to Avast. Are you using the latest Avast 4.8.1368 installer? http://sdfox7.com/avast/4.x/setupeng.exe

I have download the vpsud4.exe from the 04/04 et I just download it from today and this is the same file [113 Mo (119 074 336 octets)] than from 31/03;

I run it but it say the vps are uptodate and it is the 160331-2 version

[sdfox7]

Avast 4.8 support was scheduled to end in 2009/2010. Version 5 was released in 2009. This was followed up on in 2011 on the Avast forum, and I quoted this 5 years ago in another forum as well.

This version has been on borrowed time for several years now. Anything beyond that is something to be grateful for

https://forum.avast.com/index.php?topic=69329.0

Avast Free 4.8 is Updating Past End of Support Deadline

Edited April 6, 2016 by sdfox7
correct second embedded link which was repeated

[Commodore]

Hello, thanks to both of you. Sdfox7, i'm also sorry for the delay in replying.

I cannot download the full defs, because in this days i have only a connection too slow for a big download like this.
But i just started the download four days ago, and the browswer shows me a total size of 119.074.336 bytes. Now, trying again, it's still unchanged.

This version has been on borrowed time for several years now. Anything beyond that is something to be grateful for

Yes, you are right.
The last reference (that i founded) talked about april 2013.
http://www.msfn.org/board/topic/162132-good-firewallantivirus-for-win98/#comment-1032019
Three extra years have been a good gift! Perhaps this could be the right time... except new surprises like for the 200 MB trouble Edited April 7, 2016 by Commodore
link and quote error