This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I'm trying to update to the latest Win10 update released on 8/8/22. Ever since that update was downloaded the machine hangs
on the required reboot after the install. I have disabled updates until I can find a fix. I've tried to download the update and install
manually but get the same results. Other updates, such as .NET, download and installed fine. Once the machine hangs it has to be rebooted
2 times to get to the automatic roll back. At least that works for now. I've run the Update trouble shooter and it doesn't fix anything.
Windows Update and BITS services are both set to automatic.
There is an error in the event log but I think its from the install abort from a forced shutdown.
Installation Failure: Windows failed to install the following update with error 0x800F0845: 2022-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5016616).
Update 10/5/22: KB-5017308, KB5017380, KB5018410 also FAIL in exactly the same manner as KB-5016616. Spinning dots on the reboot and the need to do a dual boot auto recovery. Title has been updated.
Any help would be appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
For me, the following solved the Problem:
Delete the Value data (all bytes) of
HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\CurrVal(Default)
and
HKEY_LOCAL_MACHINE\SECURITY\Policy\Secrets\NL$KM\OldVal(Default)
One reboot and CurrVal(Default) should be filled again.
If you are not domain-joined, i would not expect any problems.
I'm not giving directions on how to access and delete the value data because i want skilled people who know what they are doing to test my solution.
Thanks glezbsg - pointer to Setup log - and also Events log. Spent ages looking there, especially Events. Many messages about KB5016616 and other errors - but nothing that seems to provide much light.
But - just a thought: the odd thing is the prevalence of old ex W7 PCs - but not exclusively.
So, just possibly - the SMB protocol? Used to be widely used for file sharing across the network (Homegroup etc), but mainly now superceded, and normally not Enabled in W10. But I use it to allow access to an older (2012) NAS. Makes it and its folders visible under Network view to map drives. MS often deprecate its use as security issue., so defaults it off. Check the settings under Control Panel / Programs and features / Turn features On & Off / SMB....
My settings are:
Does this fit the pattern of those with 5016616 fails?
And, Peter Bisco, if you're going to take the time to try with a spare disc (and end up with much of you stuff gone, - better just to try a clean install? Checks whether there is actually anything on your PC as opposed to the old W10 legacy? I shall as soon as I can find the time.
Hi people,
I have exactly the same problem here. It is ancient laptop HP ProBook 4530s
(Intel Core i5-2450M 2.5GHz, 4GB RAM, of course migrated to SSD).
It was not clean installed, but upgrade from Windows 7 Pro x64 was performed
(after removing HP incompatible bloat software and Intel RST drivers).
System is booting in legacy mode with MBR disk with classic HP four partition layout (BOOT, WINDOWS, HP_RECOVERY, HP_TOOLS).
Everything was running smoothly for few years, including installing Win10 cumulative updates until 2022-08 came.
Machine installs the update (from WU or MSU manually) and after required reboot it waits forever with spinning white dots.
Tried every common troubleshoot step:
Problem was firstly mitigated by hiding the 2022-08 Windows cumulative update.
When 2022-09 Windows cumulative update was released, problem appears again.
Now the problem was mitigated by switching WU to ask before downloading updates through group policy.
As I read this thread, it seems that this problem affects very different computers:
If I will have some spare time, I will try to clone the system to second drive and then try to remove
as much software, files and drivers as possible to bring OS back to "nearly clean" state and check
if updating fails or works and then post some results.
Well this is interesting. I thought there may be logs of the install somewhere to help us figure out where its hanging. I started looking with the Event Manager | Setup logs. I was surprised to find KB-5017308 was installed properly after the reboot even though it was an automatic repair??? And the update still shows its hidden.
What I did was to try a manual update and had to do the recovery as previously reported. Then I went to the update settings page and pressed the download button for all updates including KB-5017308. While other updates were installing and after the download, I deleted KB-5017308's installation cab file from C:\Windows\SoftwareDistribution\Download. Now the update doesn't show as being required but is hidden.
The update does not appear in Control Pannel | Programs and Features | Installed Updates | Windows
This is from my manual try to update it that caused the reboot hang:
Windows update "Security Update for Windows (KB5017308)" was successfully installed. (Command line: "C:\windows10.0-kb5017308-x64_2027053968a06948b45d139d95475ab4feee5654(1).msu" ")
Windows update Security Update for Windows (KB5017308) requires a computer restart to complete the installation. (Command line: ""C:\WINDOWS\system32\wusa.exe" "C:\windows10.0-kb5017308-x64_2027053968a06948b45d139d95475ab4feee5654(1).msu" ")
