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

On-access scan self disabled and would not be turn on again

Hello there, I have installed Sophos MacHome AV few days ago on my macbook (OSX 10.6.8) few days ago and today while I was working in Firefox (11.0) a pop-up window appeared, saying that on-access scan had been disabled. Indeed, the S icon in the menu bar was grayed, but when I opened Sophos preferenca panel I would not be offered the possibility of turning it back on. Clicking the restore default button also did not work, all I got was a message saying that preferences for on-access scan could not be restored to factory setting.

It might be just a coincidence, but this happened as soon I had blocked on outgoing connnection using Internet Cleanup (in particular, I blocked ksurl, a process that started to show up ever since I have installed Google Chrome browser).

After rebooting, on-access scan was initialy disabled but went back to normal after about one minute.

Any idea if this was just an oddity or an indication of some problem (compatibility, may be?) in my specific architecture?

thanks!!

:1006275


This thread was automatically locked due to age.
Parents
  • I can confirm this.

    1. Did the uninstall via the Sophos Remove app.

    2. Restarted the Mac. 

    3. Downloaded the newest version of Sophos.

    4, Profit !

    The On-access scanner immediately started working, and has stayed active with no self-quits. My suggestion to the Sophos crew is to keep a lid on the update files. In other words, after XX days, the old files are deleted by the updater. Either that, or take the lazy way out and just tell people to run Sophos Remove and re-install. 

    :1007593
Reply
  • I can confirm this.

    1. Did the uninstall via the Sophos Remove app.

    2. Restarted the Mac. 

    3. Downloaded the newest version of Sophos.

    4, Profit !

    The On-access scanner immediately started working, and has stayed active with no self-quits. My suggestion to the Sophos crew is to keep a lid on the update files. In other words, after XX days, the old files are deleted by the updater. Either that, or take the lazy way out and just tell people to run Sophos Remove and re-install. 

    :1007593
Children
No Data