Dear Vlk,
I have had a troublesome time since this upgrade was floated.
The beta version wouldn't write to wherever it should.
I did a clean install after using the cleanup program, managed to finally find my licence no in the chaos!
The one thing that has remained a bother is the little red disk in the blue disk syndrome.
Starting it on the management Console doesn't cure it for the next start-up.
The program does appear to open normally if I only log-off or restart.
I have run repair on add/remove programs.
I have done all sorts of permutaions with and without safe-mode . I don't have an Internet connection in that mode.
As it only started with this upgrade, I tend to think the answer may be with that, but the forums don't appear to show that its bothering a lot of people.
I may be the only person on your forum with an old 233 Dell (Win 95) upgraded in steps to w2000 and 128 MB of RAM.
I run Zone Alarm for firewall and SpyBot for spyware etc. The SpyBot appears to run only on command and is not "resident" .
My Dell 325SX (Win 3.1) sits nearby to amuse the grandchildren!
Any suggestions would be welcome. Could the official release be a more finished article than the "pre-Release" in this respect?
Slán tamall,
Tom Johnson
Hi *,
here I'm again. A service update for avast Home/Pro is coming soon (my guess is in about 1-2 weeks) and as usual, it's my pleasure to announce the availability of a pre-release version of this update.
How to install it:
In case you already have avast 4.7/4.8 installed on your system:
1. NEW! go to avast settings, and on the Troubleshooting page, disable the avast self-defense module (this is NECESSARY for the update to complete successfully)
2. download and run the following program: http://files.avast.com/files/beta/aswbeta.exe
3. after it completes, re-enable self-defense module (disabled in step 1.)
That's about all it takes (provided you have a previous version of avast Home/Pro already installed, of course).
If you don't have the previous version installed, or would prefer to do a clean install (which, in some more serious cases, may be necessary), we have also prepared the full installation packages (setup files). These can be downloaded from the following locations:
http://public.avast.com/~vlk/4.8.1178/setupeng.exe (Home Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupengpro.exe (Professional Edition, English version) ~21MB
http://public.avast.com/~vlk/4.8.1178/setupful.exe (Home Edition, all languages) ~59MB
http://public.avast.com/~vlk/4.8.1178/setupfulpro.exe (Professional Edition, all languages) ~59MB
If your current installation of avast stopped working (and/or cannot be uninstalled), we recommend the following procedure to install this new build from scratch:
1. boot into Windows Safe Mode
2. use aswClear.exe to remove any existing avast installation (or remaints of it)
3. boot back into normal Windows mode and use the above mentioned setup packages to install the new version
There is a number of fixes in this release. Here's an (incomplete) list:
- solved incompatibility of the avast self protection module and the System Restore feature (Windows XP/Vista)
- solved keyboard/mouse lags in some games (e.g. World of Warcraft)
- "Quick" scan now quick again (in the previous version, it was usually slower than "Normal" scan)
- fixed deleting of infected files in some nested archives
- shell extension: under Windows Vista, shortcut targets are now correctly scanned
- boot-time scanner now correctly displays warning messages about corrupted archives
- improved scanning speed in the Simple user interface
- improved handling of scan exceptions
- self protection: improved detection of changes in the INI file
- start of the "avast! Mail Scanner" service should now be fast again
- fixed a problem with avast being installed in a directory with name containing non-Latin characters
- fixed entering of the license key (didn't work in certain configurations)
- improved detection/healing of MBR rootkits
- avast can now correctly handle the case when the INI file is missing/corrupted
- the "Disable startup rootkit scan" option on the Troubleshooting page now effective (in the previous version, it was ignored)
Any comments on this release are welcome and appreciated!
Thanks
Vlk