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
    2018-01-05T19:08:51+00:00

    I experienced te problem, as can be seen on page 15 of this forum thread. I also had reset my PC. This was because during an attempt to update my PC, it lost power.

    On trying to reboot it had loads and loads of problems, so I rest the PC. Then the update started again. I noticed at the time it seemed to be stuck at 99% completed. But I rebooted and thought nothing of it as nothing untoward happened other than windows taking well over an hour saying it was reconfiguring.

    Three days later the system complained it had run out of space on the system disk. On investigation I saw the 99% problem and that it was the CBS log file that was well over 150GB in size. I then spent an hour or so before figuring out how to delete it.

    A reboot then took ages again, saying it was reconfiguring and it ran out of space again a couple of days later and the 99%. problem was back. Finally I saw this thread. Tried most of the suggestions, but they didn't work, so eventually I "hid" the update, so it wouldn't be installed.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-05T14:43:02+00:00

    I've come to the conclusion that Windows/Microsoft just doesn't care enough about this issue to properly address it. Other than absolutely useless answers like "Run the troubleshooter" or "Download this troubleshooter" only to have the issue remain while Windows /Microsoft states that the issue will be addressed in the next cumulative update on 01/09/18, or most likely failing that, the next cumulative update or the one after that, so on and so forth, while the issue remains or some equally problematic, unfixable issue arises  to make KB4054517 look like a minor glitch.

    At this point I'm seriously considering the total removal of Windows 10 Pro and the installation on some Linux OS that I can at least fix myself or get reliable information on how to address an issue from the Linux community. My PC is a little over a year old, it cost well over $1000.00 and I can't properly use it. I have spoken with several windows users in other forums who were able to install KB4054517 only to lose programs or have other severe issues with the operation of their computers. 

    It's almost like not being able to install KB4054517 is a blessing in disguise, except that it isn't.

    In closing, I have tried several of the suggested workarounds people have posted in answer to my initial comment, none of them have worked for me. I still have Windows updates shut off and I'm left with no reasonable expectation of competent help from Microsoft. It looks like I will have no other realistic recourse other than to erase Windows 10 Pro from my hard drive and install an SSD with some iteration of LInux as my new OS.

    Whatever I wind up doing this is the absolute last Windows PC that I will ever waste my money on.

    Good luck to those of you who are willing to hang on and be ignored by Windows/Microsoft who are happy to take your money while providing a highly questionable OS that rarely functions as Microsoft would like you to believe.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-01-04T01:30:23+00:00
    • Hello. The following occurred on my HP desktop on 1/2/2018. I had previously received a failed install of KB4054517 on 12/12/17 w/error code 0x8024200d.
    • Went to MS Update Catalog and downloaded the appropriate KB4054517 .MSU file, approx. 513mb.
    • Ran the .MSU stand-alone installer and got the message that KB4054517 was already installed!?
    • Went to Programs and Features > Installed Updates, and sure enough there it was showing an install date of 12/12/17.
    • Uninstalled KB4054517 and the system restarted.
    • Again, tried the stand-alone installer for KB4054517, but again got the dreaded news that KB4054517 was already installed!?
    • Checked back in Programs and Features > Installed Updates, and KB4054517 was still there, except the date of install column was blank!?
    • Well, I right-clicked and Uninstalled again with fingers crossed, and the system restarted again.
    • Interestingly, at this point, in Settings > Window Update > Update History Log, it shows an entry as follows:
    • '2017-12 Cumulative Update for Windows 10 Version 1709 for x64-based systems (KB4054517) (2)', then on next line,
    • 'Last Failed install attempt on 1/2/2018 - 0x80070490'
    • Checked back in Programs and Features > Installed Updates, and KB4054517 was gone!!
    • Re-ran the stand-alone installer for KB4054517.  It installed OK, and the system restarted again.
    • Interestingly again, in Settings > Window Update > Update History Log, it shows an entry as follows:
    • 'Security Update for Windows (KB4054517)', then on next line,
    • 'Successfully installed on 1/2/2018'.
    • So, this update comes with two different definitions. Go figure!?
    • Hope this helps someone in the community.  You people sure helped me work around this problem.  Many thanks!!!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2017-12-15T15:46:19+00:00

    Finally got it installed. This is what did it...

    According to this  https://www.computerworld.com/article/3199077/microsoft-windows/windows-10-a-guide-to-the-updates.html

    The update progression from OS Build 16299.68 is via 16299.98 to 16299.125

    So I manually updated using KB4051963 to OS Build 16299.98 and then manually installed KB4054517.

    The router was turned off to stop the automatic updater which was trying to butt in.

    Took a while but there were no further problems.

    Don't know why KB4051963 was missing.

    I would expect Cumulative updates to be designed to contain all previous update files. If that is the case then KB4054517 must be incomplete and is more like a "Delta" update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-12-14T04:51:31+00:00

    My build is 16299-98. I did receive a message saying the update is not applicable to my build. How do I update that? I am not technically minded, I do appreciate any help I receive.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments