Sophos Agent fails to start with Error 1067 "Process Terminated unexpectedly"

  • Article ID: 121152
  • Rating:
  • 19 customers rated this article 5.4 out of 6
  • Updated: 03 Oct 2014


The Sophos Agent service repeatedly fails to start either manually, as part of corrective action or as part of system start-up.

As a result the following symptoms may be observed:

  • Event ID 67860 is logged by the 'Service Control Manager' in the System Event log with a message similar to:

The Sophos Agent service terminated unexpectedly. It has done this 26 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

  • The endpoint shows as out-of-date in the console and is unresponsive to actions such as: scan now, comply with policy, update now, etc..
  • If this issue occurs with the 'Sophos Agent' service on the management server, it can result in multiple computers showing as out of date as a result of the Sophos Update Manager status message not being processed .

Note: This issue does not affect the endpoint or server's ability to update and maintain protection; it affects the endpoint or server's ability to send and receive messages that are generated by the various endpoint components such as Sophos Anti-Virus, Sophos Update Manager, AutoUpdate, Patch Assessment etc.

First seen in

Sophos Anti-Virus for Windows 2000+


Failure of the Sophos Agent to start is typically caused by one of the Sophos Agent adapters or their corresponding policies to have become corrupt.

The adapters are how the various endpoint modules such as Sophos Anti-Virus, AutoUpdate, Patch Assessment etc, send and receive messages to and from the Message Router which in turn communicates back to the Sophos Enterprise Console server.

What To Do

The most likely cause is the corruption of the Sophos AutoUpdate agent adapter policy during shutdown of the computer.  To resolve this issue do as follows:

  1. Upgrade to SAV 10.3.11 - This version has a fix which will enable the Sophos Agent service to start if it encounters a 0 byte file. As a result it will enable the client to re-fetch the updating policy to correct the locally cached policy file. 

If you are unable to upgrade to this version, follow the steps below:

  1. Browse to the following location:
    • Vista+: C:\ProgramData\Sophos\Remote Management System\3\Agent\AdapterStorage\ALC\ 
    • XP/2003: C:\Documents and Settings\All Users\Application Data\Sophos\Remote Management System\3\Agent\AdapterStorage\ALC\
  2. Check the file size of SAUPolicy.
  3. If this file is 0kb in size, delete the file.
  4. Start the "Sophos Agent" service, it should start without issue.
  5. A new SAUPolicy file should be generated within 30 seconds. This file is typically ~9kb in size.

If the Sophos Agent service still does not start, please contact Sophos Technical Support after performing the following steps, provide them with an explanation of your issue, and what you have attempted so far.

  1. Restart the system.
  2. Open the Registry Editor. See KBA 10388 for more information.
  3. Browse to the following registry key:
    • 32-bit: [HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Remote Management System\ManagementAgent]
    • 64-bit: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\Remote Management System\ManagementAgent]
  4. Create a new DWORD value named 'LogLevel'.
  5. Change its value to 2.
  6. Install and start Process Monitor (please see KBA 119038 for instructions on generating a normal Process Monitor log).
  7. Attempt to start the 'Sophos Agent' service (make note of the time you attempted to start the service and if the results differ from the previous 1067 error).
  8. Stop Process Monitor.
  9. Save the Process Monitor log with all events and compress the .PML into a .zip.
  10. Gather a Sophos Diagnostic Utility (SDU) archive.
  11. Send the SDU and Process Monitor log archive to Sophos Technical Support.

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent