WinXP, Avast home.
Exclusions in Avast main settings: d:\mercury*
Exclusions in On-Access scanner settings: d:\mercury*
Main scanner excludes files but On-Access scanner does not exclude files on that directory.
On-Access scanner sirens and: Found Eicar … in d:\mercury\eicar.com
Am I doing something wrong or is there a bug?
Odd - I tested it, and it seems to be working fine… :-[
Where exactly (in the program) did you set the exclusion for the on-access scanner? On the ‘Advanced’ tab of Standard Shield’s properties?
Vlk
Main program…
Settings…
Exclusions…
d:\mercury*
Note: These settings affect all parts of avast!
(Including Standard Shield?)
Standard Shield…
Customize…
Advanced…
Here You can modify…
Add…
d:\mercury*
Main scanner and quickscan work ok, they do not find eicar.com in that folder.
Standard Shield: there is a virus …
It finds eicar.com even if I put d:\mercury\eicar.com in the exclusions list.
?
Try to restart the avast! service (Control Panel / Administrative Tools / Services) (or reboot) - doesn’t it help??
Thanks
Vlk
Nope.
I have tested both restarting the service and computer with no affect.
That exclusion setting in Standard Shield does not exclude.
No matter where I put that eicar.com and try to exclude … it is always found by the resident shield.
Actually I installed Avast4 to my other machine (NT4) for testing purposes and the results are the same.
If I remember correct, I had Avast3 (settings nearly the same as in Avast4) in this NT4 setup and it did exclude folders ok.
I can’t believe it behaves differently on your and our machines. 
I have tried it multiple times, even created a directory called “d:\mercury”, but it always worked as expected (tried both XP and NT)… ???
How do you access the file (to trigger the scanner)? What other Standard Shield settings have you changed?
Thanks
Vlk
Standard shield settings : Sensiitivity Normal, no changes.
Define : “it always worked as expected”
At least I expect no activity from on-access scanner when a folder or file is excluded.
Doubleclick eicar.com and Standard Shield jumps in.
By the way, filesystem is ntfs on both machines I tested.
Voila! I tested the “scan-on-read” feature, not “scan-on-execute” (I didn’t try to execute the program).
Now I can simulate it.
We’ll do something about it in the next update.
Thanks for pointing this out,
Vlk
Hi!
I just found this old thread and I am wondering if you (think that you)
have fixed this problem already? ;D
To reduce the (recently very high) cpu utilization I tried to exclude
a folder containing a log-file that is very often updated from scanning,
but to no avail. Avast! is simply ignoring the exclusion and is causing
up to 100% cpu load (by permanently accessing this text-file). ???
Any suggestions?
[AMD XP 2000+, 1024 MB RAM, WinXP pro SP1, NTFS, avast! 4.6.623]
Thanks in advance,
Robert
What exactly did you put into avast! exclusions? (and is it the right one, i.e. Standard Shield settings?)
The comple path of the folder. I put it in the global settings.
Now I tried the Standard Shield setting - that worked. :o ??? 
I still don’t understand why the global exclusion didn’t work,
but I’m ok with that solution, too. Thanks!