[b]This thread is now obsolete - the new version has already been released, as 4.7.844.
Thanks.[/b]
Hi *,
this is already becoming a tradition. As usual, we’re offering our forum members to test drive the upcoming avast update before it is official released.
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, and doesn’t bring any new big features. It should fix couple of bugs that were discovered since the last official update (such as incorrect display of non-Latin characters in avast tasks - although in some special cases, a reinstall of the program may be necessary to completely solve the problem). Also, we have added an AsProtect unpacker in this release (quite an interesting change) - so I’d like to ask everyone who installs this version to run a full on-demand scan of all your drives (with unpacking enabled) and report any respective problems (stalls, crashes etc).
Also, this build adds Danish language pack - so if there’s anyone who speaks Danish here, it would be very helpful if he/she could install it and report any typos, grammatical errors etc (this applies to the program and the help files as well).
Two of the changes mentioned by Vlk (the Danish language pack and the ASProtect unpacker) are in the state of “being polished” - so they’ll be slightly improved within the next few days.
have installed this build on two of my laptops. on both machines avast insisted to have the computer restarted two times.
and: on both machines the blue avast icon in system tray stopped spinning after the update. at firs ti thought this was indication non running providers, but avast control panel indicates that all providers are running smoothly and the “Last scanned: …” item and “Scanned Count” is changing over time.
Well installed it without a problems, only one reboot was required.
Also I run a full system scan(unpacking was enabled) and everything went fine - no errors
I have since re-installed avast on one of my two laptops showing the before mentioned strange upgrade behavior.
After I de-installed avast and rebooted, Windows Security Center still reported avast 4.7.838 as installed and virus database information as up-to-date. Funny. I double checked but no avast component was left on the system (no services, no nothing). Maybe this was because I used the stand-alone deinstaller (aswclear).
Before re-installing avast, I removed some avast relarted entries from the registry and deleted avast installation folders to start as clean as possible. While the newly installed version 4.7.827 could be painlessly updated to version 4.7.738 and only one reboot was necessary, I noticed that security settings on the installation folders are still pretty weak (yes, we’re talking Windows XP here): While group Users had “Read&Execute, Read” permission on files on folder DATA, group Everyone had “Full Control”. E. g. file avast.ini had User:Read&Exe and Everyone:FullControl. This does result in a plain FullControl for any user which might not be what is intended (or desireable). Other folders had a plain Everyone:FullControl … - I would prefer much thighter security settings here.
I have the beta up and running. No problems so far. Only that the avast seems to start up a little later than before. When my screen opens, I was used to see
the icon spinning, indicating that avast was running. Now it starts whit a icon whit the red circle, and then starts whit in 10 sek.
Haven’t tried a scan yet. But I have some corrections to the translating.
when start up the “memory and startup test” translation is to long. “Stands hukkomelsest" is what I can see, but in fact there is missing 3 letters. it should say " stands hukkomelsestest” but there isn’t room enough. And it look stupid. ;D
I suggest something shorter, like " stands test "
In settings > confirms > you missed a line. " ask before deliting files from chest " is not translated.
Could be something like " spørg før sletning af filer i viruskiste."
Thats it for now. I will now go fore the big scan.
See you later.
I noticed that security settings on the installation folders are still pretty weak (yes, we're talking Windows XP here): While group Users had "Read&Execute, Read" permission on files on folder DATA, group Everyone had "Full Control". E. g. file avast.ini had User:Read&Exe and Everyone:FullControl. This does result in a plain FullControl for any user which might not be what is intended (or desireable). Other folders had a plain Everyone:FullControl ... - I would prefer much thighter security settings here.
Strange, really. The main Avast4 folder (i.e. the one with the binaries) should NOT have the Everyone/FullControl right. Only the DATA folder (and its subfolders). Isn't that the case on your machine?
Daffy, Igor will follow up with you (he handles avast translations). Thanks for the comments. The unpacker box – I meant simply the “Scan archives” box in the Simple UI.
Well, I wish I could. But the changes are pretty subtle.
So (unless you speak Danish), the short list would be something like
test scanning in Outlook/Exchange or ScriptBlocker provider when NOT logged on as an admin (there have been some fixes in this code to accomodate Vista beta 2)
on-demand scan your whole hard drive, with archive scanning enabled
check the access rights of your Avast4 folder. There should be no Everyone/FullControl entry.
That’s about all I can think of from the top of my head right now…
Tryed with Simple User Interface, not a trouble. My Pro license is at one off-line computer right now, so, can’t test the beta there.
There isn’t…
I’m not using the default path, although it is a subfolder of %ProgramFiles%.
I have Full control to Administrators (group and my account) and System.
Normal Users could read/execute. Advanced Users could modify/write.
I’m using XP Pro SP2+ and advanced folder sharing option (not the simple one in Windows Explorer), if this concerns.
Thanks Vlk. I wish I could keep helping here in forums as much as I can.