This is a bug I reported quite some time ago, it was acknowledged by the devs, but no one has done anything to fix it.
The situation is the following:
If you want to add a single file name (for example “file.exe”) to the exclusions or, for example, you want to exclude all files with an extension of .123, you can’t.
Avast always assumes you’re trying to add TWO URLs, eg, http://file.exe and https://file.exe instead of just A FILE NAMED FILE.EXE, regardless of its location on the disk (which is what I want to do).
same goes for the *.123 files.
I really hope someone can look into this. It’s extremely annoying.
avast free, lastest ver 20.10
windows 7 x64 SP1 + all patches
always used avast on this PC
other programs: super antispyware, malware bytes, but the DO NOT RUN in the background, only “on demand” use.
but that doesn’t really matter, it’s being happening for quite some time, from several versions back.
try it yourself and you’ll see exactly what I mean.
Well, the exception UI is waiting for a complete redesign… but I can’t tell you when it’s gonna happen.
Note, however, that file.exe is not what you want to enter as an exclusion - it wouldn’t work (even if the UI didn’t incorrectly assume it’s a URL) because it would never match any scanned path; it’s matched against the mask as whole. What you need to enter is *\file.exe *.123 should work (if not for the UI issue) - but you can avoid it similarly, by entering **.123