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 No comments

230 answers

Sort by: Most helpful
  1. Anonymous
    2017-12-26T17:16:51+00:00

    I tried everything in this thread with no success.

    I didn't want to do a repair install and risk having to reinstall apps etc, so in the end In the end I resolved it by signing up for the Fast Ring in the Windows Insider Programme. Had to wait a few days, but eventually I checked Windows Update and found that an insider preview was available. I set this to install, and waited for it to install then restarted.

    First time out it failed - it restarted quickly without the usual 'Updating windows...'  messages, and after the restart I went into Windows Update, and sure enough it said it was awaiting a restart - the same as the other updates that had failed. 

    However, I clicked on 'Retry' and this time when it restarted it installed properly, and now Windows Update seems all good. Hope this may help someone who is getting frustrated with this issue...

    Hi RAB1,

    Great news.

    Maybe you can copy the link of the update you refer to and solved yr problem, to help others from their suffering. You might find it discribed just under your update as a link to MS. People can look and manually find it.

    Stronger together !  Thanks for for bringing the solution up here.

    slagtand  (John)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-26T14:31:12+00:00

    I tried everything in this thread with no success.

    I didn't want to do a repair install and risk having to reinstall apps etc, so in the end In the end I resolved it by signing up for the Fast Ring in the Windows Insider Programme. Had to wait a few days, but eventually I checked Windows Update and found that an insider preview was available. I set this to install, and waited for it to install then restarted.

    First time out it failed - it restarted quickly without the usual 'Updating windows...'  messages, and after the restart I went into Windows Update, and sure enough it said it was awaiting a restart - the same as the other updates that had failed. 

    However, I clicked on 'Retry' and this time when it restarted it installed properly, and now Windows Update seems all good. Hope this may help someone who is getting frustrated with this issue...

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-26T07:47:14+00:00

    microsoft is working on this for next update.

           

    Will be nice when it works.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-12-25T18:15:01+00:00

    microsoft is working on this for next update.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-12-25T17:19:07+00:00

    The Microsoft workround did not work for me.

    Was this answer helpful?

    0 comments No comments