Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 21 replies
  • Subscribers 3 subscribers
  • Views 43900 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 (0x000006d)"

Weeboo

We are seeing this error on 260 devices (increasing) on our network

Enterprise console 5.5.0

Has Sophos pumped out an update to cause this or is there some other reason ?

I have checked my own PC (Which is included in the ones at "error") and see absolutely no problem with my Sophos installation...

What is going on here ?



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

    Are those devices Windows 10 devices with Fast Boot enabled? If so, shutting down does not really shut them down.

    Fast Boot can lead to a lot of strange start behaviors like not applied policies or the mentioned issue.

    I recommend to disable Fast Boot (unfortunately it returns with each Feature Update, so you would have to set the registry key to disable, maybe per GPO). Strange enough, that Windows 10 has a GPO to Force using Fast Boot, but none to disable.

    Best greetings from Germany
    Olaf

  • 0 in reply to Olaf Engelke

    Olaf Engelke said:

    Are those devices Windows 10 devices with Fast Boot enabled? If so, shutting down does not really shut them down.

    Fast Boot can lead to a lot of strange start behaviors like not applied policies or the mentioned issue.

    I recommend to disable Fast Boot (unfortunately it returns with each Feature Update, so you would have to set the registry key to disable, maybe per GPO). Strange enough, that Windows 10 has a GPO to Force using Fast Boot, but none to disable.

    Best greetings from Germany
    Olaf

     

     

    I have been searching on-line and it appears that MS have not offered the option within GPO to "disable" fastboot - or HIBERBOOT - Only to "enable" it

    Any further help welcome

    Thanks

Reply
  • 0 in reply to Olaf Engelke

    Olaf Engelke said:

    Are those devices Windows 10 devices with Fast Boot enabled? If so, shutting down does not really shut them down.

    Fast Boot can lead to a lot of strange start behaviors like not applied policies or the mentioned issue.

    I recommend to disable Fast Boot (unfortunately it returns with each Feature Update, so you would have to set the registry key to disable, maybe per GPO). Strange enough, that Windows 10 has a GPO to Force using Fast Boot, but none to disable.

    Best greetings from Germany
    Olaf

     

     

    I have been searching on-line and it appears that MS have not offered the option within GPO to "disable" fastboot - or HIBERBOOT - Only to "enable" it

    Any further help welcome

    Thanks

Children
  • +1 in reply to Weeboo

    You can create a Group Policy Preference setting to Replace the appropriate registry value:

    In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power

    Set the value of HiberBootEnabled to 0

    and then apply this policy to your computers.

    Best greetings from Germany
    Olaf

  • 0 in reply to Olaf Engelke

    Olaf Engelke said:

    You can create a Group Policy Preference setting to Replace the appropriate registry value:

    In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power

    Set the value of HiberBootEnabled to 0

    and then apply this policy to your computers.

    Best greetings from Germany
    Olaf

     

     

    Thanks Olaf, much appreciated

Unfiltered HTML