Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 22386 views
  • Users 0 members are here
Options
Suggested
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

"Restart needed for updates to take effect"

Weeboo

We are seeing large numbers of devices with this error on our network on the Enterprise console

What is the solution because when I remotely reboot the devices - the error remains !!



This thread was automatically locked due to age.
Parents
  • 0

    Hello Weeboo,

    there's this one article about a persistent restart message.  Has there been an upgrade or some other change recently?

    Christian

  • 0 in reply to QC

    No - nothing has changed - just the ever increasing numbers of endpoints with this error

    I first noticed the error about a month ago - the numbers are increasing daily now !

    Enterprise console 5.5.0

    Endpoints 10.7

  • 0 in reply to Weeboo

    Hello Weeboo,

    might or might not actually be a Sophos issue, Windows does not show that a reboot is required, does it? In this case there'd be the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired key.

    If you can identify an endpoint that has "just" started to display this message please check the ALUpdate logs, this will perhaps indicate what triggers this status. IIRC the log will mention the VolatileFlags key if it's involved.
    Also check the PendingFileRenameOperations value under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager though AFAIK it isn't taken into account on "minor" updates. When a Sophos component (e.g. SAVXP) "recommends" a reboot it should appear around the same time for all endpoints, but nevertheless you could also check the installation logs in %windir%\Temp.

    Christian

Reply
  • 0 in reply to Weeboo

    Hello Weeboo,

    might or might not actually be a Sophos issue, Windows does not show that a reboot is required, does it? In this case there'd be the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired key.

    If you can identify an endpoint that has "just" started to display this message please check the ALUpdate logs, this will perhaps indicate what triggers this status. IIRC the log will mention the VolatileFlags key if it's involved.
    Also check the PendingFileRenameOperations value under HKLM\SYSTEM\CurrentControlSet\Control\Session Manager though AFAIK it isn't taken into account on "minor" updates. When a Sophos component (e.g. SAVXP) "recommends" a reboot it should appear around the same time for all endpoints, but nevertheless you could also check the installation logs in %windir%\Temp.

    Christian

Children
No Data
Unfiltered HTML