I use AVAST Home. I tried to exclude the files in resident protection without any success. I moved Sensitivity to CUSTOM and put my files to be excluded in Standard Shield/Customize…/Advanced, like this:
C:\PROGRAM FILES\keylog*.*
But AVast still keep detecting my files. What did I do wrong ? Please suggest.
And one other thing, when I check “On access protection control” again, the sensitivity slide bar is changed to High, instead of “Custom” which it is supposed to. Is this a bug ? Is this why it did not work for exlusion files ?
I use XP Pro. Avast will pop up detecting my excluded files when I try to open any folder. (The avast icon ratates showing the detection.) I guess that file has already in the memory.
I set the standard shield just I have already told. (Sensitivity is slided to Custom. In Customize…\Advanced, I put
C:\PROGRAM FILES\keylog*.*
And as I’ve already told you, the sensitivity slide bar never stays at Custom, it will go back to High. Is that strange?
Open folder? Hm… what program do you use? Just the basic Windows Explorer?
If you open the resident protection window, what does the “Last checked” show? (leftclick the blue icon, select “More details” if not already, and select the Standard Shield provider; there are “Last checked file” (and others) displayed. Can you give me an example of a filename that is scanned (even though it shouldn’t)?
kaka, the rotation of the icon could be related to other operation than ‘opening’ the folder, I mean, in background…
To be sure of the ‘exclusion’ behavior you can:
disable avast! providers.
copy the eicar.com file (virus test file) into that specific folder
I can perfectly repro this - imho - erratic behavior.
Regardless of what you enter in the exclude field, the files get scanned anyway AND the sensitivity slider does not stay at “custom” but returns to whatever it was before (either “normal” or “high”).
I have a lot of OpenMG music files on one of my systems and the SonicStage program sometimes has problems playing these files when avast puts itself in the chain.
Maybe one of the avast team members is willing to comment on this.
Hmm, I guess I know where the problem is.
The paths (for the exclusions) are matched exactly as they are… which may not be the best idea for LFN paths. I mean, if a file is accessed with the long filename, as C:\Program Files\keylog.…, the exlusion will work. However, it the same file is accessed with its short filename, as C:\PROGRA~1\keylog.…, it won’t - and the file will be scanned.
For now, try to add C:\PROGRA~1\keylog* to the exception list as well (in addition to what’s already there).