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
  • It did the same thing to Snow Leopard.  Finder (not reponding).  Everything hung up.

    Restarting did not fix the problem for me.

    I thought the problem was the new wireless router I installed a couple of days ago.

    Spent all morning trying to "fix" the router . . . finally got everything working again and left the machine. 

    While I was gone Sophos finished its update.

    Not really happy that my whole day was wasted by this.

    I thought I had it set to tell me before doing something like this, but apparently not.

    Anyone know how to keep this from happening again in the future?

    :1008237
Reply
  • It did the same thing to Snow Leopard.  Finder (not reponding).  Everything hung up.

    Restarting did not fix the problem for me.

    I thought the problem was the new wireless router I installed a couple of days ago.

    Spent all morning trying to "fix" the router . . . finally got everything working again and left the machine. 

    While I was gone Sophos finished its update.

    Not really happy that my whole day was wasted by this.

    I thought I had it set to tell me before doing something like this, but apparently not.

    Anyone know how to keep this from happening again in the future?

    :1008237
Children
No Data