Didn't work for me
Windows 10 Cumulative Update KB4054517 fails to install error 0x80070643
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.
Windows for home | Windows 10 | Windows update
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.
230 answers
Sort by: Most helpful
-
Anonymous
2017-12-15T04:39:20+00:00 -
Anonymous
2017-12-15T04:02:58+00:00 I've been getting an issue as well.
The following is from the error detailed in event viewer:
Installation Failure: Windows failed to install the following update with error 0x800F0845: 2017-12 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4054517).
I'm running Windows 10 Pro (64 bit) v. 1709 build 16299.98.
I've been having random freeze up glitches since I installed FCU and I cannot pinpoint what's causing the error due to insufficient data.
I decided to install the update in question and I was presented with the error mentioned in this article post.
I didn't recognize anything in event viewer during the first occurrence. Just today, I forgot the update installed itself and when I happened to reboot, it started applying the update. Yet again, I receive a boot loop, an auto repair screen, and a status of "We could not complete the installation. Undoing changes" upon the final stable boot.
The difference this time was that when I checked even viewer, I found this nasty little bugger:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xffff84846a680080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 72f3b9d8-66fd-42c9-8f57-4bad9f38c83f.
Something caused the kernel to flop from what I can tell. I can only assume at this point that there's a driver conflict for the FCU glitch. As for this now cumulative update error, I have no clue. Seeing as how I'm not the only one, I can only infer that Microsoft didn't provision the update correctly.
-
Anonymous
2017-12-15T00:01:24+00:00 Error 0x80070020
PS>net helpmsg (0x20)
The process cannot access the file because it is being used by another process.
More possible interference.
-
Anonymous
2017-12-14T23:28:54+00:00 KB4054517 keeps trying to install then undoes the installation after 7 minutes or so of grinding.
Error 0x80070020
My build is Win10 1709 Build 16299.64
Nothing has fixed the problem.
I have a different build # than has been mentioned. And a different error.
I'm hoping someone knows what I can try.
-
Anonymous
2017-12-14T21:58:22+00:00 I had error 0x8024200d with KB4054517. I ran the 'Check for updates' in Windows Update and it kept coming back with the status message that I was up-to-date. So I went to the Microsoft Update Catalog webpage for KB4054517 and downloaded the .msu file particular to my machine. I ran the Stand-alone Installer and it came back with the message 'Security Update for Windows (KB4054517) is already installed on this computer'. Go figure!? Windows Update History states that the install failed on 12/12/17! I guess I'll wait and see what happens.