It was a custom scan. I'm not sure where the location was or how to find it. I'm not an expert by any means. I had memory selected. So that was most likely the the problem?
Process 2700(superantispyware.exe),m Is what it said in the scan logs.
Yes that was the reason for A) the alert and B) the inability to do anything with it (not a physical file, but a memory location).
So I don't need to scan memory? The alertsare really nothing to worry about then?
Thanks for the responses they are greatly appreciated.
In this instance they are nothing to worry about, though the main point is do you even need the custom scan, you haven't said why you chose to do that and what areas ?
I would say the custom scan isn't really required and is complicated further in that when you select scan memory in a custom scan, it is the most thorough sensitivity memory scan.
####
- With a resident on-access antivirus like avast, the need for frequent on-demand scans is much depreciated. For the most part the on-demand scan is going to be scanning files that would be otherwise be dormant or inert. If they were active files then the on-access file system shield would be scanning them before being created, modified, opened or executed.
I have avast set to do a scheduled weekly Quick scan, set at a time and day that I know the computer will be on. If for some reason my system wasn't on, no big deal I will catch up on the next scheduled scan.