Sophos Anti-Virus for Mac Home Edition

[AMC3]

Is Sophos Anti-virus for Mac compatible with Lion? The description does NOT mention OS 10.7.  I just upgraded to Lion and suddenly this software is malfunctioning. Is Sophos behind on keeping up with Apple's current OS?  Really?

[AMC3]

I updated my signature to reflect my current OS.

[Agile]

Which version of SAV are you running?  SAV for Mac HE 8.0.3C and 7.3.12C are both Lion compatible (all versions).

What issues are you having?  Does a search on here indicate others with a similar problem/solution?

[AMC3]

I am running SAV for Mac Version 8.0.4C

Threat detection engine: 3.32.0

Threat data: 4.78

I just uninstalled the earlier version and reinstalled this one off a fresh download. However, the "On-Access scanner" is still OFF. It will not let me turn it back ON.

[AMC3]

And, as before, I am getting a " Sophos Anti-Virus Error" mesage saying "Sophos Anti-Virus is not running."

[AMC3]

Just to add some info, I have this software installed on another MacBook and it is working fine. The On-Access is ON and could be turned ON or OFF, unlike the software on my MacBook Pro. As far as I can tell, the software IS working in Lion... just not on my MacBook Pro now. How do I get this software preference reset?

[AMC3 · Accepted solution]

Andrew, I found this note from you regarding the same issue about a year ago. Still good advice? I assume so and will do a restart.

Re: On-access scanner no longer running

06-30-2011 04:45 PM

For all other users I've been in contact with, the issue was resolved by letting autoupdate complete another update and/or selecting update now and then re-enabling on-access scanning.

Personally, I have got myself into a position before where I killed InterCheck through some convoluted skullduggery and got into the situation you describe... I was able to fix it that time by ensuring on-access was disabled (not hard when it won't allow anything else), rebooting the computer, running an update check, and then re-enabling it.

[AMC3 · Accepted solution]

For all other users I've been in contact with, the issue was resolved by letting autoupdate complete another update and/or selecting update now and then re-enabling on-access scanning.

Personally, I have got myself into a position before where I killed InterCheck through some convoluted skullduggery and got into the situation you describe... I was able to fix it that time by ensuring on-access was disabled (not hard when it won't allow anything else), rebooting the computer, running an update check, and then re-enabling it.

[Agile]

Still good advice; I don't think the autoupdate mechanism has changed that much.

[AMC3]

Basically, it looks like RE-BOOTING is the solution.