I’m afraid all your images were for nought as they don’t show what you actually entered in the exclusions, nor does the alert screen show the full path and file name that avast is alerting on, so I can’t compare them.
Try f:*\elite keylogger\filename.exe, where filename.exe is the actual executable avast alerts on (you can actually copy and paste the path in the alert window avast). The * wildcard saves entering the full path, but should be used with care or you could leave a hole in your security.
This is I would say what is required, F:\Archivos de programa\WideStep Software\Elite Keylogger\logs viewer.exe as that is what is being alerted on. Entering what you did, doesn’t define any file, you either have to define a specific file or exclude the folder by the use of a wildcard (not advisable).
I have to say I find it strange to have a file name with a space in it, e.g. the “logs viewer.exe” name.
Looking at this I would say this isn’t an essential file if the [Armadillo][Embedded_R#FEEDBACK] means what I think it does, sends feedback, to whom does it send this feedback ?
If I read well perhaps I’m doing the things bad, because I interpreted until now that when I put a folder I’m not putting nothing
How can I express a folder, subfolders and any file in it ?
Suppose the folder is M:\pepe\
and this folder has two subfolder : joaquin and maria
That’s :
M:\pepe\joaquin
M:\pepe\maria
and each subfolder has two files : merienda.exe and torcuato.exe
and the other one : cena.exe and nicolas.exe
that’s
M:\pepe\joaquin\merienda.exe
M:\pepe\joaquin\torcuato.exe
M:\pepe\maria\cena.exe
M:\pepe\maria\nicolas.exe
I want to put as an exception all below M:\pepe\
How can I do ?
Is M:\pepe*.* /s ?
Thanks
Excuse my language. I’m from Canary Islands
You add an * at the end after the closing folder mark (this excludes all files, sub folders and files in those sub folders), M:\pepe* this however, is madness as it can leave a huge hole in your security.
Exclusions should be more specific to a specific file or file type within a folder, or everything in there would be able to run without being scanned a big mistake for executable files, which are the targets of many pieces of malware.
I think the exceptions don’t goes well in the avast free version.
Not in the resident scanning mode, because I am tired of put exceptions with no result.
Am I right ?
Thanks
Excuse my language. I’m from Canary Islands
The exceptions work exactly the same in the Home or Pro version, so again you need to show, a) the exact text of the avast alert, b the exact text you entered in the standard shields exclusion.
Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning section, this contains information on all avast detections. C:\Program Files\Alwil Software\Avast4\ashLogV.exe
Or check the source file using notepad C:\Program Files\Alwil Software\Avast4\DATA\log\Warning.log. This is probably the easier place to copy and paste the full text of the alert. From that you should also be able to paste that path into the standard shield exclusions.
