Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 18 replies
  • Subscribers 8 subscribers
  • Views 52721 views
  • Users 0 members are here
Options
Suggested
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

Full Scan will not complete

jshoughton

I have tried many times to complete a full scan and each time it stops at about a third left to go with the following error:

"Scan cannot be completes.  An error occured running the scan."

I have tried redownloading, removing and reinstalling Sophos, and get the same result.  In case it was an issue with the bootcamp partition I excluded it in a custom scan and the same error still appears.

It is running on an iMac 3.06GHz intel core i3, which has been upgraded from Snow Leopard to Lion.  I had no problems running the full scan prior to upgrading to Lion.  I am running the latest version of Sophos (7.3.2c with threat detection engine 3.22.0), so it should be a Lion compatible version.

Another problem that has developed since the upgrade is the shield icon on the top bar intermitently disappears and the setting to display in status bar needs to be rechecked to enable it again.

Any help with this would be much appreciated as until now I've had no problems at all with this great free tool!

:1003679


This thread was automatically locked due to age.
Parents
  • 0

    "Scan inside archives and compressed files" being disabled on the on-access scan isn't really a big issue in most situations, as most of the time, an archive has to be unpacked in order to do anything with the contents -- at which point, any malicious files inside the archive are detected.

    However, I'm pretty sure the development team is aware of the issue.

    The "corrupt files" issue has been discussed in another thread; what's happening is that the scanner attempts to identify the file type, and if it detects it as one format but doesn't find the contents match that format, it labels it as corrupt.

    Thanks for pointing to the MacPorts .gz files as being the issue; this likely relates to your other post about on-access scan failure too, and should be investigated.

    Would you be able to post a list of some ports packages that are being flagged as corrupt?  That way the labs and dev teams have some test data to work with.

    As for "Shouldn't Sophos be able to handle everything that the OS can handle," the answer is "it should be, in theory."  However, as a security product being installed on a system that might be infected, SAV tends to use its own toolset, as the OS tools might be compromised by malware.

    :1003811
Reply
  • 0

    "Scan inside archives and compressed files" being disabled on the on-access scan isn't really a big issue in most situations, as most of the time, an archive has to be unpacked in order to do anything with the contents -- at which point, any malicious files inside the archive are detected.

    However, I'm pretty sure the development team is aware of the issue.

    The "corrupt files" issue has been discussed in another thread; what's happening is that the scanner attempts to identify the file type, and if it detects it as one format but doesn't find the contents match that format, it labels it as corrupt.

    Thanks for pointing to the MacPorts .gz files as being the issue; this likely relates to your other post about on-access scan failure too, and should be investigated.

    Would you be able to post a list of some ports packages that are being flagged as corrupt?  That way the labs and dev teams have some test data to work with.

    As for "Shouldn't Sophos be able to handle everything that the OS can handle," the answer is "it should be, in theory."  However, as a security product being installed on a system that might be infected, SAV tends to use its own toolset, as the OS tools might be compromised by malware.

    :1003811
Children
No Data
Unfiltered HTML