With all builds before the latest 235, the on-access scanner scanned all files on open when entering the “*” as extension in the appropriate box. Thus it detected a renamed eicar (e.g. eicar.txt) file as being “infected”. However this behaviour stopped with the latest version although the file itself is scanned.
What did change in the recent v235 update?
What OS do you use?
How did the behaviour change - the virus is not announced? How do you know that “the file itself is scanned”?
The file is scanned because the on-access scanner window lists it as scanned. Anyway, even a reboot didn’t make Avast see the eicar string in a “eicar.txt”. But a “pause provider”, then “resume provider” did. Now avast sees the eicar string again; I was just curious if you changed something in the extension settings…
Supose it was just a glitch on my system.
KMT
Strange… so now, even after a reboot, is works correctly from the start (i.e. without having to pause/resume the provider?
What operating system are you using, please?
Yes, now it keeps this settings…will try to reproduce this on another system and see if it was a one time glitch.
I am using Win98
I have no problems putting the * into the exctension list. (after update) it scans ALL files without problems.
Isn’t it nescecary to put ALL extensions in the list like .txt. .exe. com etc… or does the * replaces ALL extensions just by putting the * in ? Really ?
Thanks IGOR > you rule ! 