Support of avast! 4.8 is being discontinued, as we all know. However, on some (early Pentium 4 and older Pentium III) computers, particularly those that only run a specific task, we don’t want (or need) to upgrade to avast! 5 (which may slow down these older machines).
Finally, after some searching we found that the process asw5Noti.exe or awsw5Not2.exe was running whenever the annoying avast! upgrade notification pop-up is on the screen.
In order to rename these files and disable them from popping up, go into the avast! Program Settings (located in the System Tray icon)
select the Troubleshooting tab
and check “Disable avast! self defense mode”
click OK and you may be prompted with a confirmation screen:
click YES.
Now open up a “Command Prompt” window and type the following:
cd “%ProgramFiles%\Alwil Software\Avast4″
ren asw5Not?.exe *.exe.DISABLED
If you do not get any errors, then the files were successfully renamed; effectively disabled.
You should then turn back on the “avast! self defense mode” by removing the check you did in the steps above.
Hope this helps everyone who is using an older computer and does not want to be continually annoyed by the avast! upgrade notification screen.
NOTE: on faster computers, it is strongly recommended that you upgrade to avast! 5 for complete protection.
.
©2012 Johnny Chin. All Rights Reserved.
Support of avast! 4.8 is being discontinued, as we all know. However, on some (early Pentium 4 and older Pentium III) computers, particularly those that only run a specific task, we don’t want (or need) to upgrade to avast! 5 (which may slow down these older machines).
Finally, after some searching we found that the process asw5Noti.exe or awsw5Not2.exe was running whenever the annoying avast! upgrade notification pop-up is on the screen.
In order to rename these files and disable them from popping up, go into the avast! Program Settings (located in the System Tray icon)
select the Troubleshooting tab
and check “Disable avast! self defense mode”
click OK and you may be prompted with a confirmation screen:
click YES.
Now open up a “Command Prompt” window and type the following:
cd “%ProgramFiles%\Alwil Software\Avast4″
ren asw5Not?.exe *.exe.DISABLED
If you do not get any errors, then the files were successfully renamed; effectively disabled.
You should then turn back on the “avast! self defense mode” by removing the check you did in the steps above.
Hope this helps everyone who is using an older computer and does not want to be continually annoyed by the avast! upgrade notification screen.
NOTE: on faster computers, it is strongly recommended that you upgrade to avast! 5 for complete protection.
.
Avast tonight released their updated VPS 091203-0 signature file which has been causing a lot of grief to everyone around the world with false-positives for the trojan/worm Win32:Delf-MZG[Trj].
The only fix for now is to disable updates and go back to a previous signature file that is not “bad”.
Luckily I have another machine which has not yet taken down this update, so I saved the 400.vps file from C:\Program Files\Alwil Software\Avast4\DATA into my USB key. I then copied this older version of the 400.vps file onto the computer with bad 091203-0 VPS signature file. I placed it into C:\ for easy access later (because we will be using the Command Prompt, so everything would be typed).
Now on the computer with the bad VPS signature file,
disable the Avast updates by setting it to “Manual”.
Reboot the computer (assuming Windows XP) into
and type the following:
cd “C:\Program Files\Alwil Software\Avast4\DATA”
ren 400.vps 400.vps.091203-0.bad
copy C:\400.vps
(this is why I recommended putting it in C:\ above, less typing)
Then reboot the computer back to Normal mode.
Your Avast VPS signatures should now be reverted to the older version.
Good luck!
Update: December 3, 2009 8:25AM EST
Avast released an updated signature file (VPS 091203-1) that is suppose to resolve the bug. Goto http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=377
.
©2012 Johnny Chin. All Rights Reserved.
Avast tonight released their updated VPS 091203-0 signature file which has been causing a lot of grief to everyone around the world with false-positives for the trojan/worm Win32:Delf-MZG[Trj].
The only fix for now is to disable updates and go back to a previous signature file that is not “bad”.
Luckily I have another machine which has not yet taken down this update, so I saved the 400.vps file from C:\Program Files\Alwil Software\Avast4\DATA into my USB key. I then copied this older version of the 400.vps file onto the computer with bad 091203-0 VPS signature file. I placed it into C:\ for easy access later (because we will be using the Command Prompt, so everything would be typed).
Now on the computer with the bad VPS signature file,
disable the Avast updates by setting it to “Manual”.
Reboot the computer (assuming Windows XP) into
and type the following:
cd “C:\Program Files\Alwil Software\Avast4\DATA”
ren 400.vps 400.vps.091203-0.bad
copy C:\400.vps
(this is why I recommended putting it in C:\ above, less typing)
Then reboot the computer back to Normal mode.
Your Avast VPS signatures should now be reverted to the older version.
Good luck!
Update: December 3, 2009 8:25AM EST
Avast released an updated signature file (VPS 091203-1) that is suppose to resolve the bug. Goto http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=377
.
Source: http://www.google.com/appsstatus
©2012 Johnny Chin. All Rights Reserved.
Source: http://www.google.com/appsstatus