I know that some of Nirsoft's tools are considered to be riskware. However, in many cases, they are essential to getting someone's PC back up and running. IMO, while they can be abused, they are really help/forensic tools. Is there any chance of them being white-listed for NAV/NIS/360? It is a pain to keep a set on my netbook without going through a bunch of exclusions...
Which brings up exclusions... The only exclusion set by default in NIS is
\System Volume Information\
My question is, since this example uses a relative path, i.e., no mention of any drive(s), why can't I do a similar thing for something like
\Nirsoft NirLauncher\
I tried and NIS won't accept this syntax. The only way I could do this was to specify a complete path, drive letter and all.
Since this is a user to user help forum, I suspect that none of us can answer your question. It might be faster to submit the Nirsoft .exe files to Symantec as false positives. If there is no problem, they will be whitelisted. I suspect the path information was something worked on by both Symantec and Microsoft to handle the requirements for system volume info.
I know that some of Nirsoft's tools are considered to be riskware. However, in many cases, they are essential to getting someone's PC back up and running. IMO, while they can be abused, they are really help/forensic tools. Is there any chance of them being white-listed for NAV/NIS/360? It is a pain to keep a set on my netbook without going through a bunch of exclusions...
Which brings up exclusions... The only exclusion set by default in NIS is
\System Volume Information\
My question is, since this example uses a relative path, i.e., no mention of any drive(s), why can't I do a similar thing for something like
\Nirsoft NirLauncher\
I tried and NIS won't accept this syntax. The only way I could do this was to specify a complete path, drive letter and all.