So how’s it going with the new build? No new crashes? No new problems?
And what about the probs that were introduced in 4.1.260 - are they gone? What about the P2P/IM provs? FreeCell? Empty bodies in Outlook? …?
No problems here! (Avast pro and WinXP pro with several email clients like Outlook, OE, Eudora, Pegasus)
Updated yesterday (18.9) manually and this morning got 24 pieces of this new Swen worm through email (Avast website calls it Swan ?). Avast removed every one of them! (Well 50 more during the day.)
Well I do not need any fancy new features, just make a simple and solid program that works!
This test in real life today told me that I did not waste my money!
mantra do you have version 4.1.268? That version should absolutely not ask you for a reboot after an VPS update (unlike v4.1.260 which had a bug that was causing just this…).
Vlk – just did a clean install of 4.1.268 and my computer is much happier with it. Only thing I noticed was that while the program says 4.1.268, the drivers listed in Windows System32 say 4.1.267. Any cause for concern?
Vlk
it asked me to reboot!
i have version 4.1.268!
i update the virus database and it asked me for a reboot
what should i do ? download the full version ?
i used the built in updater!!
maybe it asked me for reboot
because i renamed Ahresmes.dll in Ahresmes.back?
or?
can u give me an advise VLK???
download the full version from www.avast.com?
mantra: yes, it’s possibly because you renamed the files. The updater is trying to “rectify the problem”, you know… As I stated previously, renaming these files is probably not the best way to stop using the providers… (see previous discussions about this).
dave: that’s fine. The drivers should be 4.1.267. Build 268 was just a refresh with virtually no changes, designed to be released “out”…
That almost for sure. Check setup.log in setup directory. It should tell you why did it ask for reboot.
Avast installer forces all files to be correct. If some of them get broken (or deleted), installer replaces them on next ‘repair/refresh’ operation. It’s unlikely this behaviour will change.