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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-12-28T13:09:56+00:00

    Hi Elusien.

    Great you managed finally. My solution worked. I'd to delete all log files too to engage disk space.

    Thanks for your contribution.

    JOHN

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2017-12-31T20:10:13+00:00

    I too had the same 0x80070643 error on KB4054517 and the "Inaccessible boot device" error when restarting the system or resuming from hibernation.

    The fix that I found was to do the following.

    To get past the "inaccessible boot device" error

    1. Boot into recovery mode, boot from recovery your recovery drive, or boot from Windows 10 Installation Media (select Repair my computer >> troubleshoot)
    2. From the Advanced Options, select System Restore and restore to a previous restore point.    (I used the automatic restore point created by Windows Update)
    3. Your system should boot up after a successful system restore, but if you reboot you will once again have the Inaccessible Boot Device error after a period of time.

    Fix the failed install of KB4054517 responsible for the "Inaccessible Boot Device Error"

    • Download the stand alone installer for KB4054517 using this link https://www.catalog.update.microsoft.com/Search.aspx?q=KB4054517
    • Uninstall KB4054517 via Programs and Features control panel
    • Reboot
    • Kill the Windows Update service, or disconnect from the internet to prevent Windows update from trying to reinstall KB4054517
    • Install KB4054517 manually using the stand alone installer

    Once reinstalled manually, the update was installed correctly and the inaccessible boot device problem was resolved as well.

    One thing that I did notice, was that after rebooting after the System Restore, but before fixing the failed update, the

    Hardware Abstraction Layer was version "10.0.16299.15", while after fixing the failed update, the Hardware Abstraction Layer was version "10.0.16299.98".  

    Cheers,

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-03T23:33:06+00:00

    My upgrade history shows the KB4054517 update successfully installed 14 times, on consecutive dates beginning December 13th. It appears to reinstall daily. There's definitely a problem, and I have no clue how to address it.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-03T23:43:06+00:00

    There seems to be a serious problem with the KB4054517 update not fully installing, yet reporting either that is failed in Update history and installed successfully in Programs and Features, or that it successfully installed, and yet keeps trying.   

    At least you are not getting the BSOD that others, including myself, were getting.

    I would probably download the stand alone installer, uninstall the current one that is not installed correctly, and reinstall using the standalone it it were me, but I would create a system restore point, and have a recovery driver or install media handy just in case.

    • Download the stand alone installer for KB4054517 using this link https://www.catalog.update.microsoft.com/Search.aspx?q=KB4054517
    • Uninstall KB4054517 via Programs and Features control panel
    • Reboot
    • Kill the Windows Update service, or disconnect from the internet to prevent Windows update from trying to reinstall KB4054517
    • Install KB4054517 manually using the stand alone installer
    • Reboot and test.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-03T23:53:55+00:00

     

    My upgrade history shows the KB4054517 update successfully installed 14 times, on consecutive dates beginning December 13th. It appears to reinstall daily. There's definitely a problem, and I have no clue how to address it.

    Hi David,

    I recommand this: 

    Hope you can find the solution here: 

    https://support.microsoft.com/en-us/help/4054517/windows-10-update-kb4054517 

    AND: clean up the directory " *C:\Windows\SoftwareDistribution\Download* " since it stores all former update packages.

    Together with the advices in the MS-link, and a full (=cold) reboot, Windows should re-install the proper updates, if any,

    might be lost and you have disk space won.

    Regards, John  (slagtand)

    My system:  Win10 Home x64 Version 1709 / build 16299.98    ☺ ☺ Took just 10 minutes or so.

    Was this answer helpful?

    0 comments