error code 0x800f0922.
That one shows up in CBS.log but it may be in an archived portion of it.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We just got our "second Tuesday" updates (12/12/2017) on our W10 machine running V1709.
The cumulative update KB4054517 failed with an error code of 0x80070643.
The only thing we've discovered so far is that this machine will not display our other 3 PC's on the network when we select "Network" in File Explorer. But all three other PC's can "see" and access this PC no problem. And we ran a batch backup job on the affected PC and it was able to copy files from all three other PC's. So it's just a display problem in File Explorer -> Network.
We've run Windows Update Troubleshooter and told it to Apply Fixes whenever it prompted us, and it DID report that it found and fixed three issues:
Potential Windows Update Database Error - Fixed
Windows Update Component Must Be Repaired - Fixed
Check for pending updates - Fixed
After exiting the Troubleshooter, we clicked on "Check for Updates" again and it said "Your device is up to date".
We noticed that the build number after the "failed" update had changed to 16299.125. So the system thinks it DID install something newer than it had before, but Windows Update thinks the cumulative patch failed to install.
BTW, the other "Second Tuesday" patches (Adobe Flash KB4053577 and Windows Malicious Software Removal Tool KB890830) both installed OK.
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.
error code 0x800f0922.
That one shows up in CBS.log but it may be in an archived portion of it.
I have the same problem, tried different solutions, going back to a restore point, but then the update comes again and with the same failure
I had error 0x8024200d with KB4054517.
0x8024200D WU_E_UH_NEEDANOTHERDOWNLOAD The update handler did not install the update because it needs to be downloaded again.
Go figure!? Windows Update History states that the install failed on 12/12/17!
A possible explanation of your symptoms is that an interferer allowed the update to download and install but not apply. E.g. the apply phase would occur during a subsequent reboot.
To check on that possibility see if you get any additional clues from sfc /scannow
Someone mentioned Norton, an interferer, then it might be necessary to uninstall that (and any other similar products) in order to avoid the possibility that any of the three phases of the update process not be affected negatively. Realize that with a cumulative update you are essentially modifying the whole OS so it is not difficult to see that permitting something to interfere with that process is likely to at least cause a significant performance hit, if nothing else that would be worse.
FYI
Robert
Same thing with what you did and almost all the other comments on this topic.
I have 2 other computers that didn't have any problems, one is 3 months old (Windows 10 home version), the other is a year and a half (Windows 10 Pro) and the failure occurred on a 2 year old computer (Windows 10 Pro), so they are not out of date old technology.
Each had a full virus scanned by Norton, with clean results.
The other updates that came with KB4054517 installed correctly.
The computer that had an unsuccessful KB4054517 update runs fine, but not if I do a restart. I must do a shutdown and then turn it on again. If I do a restart the computer try to install the update which fails after an hour or so.
I did a full recovery clean re-install, and the problem still exists.
Me too. Carried out the reset recovery procedure (with keeping files option) twice but the update KB4054517 stops at "status: Installing - 99%". If I do a restart, it takes a very long time for the "getting windows ready" message to go away. The update status issue remains each time. So I don't shut my computer down. Now I have the message, again after a very long time, "There were some problems installing updates, ........................ etc., error code 0x800705b4". Retry.