Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do you create a custom scan?

After a first complete scan, 3 threats were quarantined, although the Sophos AV said 5 were detected - where are the other 2? The report said - "that the threat cannot be cleaned up. Please click the threat name above for manual cleanup instructions."

The manual cleanup instructions said -

11. If there are any threats for which the action available is "Clean up manually", create a custom scan.

12. Select the areas where the remaining threats reside and add these to the Scan items.

13. In the Options tab, select "Delete threat" from the drop down menu.

14. Click Done.

15. Run the scan.

First of all I cannot find a way to create a custom scan. There seems no way to drag and drop the threats into the custom scan window, or to move them there any other way. When I clicked the + button I expected to be able to select the threats and add them in, but all it did was create an empty file.

The software seems very unintuitive and un Apple like, very disorganised and illogical just like Windows. On the other hand, it may well be me that doesn't get it!!!! Having said that, it's good of Sophos to offer this program, and hopefully in time it will become more Apple like with a better UI.

Can you advise me, please? Thanks.

I am running Tiger 10.4.11

:1000163


This thread was automatically locked due to age.
Parents
  • Would you please list the threat name that is not being cleaned up?  Detection and cleanup are two different things, and it's always possible that your file is not being cleaned up for some understandable reason -- but this should fail nicely with the reason given.  I can update the cleanup handling if I know what the threat was and in what conditions cleanup was attempted.

    The most common reason that cleanup fails is that the file was deleted (temporary file) before cleanup could complete.  This one may be hard to fix.  The second most common reason that cleanup fails is that the item was detected inside an archive, and could not be cleaned up without potentially damaging other innocent files included in the archive.

    :1008962
Reply
  • Would you please list the threat name that is not being cleaned up?  Detection and cleanup are two different things, and it's always possible that your file is not being cleaned up for some understandable reason -- but this should fail nicely with the reason given.  I can update the cleanup handling if I know what the threat was and in what conditions cleanup was attempted.

    The most common reason that cleanup fails is that the file was deleted (temporary file) before cleanup could complete.  This one may be hard to fix.  The second most common reason that cleanup fails is that the item was detected inside an archive, and could not be cleaned up without potentially damaging other innocent files included in the archive.

    :1008962
Children
No Data