This thread is now obsolete. The new update has now been officially released as version 4.7.869. Thanks to everyone who helped testing.
Hi *,
as usual, we’re offering our forum members to test drive the upcoming avast update before it is official released. The pre-release version is currently labeled as 4.7.867.
How to install it (for starters - most people already know this trick anyway ): simply download and run the following program: http://files.avast.com/files/beta/aswbeta.exe . That’s about all it takes (provided you have the latest version of avast Home/Pro already installed, of course).
This is a minor release but it brings a fair number of fixes and enhancements,
EDIT:
I don’t see any difference in HE edition. Update was quiet big though and it appears to update quiet a lot of things.
Anything to watch/test in specific?
Standard Shield now compatible with NT systems set up for the C@ security standard
minor fixes in the data storage
auto-updater now run with normal priority (used to be high priority)
minor enhancements in a number of unpackers (e.g. added support for old versions of UPX)
fixed a bug in LHARC unpacker
fixed a bug related to deletion of files from certain special archives; the “move to chest” operation used to, under certain circumstances, cause the file to be actually extracted to the avast folder
attempt to solve the problem with corruption of ThunderBird mailbox when a virus is found in its first email
files not scanned because of scan exclusions are not displayed in the Simple UI results dialog anymore
hyperlinks (e.g. “virus information”) are now opened in browser’s new window
Windows 9x: fixed a bug in data storage causing incorrect behavior if the program was installed to a folder with non-Latin character path name
minor optimization of memory consumption of the “avast! Antivirus” service (process ashServ.exe/aswServ.exe)
RejZoR, unfortunately, I’m not able to simulate the problem you’re having. Does it happen even if you scan these files alone? (i.e. the folder where the files are).
Tech, under Vista, it may be necessary to run aswBeta.exe as real admin. Can you please right-click the file, and select “Run As Administrator”?
I knew updater was running at high priority because i always knew when it was updating when i was playing games. Normal priority should be now fully transparent i guess.
Btw is help file unpacking now supported again (because it was disabled because of that vulnerability)?
Just one of those nagging … I can’t prove it (yet) … concerns.
I installed this beta on 08/03. Since then I have been experiencing significant problems with Norton GoBack (4.02.309). Basically … Norton GoBack is telling me (on every system hard start) that I can only go back as far as the most recent system start (my typical timeframe is 10-14 days).
I’m definitely not saying this an avast problem … but the avast beta update is the only change I have made in the past week. I have never experienced this problem with Goback before and there have been no updates to Goback in living memory.
Just wondering if there are any boot record/startup/file system intercept changes in this beta.
I have just restored my system to an (Acronis TrueImage) image from 10 days ago so I am back pre-beta of avast. I’ll leave it and monitor for a few days before I try the beta again.
