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.
I had a similar problem after Every Hitman Pro Update, However my scenario was
==> Windows 10 Systems ==> Overall 4000+ Errors ==> Only Restart Event Fixed the error Whenever PC Was Shutdown and Turned Back On==> Error Stayed Back
Then Someone was Kind enough to let me know the FAST START UP Option on Windows 10 and How it Conflicted With HITMAN PRO (HitmanPro uses a kernel mode driver) and Fast Startup Puts the PC ON Sleep Mode During Shutdown and not really Reload the OS from Scratch for kernel Drivers to Reload and HMPRO Upgrade to Complete
https://support.microsoft.com/en-us/help/4011287/windows-updates-not-install-with-fast-startup
https://www.wintips.org/how-to-turn-off-fast-startup-in-windows-10-8-and-8-1/
I Disabled Fast Startup via GP on Systems and Errors were down to 10% from 70% and they are still going DOWN.
I Hope This Helps In Case You have a Same problem.
1. Please RESTART a SYSTEM From Start Menu and Check (Do Not SHUTDOWN & TURN ON)
2. Check Sophos HitmanPro Alert install(%windir%\Temp\
OK Update time ...........
Tried this :
If the 'Restart needed' message does not disappear following a restart of the endpoint
If the computer is still requesting a restart, then manually remove the following 'VolatileFlags' registry key and then force an 'Update now':
Note: Removal of these registry keys does not remove the requirement for a reboot and should only be done if the 'Restart needed' message has not cleared following a restart of the computer.
This doesn't work either - half of the devices that I am accessing to modify the registry (as Admin) on - are already missing this particular registry key (Volatileflags) !!
What does this mean ?
Hello Weeboo,
as mentioned if it stubbornly persists you'd have to check the logs.
The (verbose) ALUpdate log might have an associated message, if it's not clear from it which component requests the restart you'd have to check the Install logs in %windir%\Temp\.
Christian
QC said:Hello Weeboo,
as mentioned if it stubbornly persists you'd have to check the logs.
The (verbose) ALUpdate log might have an associated message, if it's not clear from it which component requests the restart you'd have to check the Install logs in %windor%Temp\.Christian
OK Have managed to run REGEDIT and have removed the VOLATILEFLAGS keys from 2 PCs and have run UPDATE with no change in the error state of either of them
They are both still showing "Restart needed for updates to take effect............." after 24 hours of waiting !!
What else can I try ?
Hello Weeboo,
you don't have to run anything - it has already run often enough. Please check the logs.
In %ProgramData%\Sophos\AutoUpdate\Logs\ are the ALUpdate201803....logs. In some cases (e.g. when VolatileFlags is present) they can tell the reason for the Reboot required ... message. In other cases an installation log (e.g. Sophos Endpoint Defense Setup ....log in \Windows\Temp\) indicates this requirement (in SED's case it says: WARNING : A reboot is required for the upgrade/downgrade to take effect).
Christian
