Hi all,
using Nod31 11.1.54.0 on Win 10 here... it seems the way how I can add exclusion entries for folders and all its subfolders/contents is not working anymore how it used to in older versions, or how it is indeed still stated in the help texts. So I need a quick hint here on how to do it properly now.
The help states:
1) "to exclude all files in a folder, use *.*" - e.g. "D:\foobar\*.*" this would then include all files in the folder "foobar", but NOT in any subfolders.
2) "to exclude including all files and subfolders, use *" - e.g. "D:\foobar\*" this would then include all files in the folder "foobar" AND in any subfolders.
And this his how I setup my exclusions in the past, and I have some of these "type 2" wildcard entries still in my list.
However: if I want to add some new exclusions for "a folder and all its subfolders", it seems the UI does not allow me to add the single "*" to a path anymore. If I select a path from the exclusion UI, it is displayed without a trailing backslash, e.g. "D:\foobar". Adding a trailing backslash and "*.*" works fine, e.g. "D:\foobar\*.*" (see attached image eset_wildcard_01.png).
But when I try to add the backslash and only a single "*", e.g. "D:\foobar\*", the UI now marks the text in red and with an error icon, stating "invalid path" (see attached image eset_wildcard_02.png).
So my questions are: is this a bug or am I missing something? And if the latter, what is the correct way now to exclude a folder and ALL its contents/subfolders from real-time scanning in Nod32 11.x?
Thanks a lot!