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

Sophos A/V Home Edition update on July 17th cause OS X Lion to hang

Hi there,

Sophos did a self-update today, and it took my primary system (MacBook Pro, OS X Lion fully updated) out completely. It grinds the system to a total halt, spinning multicolour disk, nothing works. Hard power off, have been in through the recovery partition, done a repair disk and repair permissions, upon next boot - as soon as Sophos starts, it takes at most ten seconds and then the system is totally hung again. No app works, can not log in remotely, nada.

How on earth do I recover from this without a clean install?

/Anders

:1008211


This thread was automatically locked due to age.
Parents
  • There seems to be some sort of incompatibility between the latest update to Sophos ( on or around the 17th July) and Little Snitch. I have been having problems ever since Sophos upgraded whenever Little Snitch dialogs are active. The new components are causing lots of prompts for network access to come up and whenever one of these comes up the screen goes blank a few moments later and the computer goes to sleep! Looking at the console it is reporting that 'Previous Sleep Cause 5' which is a user or dialog triggered sleep request ( which I'm certainly not doing!). This can manifest as spinning beachballs or apparent hangs as the system tries to sleep whilst in use, which could be the symptom everyone else is experiencing. Why are there now so many new Sophos modules all trying to do network connections?

    10.6.4 on a mid 2011 iMac

    :1008255
Reply
  • There seems to be some sort of incompatibility between the latest update to Sophos ( on or around the 17th July) and Little Snitch. I have been having problems ever since Sophos upgraded whenever Little Snitch dialogs are active. The new components are causing lots of prompts for network access to come up and whenever one of these comes up the screen goes blank a few moments later and the computer goes to sleep! Looking at the console it is reporting that 'Previous Sleep Cause 5' which is a user or dialog triggered sleep request ( which I'm certainly not doing!). This can manifest as spinning beachballs or apparent hangs as the system tries to sleep whilst in use, which could be the symptom everyone else is experiencing. Why are there now so many new Sophos modules all trying to do network connections?

    10.6.4 on a mid 2011 iMac

    :1008255
Children
No Data