Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 6 subscribers
  • Views 4092 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

'A different UUID is already loaded' - help!

macuser62442

Hi all. I searched this forum and didn't find any topics in which this particular concern
was addressed, but I hope I'm not being repetitive by posting this. I'll try to be concise
but thorough. If this has been answered, please do point me in that direction. Thanks!

Now then:

Just downloaded Sophos for OS X 10.8.4, Build 12E55. About window says
version 8.0.15C, threat detection engine 3.43.10. Performed a full
system scan yesterday. It took about 10 hours to scan about 225GB ---
my machine may have gone to sleep in the middle, as I was out. No threats
detected, cool. But a couple issues have come up.

First, when I got back, even though I had turned my WiFi off via the
menu at the top, next to the clock, it was on when I got home. Any ideas?

Second, and more to the point, on-access scanning is disabled. It has a
red button in the Preferences and is greyed out in the system menu bar
menu, so I can't turn it back on. Then, I get an error message that says
Sophos is not running. I look it up in Console.app, and I see this:

2013-06-26 10:54:15.763 AM com.apple.launchd[1]: (com.sophos.intercheck)
Throttling respawn: Will start in 10 seconds
2013-06-26 10:54:25.811 AM com.apple.kextd[12]: Can't load
/Library/Sophos Anti-Virus/InterCheck.app/Contents/Resources/Sophos
Anti-Virus.kext - a different UUID is already loaded.
2013-06-26 10:54:25.815 AM com.apple.launchd[1]:
(com.sophos.intercheck[9113]) Exited with code: 1
2013-06-26 10:54:25.815 AM com.apple.launchd[1]: (com.sophos.intercheck)
Throttling respawn: Will start in 10 seconds
2013-06-26 10:54:35.868 AM com.apple.kextd[12]: Can't load
/Library/Sophos Anti-Virus/InterCheck.app/Contents/Resources/Sophos
Anti-Virus.kext - a different UUID is already loaded.
2013-06-26 10:54:35.872 AM com.apple.launchd[1]:
(com.sophos.intercheck[9115]) Exited with code: 1
2013-06-26 10:54:35.872 AM com.apple.launchd[1]: (com.sophos.intercheck)
Throttling respawn: Will start in 10 seconds
2013-06-26 10:54:45.924 AM com.apple.kextd[12]: Can't load
/Library/Sophos Anti-Virus/InterCheck.app/Contents/Resources/Sophos
Anti-Virus.kext - a different UUID is already loaded.
2013-06-26 10:54:45.928 AM com.apple.launchd[1]:
(com.sophos.intercheck[9117]) Exited with code: 1
2013-06-26 10:54:45.928 AM com.apple.launchd[1]: (com.sophos.intercheck)
Throttling respawn: Will start in 10 seconds
2013-06-26 10:54:55.976 AM com.apple.kextd[12]: Can't load
/Library/Sophos Anti-Virus/InterCheck.app/Contents/Resources/Sophos
Anti-Virus.kext - a different UUID is already loaded.
2013-06-26 10:54:55.981 AM com.apple.launchd[1]:
(com.sophos.intercheck[9119]) Exited with code: 1

Over and over and over. I'm trying to kill the Sophos AntiVirus, Sophos
AutoUpdate, and Sophos UI Server processes in the Activity Monitor, but
they keep coming back to life. In the meantime, it isn't working, and
that gray shield at the top of the screen makes me sad. I'm logged in
as an admin, if that makes a difference. I just updated
the software, and still no luck. Help?

:1012468


This thread was automatically locked due to age.
  • 0

    Hi macuser62442,

    Thanks for the the very detailed question. The problem you are running into with the On-Access Scanner is one that seems to happen to a small number of systems. What its describing is that our kernel extension won't load because the system thinks it was already loaded. This can happen during an update (although we've had a extremely difficult time trying to reproduce it ourselves).

    We made some improvements in version 9.0 to "try harder" - during an update the software now takes extra steps to try to ensure this situation won't happen. Since we've been unable to reproduce the original problem ourselves, this change to the product is a bit speculative. Its safe, but we aren't able to guarantee it fixes every situation.

    If you are willing to give version 9.0 a try, we'd be very appreciative for feedback about this issue e.g. does it continue to happen for you on future updates.

    Version 9.0 is available as a preview. Look for my post near the top of the board about it, it contains details.

    :1012472