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-13T13:02:07+00:00

    I did the same as you, and I also received a message, but it said the update KB4054517was not compatible with my system.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-02-14T03:31:30+00:00

    I had the same problem with Windows Update failing to install KB4054517.  I've spent weeks trying to shake this off with all sorts of jiggery pokery from numerous websites.  Today, I followed your steps in disabling Windows Update (via 'Services'), restarting my PC and then manually running the KB4054517 msu file I downloaded from the Microsoft Update Catalogue.  It worked first time.  Thanks for sharing your fix with us all. 

    Stating that you should reset your system, is not an answer to someone having spent hours installing and using software, just to have an update make it fail. It's not so simple to just treat your data without regard to time spent to reinstall all of your Windows 10, from square one. It should not be so risky. 

    When you have work to do, you expect to be able to complete it in a timely manner, not spend hours of time, reinstalling applications and attempting to rebuild the end users work and the world.

    Was this answer helpful?

    3 people found this answer helpful.
    0 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
  4. Anonymous
    2017-12-18T15:27:24+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 :(

     Just venting  here , I agree with you  100% . I just wasted 2 days trying to get this issue resolved . I dont see Microsoft support providing any good input on the forum . Sees like they are waiting for someone  here to figure it out for them  .  I have spent way too much time fixing windows 10 issues . Never had to do anything like this with windows 7 . Maybe its time a good lawyer started a class action against Microsoft.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2017-12-13T21:36:11+00:00

    i have parallel experience.  Running W10 1709. last week I noticed that KB4051963   build 16299.98 never triggered an update on my machine.  I assume I was on previous .64 build. Today KB4054517 installed but failed with message 0x80070643.  But  I check the build number in setting the version is W10 Pro 1709 OS build 162.9.125

    The build cycle was same as you describe with stage 1 and stage 2 messages and a reboot.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments