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 scanner no longer running

Today, all of a sudden, my free Sophos Antivirus for Mac warned me, that the on-access scanner no longer was running. I tried to restart it from within the Preferences, but get an error message that this could not be done.

Whats wrong and how can this problem be solved? (Tried to uninstall and reinstall but the error persisted)

:1003257


This thread was automatically locked due to age.
Parents

  • 1MacGeek wrote:

    This fails for my set-up.

    Everything was going along swimingly until today, Sophos just announced it was shutting down with no warning, so I removed it, restarted, download the new version directly from the Sophos website. One more restart after the install just to make sure... and Sophos just stopped dead again. I have removed and restarted a total of three times, with no luck at all. I note the troubles started after I manually initiated an update. I am toying around with removing any network access to prevent any updating and see if Sophos keeps running. If it does after this latest go, then I think we have the culprit. 

    Sophos reports - in the logs - I am running updater version 8.0.5, and version 4.79, 02 July 2012 on the AV. 


    Ok, step-by-step : 

    1. Using the supplied removal tool, removed Sophos. 

    2. Restarted Mac.

    3. Download (once again) the most recent version of Sophos.

    4. Shut down all network access.

    5. Installed Sophos.

    6. Sopos complained about not being able to contact the MotherShip.

    7. Enabled network access only long enough to make the installer happy (about 5 seconds), then shut it down again. 

    8. Sophos installs with no further error.

    9. On-access scanning once again stops. 

    10. Decide back to the drawing board, turn on network access once again.

    11. Stand all amazed as the on-access scanner goes green the second the network access in enabled. 

    12. Launch manual update of Sophos. 

    13. On-access scanner stays running. 

    Not a superstitious man here, but it's times like this I just back away like the thing is possessed. . . it just makes no sense that three downloads and restarts failed, but the fourth just takes off. I should think the network access removal shouldn't play a part, but at this point... who knows? (shrugs and walks away)

    :1008199
Reply

  • 1MacGeek wrote:

    This fails for my set-up.

    Everything was going along swimingly until today, Sophos just announced it was shutting down with no warning, so I removed it, restarted, download the new version directly from the Sophos website. One more restart after the install just to make sure... and Sophos just stopped dead again. I have removed and restarted a total of three times, with no luck at all. I note the troubles started after I manually initiated an update. I am toying around with removing any network access to prevent any updating and see if Sophos keeps running. If it does after this latest go, then I think we have the culprit. 

    Sophos reports - in the logs - I am running updater version 8.0.5, and version 4.79, 02 July 2012 on the AV. 


    Ok, step-by-step : 

    1. Using the supplied removal tool, removed Sophos. 

    2. Restarted Mac.

    3. Download (once again) the most recent version of Sophos.

    4. Shut down all network access.

    5. Installed Sophos.

    6. Sopos complained about not being able to contact the MotherShip.

    7. Enabled network access only long enough to make the installer happy (about 5 seconds), then shut it down again. 

    8. Sophos installs with no further error.

    9. On-access scanning once again stops. 

    10. Decide back to the drawing board, turn on network access once again.

    11. Stand all amazed as the on-access scanner goes green the second the network access in enabled. 

    12. Launch manual update of Sophos. 

    13. On-access scanner stays running. 

    Not a superstitious man here, but it's times like this I just back away like the thing is possessed. . . it just makes no sense that three downloads and restarts failed, but the fourth just takes off. I should think the network access removal shouldn't play a part, but at this point... who knows? (shrugs and walks away)

    :1008199
Children
No Data