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

Latest pre-release of 10.11.4 breaks Sophos AV Home Edition

The problem that existed prior to the release of 9.4.1 is back with the latest version of El Capitan that has just been pre-released 10.11.4 Beta (15E27e). The Sophos icon remains dimmed in the menu bar with the error On-Access Scanning Is Disabled. Could someone in engineering please take a look at this?



This thread was automatically locked due to age.
Parents
  • To add to this, On-Access Scanning will be disabled but the Start Scanning button will be enabled. Clicking it will change the button to Starting... but then generate an error: Sophos Anti Virus is not running.

    Oddly, if System Integrity Protection is then turned off in Recovery mode, after a reboot, On-Access Scanning is now on and working without further action. However, if SIP is enabled, after reboot, it's off again. And when the Start Scanning button is clicked, its legend changes to Stopping... The SAV not running error is generated again, though it seems to have taken longer.
Reply
  • To add to this, On-Access Scanning will be disabled but the Start Scanning button will be enabled. Clicking it will change the button to Starting... but then generate an error: Sophos Anti Virus is not running.

    Oddly, if System Integrity Protection is then turned off in Recovery mode, after a reboot, On-Access Scanning is now on and working without further action. However, if SIP is enabled, after reboot, it's off again. And when the Start Scanning button is clicked, its legend changes to Stopping... The SAV not running error is generated again, though it seems to have taken longer.
Children
  • Thanks for your comments. I just tried their new product, Sophos Home, and still end up with a dimmed icon. I've reported this as a bug to Apple, but I hope that the Sophos engineering team will investigate this on their own with this pre-release to see what happened to have this issue reoccur. In the meantime, I guess I don't have any AV protection.