** INTRODUCING **: pre-release version of upcoming avast update (now 4.8.1192)

[Solemn]

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.

[smokeyjoe]

Using Avast 4.8.1192
Picture is self explanatory.
So what does that scanner pop up message mean? Is everything ok?



 

[OisteinR]

Avast 4.8.1192

When opening Outlook.
What is this?

[Hop]

I saw the same error during a windows update
i can't screen him but they look like to smokeyjoe's warning

[onlysomeone]

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

[alanrf]

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. 

[onlysomeone]

The avast registry keys are also protected (or are supposed to be).

It's no magic, really. Just a filter driver (in kernel mode).


Thanks
Vlk

probably thats the reason why this messages appear...

[MiguelAngelXP]

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 

[OisteinR]

Avast 4.8.1192

When opening Outlook.
What is this?

Updating to XP SP3 gives houndreds of this type of warnings while updating.
It was something with Registry though...
Really annoying......

[igor]

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...

[Lisandro]

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...

Why weren't I asked to disable avast while updating to SP3

[igor]

By whom?
And I don't think it's necessary anyway, I was just trying to explain the messages from avast! self-defense.

[sunrisecc]

In the KB article that relates to SP3, it was recommended to disable your AV.

[Lisandro]

By whom?

By Windows trying to manage avast files/registry keys, by Windows Update while updating...
I've read some users are being asked to disable the antivirus (http://forum.avast.com/index.php?topic=34934.msg296882#msg296882). I wasn't asked to do so.

[RejZoR]

In the KB article that relates to SP3, it was recommended to disable your AV.

They all say this crap in ANY installer. This kinda defeats the purpose of antivirus if it's disabled while installing something.
Installers may look nice on the outside, but may contain bad code on the inside...