0000006d 'Restart needed for updates to take effect' - alert does not clear following reboot

  • Article ID: 31540
  • Rating:
  • 9 customers rated this article 3.8 out of 6
  • Updated: 17 Feb 2014


The following message is shown:

  • One or more endpoint computers report to the console:
    0000006d Restart needed for updates to take effect

  • In the endpoint's ALC.log file you see the following:
    WARNING: Restart needed for updates to take effect

Having rebooted the computer, even multiple times, the alert remains as outstanding.

Important: Sophos AutoUpdate (as released with Sophos Anti-Virus 10.0.7 in August 2012) changed the mechanism for storing the 'Reboot Required' state on the endpoint.  The registry value that now records this state is now created under the following volatile key:

  • 64-bit: HKLM\SOFTWARE\Wow6432Node\Sophos\AutoUpdate\UpdateStatus\VolatileFlags\
  • 32-bit: HKLM\SOFTWARE\Sophos\AutoUpdate\UpdateStatus\VolatileFlags\

A volatile key means the information is stored in memory and is not preserved when the corresponding registry hive is unloaded. For keys under HKLM, this occurs only when the system initiates a full shutdown.  This guarantees that the key will be cleared on reboot and the correct state reflected in the console following the next update.

First seen in

Enterprise Console 3.0


Despite having rebooted, the first update following a restart is required to occur in order to send back an updated update status.

What to do

Following the restart, ensure that the computer has performed an update and the last message time for the computer as shown in Enterprise Console is recent.  

If this issue persists ensure you are running Sophos AutoUpdate or later and that communication from the computer to the management server via Remote Management System (RMS) is functioning correctly. 

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

Rate this article

Very poor Excellent