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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-12-21T17:32:01+00:00
    FWIW... <br><br>At least MS has now acknowledged this issue: "Microsoft is working on a resolution and will provide an update in an upcoming release."<br><ul><br><li><span><a href="https://www.askwoody.com/2017/microsoft-confirms-bugs-in-this-months-win10-1709-cumulative-update/" target="_blank" rel="noreferrer">Microsoft confirms bugs in this month’s Win10 1709 cumulative<br> update @ AskWoody</a> </span></li><li><span><a href="https://support.microsoft.com/en-us/help/4054517/windows-10-update-kb4054517" target="_blank" rel="noreferrer">December 12, 2017—KB4054517 (OS Build 16299.125)</a><br></span></li></ul>

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-12-21T19:55:40+00:00

    According to windows update, not only KB4054517 says "awaiting restart" and restarting wont install it. But another has come out, KB4058043. Same issue, awaiting restart and restart wont install it.

    On both my PCs I might add.........

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-12-21T20:23:14+00:00

    Yes finally MS ack the issue.  see  https://support.microsoft.com/en-us/help/4054517/windows-10-update-kb4054517

    But MS adds to confusion by stating in last paragraph ""You can also type About your PC in the Search box on your taskbar to confirm that your device is using OS Build 16299.15.""  I believe the build should be 16299.125

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-21T20:57:00+00:00

    Hi Rick.

    Thank you do much. I have been on this link before. (Added to favourites)  MS has now add issues. I was not aware of.

    Will try to get through the workaround. All these issues rake place on my machine. First have to gain free space of 30 GB since 24 seems to less. I'll reply after workaround.

    JOHN

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-12-21T21:51:39+00:00

    had to do a repair I installation. )

    I recognized that all MICROSOFT software was simply gone on the C-partition.

    Sounds like you missed a step of an ISO Upgrade Repair and accidentally did a full install with it.

    Just to put you in the picture what Microsoft regard a repair installation retaining software and settings.

    I myself managed to get out of the infernal reboot dilemma by clearing out all temp files, doing a complete disk cleanup including system files (3 GB accumulated!) plus deleting files from Windows\SoftwareDistribution\Download. Then all I had to do was double-click the downloaded.... msu file and installation went like a charm. What I did was probably crude, but it worked.

    Another chap, same problem as of all us here, used the repair method and found that of all things, Microsoft managed to corrupt Microsoft Office installation. So much for retaining software!

    Was this answer helpful?

    0 comments