i was using avast since years and i was always satisfied with what it does and was not doing, but since the new update, my exclusions are not working anymore.
I am myself handling with some files containing viruses and sometimes i need to execute them (i know what i do! ) this has always been working with avast past the years.
I created a folder and excluded the whole folder with %path%/folder/*
but since this update, the filesystem-protection (Dateisystem-Schutz in German) keeps finding a virus. Interesting is, that the .exe itself is not threated only the files created by the .exe are found as virus. I have excluded the whole folder and every single file itself in both, the global settings and in the settings of the module, not i don’t know what needs to be done to get this to work.
Thats what was working till the update has broken it.
Like said in op, it is the File System Shield.
I had tried every of these and none was working.
also i tried to exclued the file itself:
C:\Users\Me\Desktop\folder\herp.exe
Like said, the problem is not the path not beeing correct, but files which are created in the folder are found, not the .exe itself.
Example:
we have:
-virus.exe
on execution, virus.exe will create a file called virus.exe.tmp.
with C:\Users\Me\Desktop\folder*:
virus.exe.tmp is deleted
without C:\Users\Me\Desktop\folder*:
virus.exe is deleted
virus.exe.tmp is deleted
Hmmm… All settings in scan when are checked the way avast needs to operate in my opinion, so changing them would not help, because then i could also disable avast for 10 minutes, and that is not what i want
Your last question is somewhat interesting because that is something i would like to analyse but avast is blocking me
But with excluding, avast should not make any difference between the two!
Thanks for the clarification, that i’m not the only one having this error.
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.
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…
I switched to Avast from Avira for this very reason.
Avira exclusions would not work !!!
But ever since I installed Avast, the Exclusions have NEVER worked.
Very frustrating because I use VideoFixer to repair corrupt AVI files and it always find a virus in VideoFixer, as has every antivirus program done for years.
But it is a False Positive. I even reported it in the form to Avast as a false Positive and it is till being scanned.
I excluded the entire folder and the file itself - to no avail.
As a programmer, I would think implementing exclusions would be a simple matter. And if they suddenly stop working, then the fix would be simple as well. Not sure why Avast does not quickly post the fix in an update but I don’t work there so have no idea.
) this has always been working with avast past the years.