Jump to content

Auslogics - again


Recommended Posts

Sorry to harp on about this, but please can someone advise on how I make a *permanent* exclusion for something that ESET classes as a PUA but which I feel is unfounded. Every day my file gets scanned and shows an alert; every day I say "no action". Rinse and repeat.

I've now resorted to deleting the utility and will simply re-download it when I need it, but that is NOT the solution. There must be a way in EEA or ERA to exclude this alert type or marking the file as safe. i don't really want to use path names as I have several copies/versions of this file.

 

Many thanks

 

 

Jim

Link to comment
Share on other sites

Thanks Marcos, I've configured that but it doesn't seem to want to work for me. Hopefully the screenshots show how I have defined the policy, and I have confirmed that the policy has been applied.

 

59661fb33e24f_ERA2017-07-12_140443.jpg.ae20ae9540b395eb16f9019226b16b95.jpg59661fb3f2ba7_ERA2017-07-12_140743.jpg.1609052b9d07a4a0986dce7762a867c6.jpg

Link to comment
Share on other sites

  • Administrators

The threat name must be entered as

@NAME=Win32/Auslogics.F

We plan to improve this in future versions (likely in v7) so that the detection name does not have to have "@NAME=" prepended.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...