Guys, since there is a number of pending threads about this topic and it’s quite strenuous to keep them all updated, I’ve decided to start yet another thread with the anticipation that we’re close to the final solution.
My impression is that the problems are caused by a bug in the updater that sometimes fails to install the new driver files. That is, the updated drivers are correctly downloaded and unpacked, but are not installed to the system. Since other avast files are installed properly, there is a version-discrepancy problem (the program and driver versions do not match) that may eventually lead to disasters.
I’d need you to check if the drivers (i.e. the *.sys files) located in the \setup\inf directory are the same as these in \windows\system32\drivers (with respect to file sizes, timestamps etc.). They should be the same. If they’re not, there is a problem and you should copy the \setup\inf versions to \windows\system32\drivers.
Please keep me informed - I would really like to know whether this is the real cause of these problems.
Vlk – my files read the same as Technical’s – 9/11/03 date with all reading 4.0.191.0 in System32\Drivers as well as avast\setup\info.
As I reported on Saturday, after the program update downloaded on Thursday, P2P protection didn’t work. However, after the reboot with the iAVS update on Friday, avast! is working perfectly. As you stated, the drivers probably installed properly with that reboot.
Keep up the good work. You’ve got a great product!
Vlk – just noticed something and I don’t know if it’s important. As reported, the files in avast\setup\info and windows system32\drivers say version 4.0.191.0 with the September 11th date. However – when checking the program version on avast! itself, it says 4.0.260 –
On the upgrade to 4.1.260 some “strange” things happen in Windows Installer:
If the user choose Change/Remove the application, the left side on the setup window does not show the components neither
to “Update” nor to “Change”. The user could not choose what to update or change in the installation…
The file vpsupd.exe (update file) cannot be applied to version 4.1.260: Error: 0x00000008 (only works with previous version…
On the upgrade to 4.1.260 some “strange” things happened in the Windows Installer:
If the user chooses Change/Remove the application, the left side of the setup window does not show the components: “Update” “Change”. The user could not choose what to update or change in the installation…
Cannot uninstall avast for obvious reasons…
System locks up…
OOPS!
Tried file version check suggestion at top of thread to no avail…
Thanks Vlk. Worked at XP but not at Windows 98 :‘(
I´ll do more tests… I downloaded entire 4.1.268 setup but, in Windows 98, it does not allow me to change the modules.
When I run it, the change module at Windows Installer continue to give the same error. Nothing happens after I try to “change” the components :’(