did u get it installed yet? i finally did by luck i think.
Windows 10 Cumulative Update KB4054517 fails to install error 0x80070643
![](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)
Anonymous
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-18T18:50:30+00:00 -
Anonymous
2017-12-18T15:10:14+00:00 Same Problem here i can install the Update on a fresh installed windows on every reboot the Update fails
-
Anonymous
2017-12-18T10:17:56+00:00 It was a nice try but it didn't work for me. I still see a restart pending and a restart button in Settings > Updates and still cannot install the update myself. Do you know any way to actually delete the updates files manual?
-
Anonymous
2017-12-18T02:21:08+00:00 Here is an easy fix to a failed KB4054517 update
- Go to Settings > Update & Security > Windows Update > click Viewed installed update history
- Click Uninstall updates
- Click Security Update for Microsoft Windows (KB4054517)
- Click Uninstall (this might take a while)
- Reboot (it'll say it's updating)
- After it reboots go to Go to Settings > Update & Security > Windows Update > Check for updates
- KB4054517 is shown as an update
- Update > it reboots and installs the update
- After rebooting go to Settings > Update & Security > Windows Update > click Viewed installed update history
- KB4054517 successfully installed
- OS Build 16299.125
This worked for me on the 6 month old MS Surface. Thanks!
It would be good for Microsoft to explain why uninstalling and reinstalling this update corrects the problem when it should have successfully installed initially.
-
Anonymous
2017-12-17T20:23:19+00:00 Finally got it updated. But can't really say how, as I think it happened out of luck. First I followed some steps posted here. The Uninstall method then rebooted. After that I didn't get the update from Windows Update, instead I downloaded it from microsoft. Installed it then rebooted again. After that, tried installing some programs but ended up uninstalling them. Instead of uninstalling what I did was System Restore but not inside Windows but from the UEFI. That advance restart thing in Update & Security. Once System Restore was on screen, there was an entry called "Windows Installer Module" or something, not sure in English. Restored to that point and magically, after it forced me to reboot as every System Restore, it updated.
So I don't think that the method I did to work things out is applicable to you guys, but props to the help I received from this forum/site rather than the Microsoft Paid guys that can't help. I know that the method used by me is not specific but out of sheer luck. Maybe System Restore did something else or something. But yeah, thanks!