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

Why is my scan taking so long?

I have a powerful MacBook Pro with SSD drive. I started a full scan at 11 AM and now it's 7 PM and it still says 297,009 files to go, and 4 out of 8 cores are churning constantly at about 50% CPU. It's my first ever scan after installing the latest version. In the logs I see lots of SophosSXLD EARLY TIMEOUT dns context warning messages. I also get the feeling that certain files are being scanned over and over again. For example, I have seen jdk-8u11-macosx-x64.dmg come up several times. Also, from time to time the log says 'Corrupt file' when trying to read a '*.dmg.part' file. I'm running OS X Yosemite.

Is it normal to take so long? If not, what can I do to fix it?

If I tell it to stop the scan then it says "This scan has never been completed. No threats found. Issues detected." What issues? Quarantine Manager says nothing...?!

If I tell it to start the scan then it start at 1,3xx,xxx files and counts down rapidly like it did the first time. However, the mysterious 'Issues detected' text is missing.

What's going on and how can I determine what the issues are?



This thread was automatically locked due to age.
Parents
  • Yeah, so after restarting the scan then it goes through about 1 million files in an hour or so but then starts to go really slow when it gets down to 3xx,000 files. And the 'Issues detected' text is back... but how to see what they are?!
Reply
  • Yeah, so after restarting the scan then it goes through about 1 million files in an hour or so but then starts to go really slow when it gets down to 3xx,000 files. And the 'Issues detected' text is back... but how to see what they are?!
Children
No Data