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: Oldest
  1. Anonymous
    2017-12-21T00:42:32+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.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-21T10:16:19+00:00

    I have the same problem with this update failing to install.  Normally, this wouldn't by such a problem for me (other then if I accidentally click Restart instead of Shut down - I have to wait couple of hours for Windows to try and fail to install updates), but since then I have been experiencing no disk space warning, daily.

    I have an 256GB SSD drive, with 140GB remaining normally. I tracked the problem down to CBS.log file. TrustedInstaller service is using this file - and its size grows approx 20GB an hour. Windows is logging here any events concerning updates, apparently. I really can't imagine the volume of text needed for a file to reach this size. I tried different methods for fixing the cbs.log, before I even realized the problem was with this windows update. Nothing worked. Right now I'm just disabling the service completely for the day to get any work done. And every evening - this update fails to install.

    My system is Windows 10 Home, version 1709, compilation 16299.98.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-21T10:27:46+00:00

    FWIW...

    At least MS has now acknowledged this issue: "Microsoft is working on a resolution and will provide an update in an upcoming release."

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-12-21T10:33:10+00:00

    Same system configuration, same problem with diminishing disk space and no joy updating KB4054517, except my CBS.log file only seems to increase only periodically.  Have tried all the workarounds I have found but no success.  Like you, I stay away from the restart option for the same reasons. Has MS even acknowledged there is a problem here?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-12-21T10:35:22+00:00

    Has MS even acknowledged there is a problem here?

    Yes. Read my post just above yours..........

    Was this answer helpful?

    0 comments No comments