Why don’t you update to beta in the conventional way?
Download the updater (http://files.avast.com/files/beta/aswbeta.exe) and run it.
Hi Tech
Simple answer. Because of a recent problem with SR and Avast which I have used for a long time I removed and
tried other AV software to be sure the problem was in Avast.
I wanted to do a complete new install of the Beta - not upgrade 4.7.
Why bother with a link to 4.8.1187 if the link does not work!!!
Guess I will forget about it until the “official” release.
Baz
why does the link not work?! - if you have an older Avast!-edition installed it upgrades to the actual version…
but if you want an other link just go to the first side of this topic:
http://forum.avast.com/index.php?topic=34612.0
EDIT: The links on the first side are for the whole program…
Re: Freezing and missing message when ‘Push iAVS’ checked in Home version, 95OSR2
Upgraded (finally) from 1185 to 1187 today. All good, no freeze, message appears. 
I edited the avast4.ini file as the tutorial says but it didn’t work, and well , I will let it go, avast 4.8 is working fine just the way I like it like the song
Thanks Tech
Kindly regards
MiguelAngelXP ;D
You can download version 4.8 (not 4.7) and then upgrade to beta.
It won’t make a difference at all.
i noticed that when i use quickscan (4.8 last beta) on xGB folder with various video file formats (wmv, avi, mpg, mpeg, flv, mkv)
then it takes avast very very long time to complete the task (similar with other scans on same files)…
it seems Avast! read the whole file from start to end and it’s also slow (approx 2-3 times slower than disk read speed)
reason?
I assume you mean ashQuick.exe with is the most thorough of that scans as the Quick (on-demand, simple user interface) scan I don’t think scans many of the file types you mentioned by default ?
So if you are using ashQuick.ex in lieu of a scheduled scan that wasn’t something it was designed to do the bulk scanning of files, folders, partitions or drives. You could exclude your media folders for on-demand scans, which includes the ashquick.exe scan (Program Settings, Exclusions).
yes it’s only on the thorough scan style the standard scan goes quite fast (18s for 15+ GB)
The beta has now been updated to v4.8.1192. To get this version from any of the previous beta builds, simply invoke the Program Update feature from within the avast GUI (you don’t need to run aswBeta.exe again).
This is very likely the last beta build before the product goes gold.
Thanks
Vlk
Good to hear Vlk, although this issue immediately popped up again after the update. Think there’s a bit more tweaking involved before it does hit gold. :-X
Using Avast 4.8.1192
Picture is self explanatory.
So what does that scanner pop up message mean? Is everything ok?
???
http://i98.photobucket.com/albums/l277/deadlyskull1977/Avast.jpg
???
Avast 4.8.1192
When opening Outlook.
What is this???
I saw the same error during a windows update
i can’t screen him but they look like to smokeyjoe’s warning
Hi!
I also got the message like smokeyjoe when I opened MS Outlook!
But I don’t think, that this is an error message - it seems as if it would be an info from the self-defense-module or something…
yours
onlysomeone
I hope that the message onlysomeone is seeing is the same as that posted by OisteinR.
That error message (which I did not see with releases before 1192) seems to be at exactly the time the avast plugin for Outlook is activated. It occurs (for me) whether the Outlook plugin is started or not in avast. It does not occur if the avast plugin is deactivated in Outlook. It also occurs concurrently with enabling the avast plugin in avast.
probably thats the reason why this messages appear…
I have the same problem (MS Outlook). Anyway I can receive/send e-mails and the scan issue appears to be gone
http://forum.avast.com/index.php?topic=35277.msg296665#msg296665
Kindly Regards
MiguelAngelXP ;D
Updating to XP SP3 gives houndreds of this type of warnings while updating.
It was something with Registry though…
Really annoying…
I believe this particular file (URLs.txt) is an omission and could be fixed somehow… but yes, I believe if you are updating to SP3 (or similar operations), it may request some write access to avast! registry keys…