Windows 10 Cumulative Update KB4054517 fails to install error 0x80070643

Anonymous
2017-12-12T19:55:01+00:00

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.

0 comments

230 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-12-16T23:15:40+00:00

    Ugh, I swear, in the 2.5 years I've been dealing with Win10 it seems that one thing is pretty consistent.... another update, another problem that users have to consume time to figure out how to fix.

    I have 3 devices, HP DV7, ASUS X550L (both 2+ y/o) and a MS Surface 6 months old.  The older devices have definitely had their share of problems with 10 but have successfully installed all updates thus far up through V 1709, 16299.125.  However, the Surface has now failed to install KB4051963 & 4054517. 

    Based on my experience, I would disagree with the "corrupted files" statement.  The files were not corrupted before these updates.  If any device should successfully install updates is should be the Surface.  

    The fact that users are reporting this issue here says it all. I guess the only option is to sift through the user comments and try to find something that will work.

    Not happy :(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-12-16T15:03:37+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 might work for any failed update, couldn't say for sure as this was my first failed update

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-12-16T04:23:13+00:00

    The interesting thing is that there are several other updates that don't always show up. It seems that somehow Microsoft is determining which computer is trying to update and then customizing which updates to install. My computer is now successfully on build 1699.125 after using the Media Tool. It has KB4054517 installed, but also KB4055237, KB4055994, and KB4057247. These are all supposed to enhance the update process for computers running the Fall Creators update. It never did have KB4051693 installed. That was probably the problem with KB4054517 not installing. Microsoft needs to be more transparent in this stuff. Going through the hassle each time there is a cumulative update could get old.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2017-12-15T17:58:15+00:00

    10 times the update failed after reboot on 99% - the system was rolled back then.

    I've tried everything - sfc /scannow + DISM, running both of the troubleshooters, stopping the Windows Update service +  cleaning catroot2 and Software Distribution folders, uninstalling the update (it was listed as installed but the build was still 16299.64)

    • using the offline installer.

    Nothing works, 10 times error 0x80070643, now error code 0x800f0922.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2017-12-15T17:20:12+00:00

    So, I had the same issue. I worked with a Microsoft tech on all the usual fixes, no luck. Then we decided to use Windows Media to reinstall. Took about three hours and worked. The reinstalled version has KB4054517 installed. This is better that before the Fall update, when a similar update problem could not be resolved until the Fall update was rolled out. Anyway, reinstalling Windows seems to work.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments