How Do I "Do Nothing" for False Positives in Amon?

Why is there no setting to enable a "Do Nothing" (allow access) option on the alert dialog when false positives are detected by Amon?

Surely you don't want us to disable Amon entirely so we can get past whatever we're trying to do when a false positive pops up!?

David Frailey, MCSE
Williamstown, WV

 

Add whatever it is to AMON's exclusion list.

 

Compress the file, protect it with the password "infected" and submit it to "samples[at]eset.com" with "false positive" in the subject.

 

Guys, I appreciate your response, but most of the time I don't have the time to do those things.

I've been pretty happy with Nod32, but I'm surprised (and disapointed) on this one. I don't think I should have to disable Amon, or add to an exception list, if I need to access a file on "my" system that Amon happens to have a problem with (the rest of my family is another story ).

IMHO there needs to be a configurable setting (which can default to disabled) that enables an "Ignore" option on the Amon threat detected dialog (i.e. "It's OK, I understand what you're saying, but I still need to access my file").

In this particular case it's Nirsoft's Produkey utility that's all of the sudden tripping a warning during a replication operation.

Regards,

David G. Frailey, MCSE
Williamstown, WV

 

Fair point although if you do what Marcos asks it will be added to NOD's false positive list and released in an upcoming update then you'll have no more false positives!

 

Suggest you add your suggestion concerning Ignore here. https://www.wilderssecurity.com/showthread.php?p=1099483#post1099483

 

Done.

Thanks for the tip.

David G. Frailey, MCSE
Williamstown, WV

 

Adding to the exception list seems the most logical, and easiest/guaranteed way to do with..regardless of what brand antivirus product you're dealing with.

It's sort of what the exceptions list is designed for...so the AV product keeps its nose out of there.