Jump to content

AMbit

Members
  • Posts

    10
  • Joined

  • Last visited

Kudos

  1. Upvote
    AMbit received kudos from peteyt in Cleaning behavior is odd   
    I'm running v13.0.22.0, and I'm getting some odd behavior.

    So, here's the preliminary information:
    I have all scans set to "No cleaning". A scheduled scan ran and a post-scan alert came up showing me the detections it found (all in archives).  I chose "No Action" for all of them.
    So far, so good.  However, then I noticed this:
    Under the "Computer Scan" tab, the log entry shows "Scan completed:  All detections cleaned". The Quarantine shows all of the files where detections occurred.
    The above items would indicate that ESET cleaned files that I explicitly told it not to touch.  For ESET to modify/delete files I told it to leave alone, that would be bad.
    And yet, as far as I can tell, all of the files still exist in the file system and haven't been deleted.

    This is very confusing to me.
    If ESET correctly did as I instructed and ignored the detections, then I would expect that the log entry would show that detections were ignored, not cleaned.  In addition, I would not expect anything to be added to the Quarantine.
    And yet, if ESET *did* clean all the files, then why are they still in the file system?
     
    Can anyone explain this odd behavior?
×
×
  • Create New...