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: Newest
  1. Anonymous
    2018-01-08T16:53:43+00:00

    Solved my issue!

    Running Win 10 on two laptops, an Intel® Core™ i5-5200 and an AMD A10-4600M. The AMD A10 was the one where all updates were failing.

    Running the same anti-virus software on both machines however in checking the Registry files, the AMD did not have the “QualityCompat” setup, so I created that:

    Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat"

    Value Name="cadca5fe-87d3-4b96-b7fb-a231484277cc"

    Type="REG_DWORD”

    Data="0x00000000”

    The above should exist IF your antivirus software is compatible with the Fall Creators update so depending on what you are using check to make sure it is.

    Then I created a restore point (you just never know with this OS!).

    I re-downloaded the Win 10 Fall Creators installation tool from:

    https://www.microsoft.com/en-us/software-download/windows10

    Not sure if above was necessary but not taking any chances at this point.

    So at this point I went back to square one and started installing the base 1709 which took me back to the OS Build 16299.15 (think it was “15”). This took numerous hours to complete so be patient. BE SURE TO use the “KEEP ALL DATA AND APPS” option when running!!!!

    Once re-install completed, I created another restore point. Spent time checking settings and making sure everything was working correctly. Did numerous “restarts” and “shut down”/start.

    Once laptop seemed to be stable and startup quickly I went to the Windows Update settings and checked for updates. It downloaded several, taking hours to get them ready and install. BE PATIENT!

    I finally got the “restart to install” indication.. so with bated breath I “restarted”. It took several more hours and I made sure NOT to do anything until it completed ALL updates, but in the end IT WORKED!!!!!

    So when installing from square one, under “View Installed Update History” my laptop shows successful installation for:

    2017-12 Security Update for Adobe (KB4053577)

    2018-01 Cumulative Update for Win 10 (KB4056892)

    In looking at the “Uninstall an update” the Microsoft Windows section shows:

    Security Update for Microsoft Windows (KB4056892)  

    Update for Microsoft Windows (KB4058702)  

    Update for Microsoft Windows (KB4055237)  

    Update for Microsoft Windows (KB4055994)  

    Update for Microsoft Windows (KB4057247)  

    Running Windows 10 Home, I am currently at Version 1709 OS Build 16299.192 on both laptops. The above updates were required on my laptop, depending on what your's is it may install different ones.

    From start to successful installation it was about 7 hours.. not happy about it but at least our laptop is up and running again. Maybe we should all submit invoices to MS for our time fixing their issue.. LOL

    Not saying this will work for everybody just that it worked for me!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-08T14:40:10+00:00

    Second computer I had issues with, neither 32 bit nor 64 bit Windows 10 updates for December 2017, and January 2018 would allow the system to run. Re-installed Windows 8.1 64 bit that the on board motherboard Product Code Key works for. Working great.

    Third computer had a bad video card and D: drive. Will now try the Windows 10 updates and see what happens.

    First computer was at least 10 years old - owner buying a new refurbished unit today. Will then see if it has any issues.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-08T08:01:57+00:00

    Hi

    Thanks for your response,

    Unfortunatly KBKB4056892 is giving me the same reboot issue that KB4054517 was.    Basically Micrisift replaced one bad update for another

    Any thoughts?

    Just spotted on my Dad's PC that he is getting the same with KB4056892 (after KB4054517 installed automatically in December).

    First noticed it yesterday when he got a message when he closed down, that another user was using his PC and they would lose data if he shut down.

    This occurred because PC wanted to restart to complete install of KB4056892 and other "USER"  would now seem to be MS. This message appears every time we click on the restart now button for KB4056892, which then does not complete install regardless of how many times PC is restarted, or normal shut down and start.

    Looks like MS have compounded their bloomer by getting PCs that successfully installed KB4054517 with their latest cock up KB4056892.

    NB I note that there are comments that it is MS attacking older PCs, however it looks like they are not that smart as they are also affecting brand new Christmas presents as well.

    Merry Christmas.

    Nollaig Chridheil agus Bliadhna Mhath Ùr.

    Jum fosjladh dokus bliadhna uire chum sith, sonas is samchair.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-07T22:47:56+00:00

    I didn't have the same problem.  I went and deleted the folders under /windows/SoftwareDistribution and forced a re-scan for updates...the 892 update came up and 517 didn't...I also set up the Windows Insider build options up and got an update to build 17123-1610 and installed that.  I haven't had any issues since.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-07T21:33:25+00:00

    Guess what sports fans? 

    On two of our PC's (the ones that DIDN'T have any problem installing KB4054517), they both got that same error code 0x80070643 when installing the "new" patch KB4056892.  However, the build number did increment, so we're treating this as another false negative. 

    Ironically, our other two PC's that DID get the error installing KB4054517 in December, did NOT get any error codes when installing KB4056892.  GO FIGURE !

    In all cases, when one of our computers reports the 0x80070643 error during the installation of either 4054517 or 4056892, that computer immediately ceases to be able to display other PC's on our Ethernet/LAN network in File Explorer -> Network, although the PC's ARE actually accessible.  Strangely, wireless PC's and printers ARE still visible in File Explorer.

    GO FIGURE 2.0 !!

    Also, lag times between requesting a print and hearing the printer start up increased dramatically as each of our PC's installed the fall creators update.

    WHY IS IT THAT WHILE MICROSOFT IS BUSY CRAMMING IN A BUNCH OF NEW CAPABILITIES INTO EACH W10 FEATURE UPDATE THAT I'LL NEVER USE, THEY ARE ALSO BREAKING OR DEGRADING BASIC FUNCTIONS LIKE NETWORKING AND PRINTING AND UPDATING OUR OS?

    Was this answer helpful?

    0 comments No comments