Yes, the exclusions for writing don't seem to work in the last version.
This is the type of test I was aiming at. My point was, if the virus is only being written (not executed), then the "scan when writing" is the setting that should get you a different result in scanning, specially if you would use "scan all files". That's the reason I asked for your settings there.
If you can, please test these settings in several combinations so to confirm igor's suspicion.
Please report back your test's results.
seems like igor is right, disabling check for writing leads to no found and disabling check for open leaves no difference.
Ok, i think, in this case we all can clearly state that avast has a bug.
is there a need to report this bug, or is it already known or is it known since this thread?
just asking because i think this should be fixed soon
Thanks for all your help in finding the issue
Kostronor
wowow big edit:
Seems to me that my first guess was wrong, the shield even scans when deactivated. i have deactivated the FSS and it is finding the virus. But i checked every module and none of them is telling me that a virus has been found...
i will now investigate a bit further about it
Well, i cannot find what is finding the virus.
even with FSS disabled it is finding it.
with all modules disabled nothing is found...