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-05T08:22:13+00:00

    As of January 4, 2018 Microsoft has released update KB4058702 which should have fixed this issue for all users. I would just like to point out it took Microsoft NEARLY A MONTH to fix this problem from the initial KB4054517 update on December 12, 2017 to the fixed KB4058702 update January 3, 2018. Suffice to say Microsoft's handling of this issue has been reprehensible and completely unacceptable.

    For those interested, here's what I think was causing the problem:

    On the KB4054517 update page there is a section titled Known issues in this update where Microsoft exactly describes this issue: *"Update installation may stop at 99% and may show elevated CPU or disk utilization if a device was reset using the Reset this PC functionality after installing KB4054022."*Before Microsoft patched the problem in the most recent update they listed a long, drawn-out solution that involved manually downloading update KB4054022 from their update catalog, unpacking it, installing it, and only after that could update KB4054517 be installed (they have since removed the large explanation now with a short statement saying the latest update has fixed this). I know this because I was looking at this page Wednesday night, January 3rd, and by following their steps and installing KB4054022 and KB4054517 I was able to fix my problem. It just so happened that the next day, January 4th, that the patched update was finally released and consequently they webpage was updated (go figure).

    From what I understand, there was a problem with a previous update (KB4054022) which was preventing KB4054517 from being installed, likely do to the PC being recovered / reset. I do remember reseting my laptop early on in December even though I had just got it because I had messed up some directory and thought it easiest to reset it. Furthermore, I have two different laptops: an older one which I had not reset in the past month which was able to seamlessly install the update in under 10 minutes, and the newer one which I had reset which was the one experiencing trouble installing the update. If anyone else who was having this problem also remembers resetting their PC sometime recently from the Setting > Update & Security > Recovery menu please share because I'd like to know if this really was causing the problem.

    Anyways, because Windows hadn't properly configured an earlier update it was preventing the KB4054517 update from being finalized so the update was basically completed but the installation process never terminated (hence why the update was perpetually stuck at 99% and why some computers seemed to 'detect' that an update was installed but kept on retrying to update). Windows tried to complete the update whenever it rebooted but that same thing was keeping the update from being properly installed so your computer ended up being stuck on loop for hours only to finally start up and say that the update had failed. All of this was causing various problems like insanely large cbs.log files taking up gbs of space (I think mine was 120 gb) and reboot getting stuck at "Getting Windows ready" every time the computer was restarted.

    This is probably the best explanation you can expect to see on this issue because we all know Microsoft doesn't have the decency to give its users an explanation for why they had to waste hours of their time trying to fix a bad update. I'm just sorry I had to spend the whole week trying to fix my laptop.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-01-04T15:15:20+00:00

    Yesterday, Jan 3, the KB4504517 would try to install but seemed like as soon as it started it was told to quit and it just did a normal restart.

    Now On Jan 7, I see a new download for my updates and 4517 is missing.

    KB4056892 is on tap. I'll report how it goes by editing...

    AND THIS NEW kb4056892 FAILED at the same 48% point that the KB4054517 failed.

    But the Windows Update page says it installed correctly and of course no error is given.

    The winversion is still 16299.64

    AT first Windows Update says my computer is up-to-date. But after it ran 

    a check, it now wants to download KB4056892 again.

    Welcome to Microsoft.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. 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 No comments
  4. Anonymous
    2017-12-28T12:11:22+00:00

    Hi,

    I tried most of the suggestions here, but none worked. The automatic updater tried each time to install KB4054517 and got stuck. When I then restarted the system it took hours, saying it was configuring windows, filling up the CBS log (and my disk) in the process..

    In the end I downloaded the "Show or Hide Windows Update Troubleshooter Package from here:

    http://download.microsoft.com/download/f/2/2/f22d5fdb-59cd-4275-8c95-1be17bf70b21/wushowhide.diagcab

    and ran it. I used it to "hide" the offending update "KB4054517", so automatic update wouldn't try to install it from now on.

    I then restarted my PC and lo and behold, I no longer have the problem. I still had a huge CBS log in C:\Windows\logs\CBS (over 150GB).

    So I started a powershell in Admin mode (Windows-X) and used it to stop the Trusted Installer using the commands: 

    taskkill /f /im tiworker.exe taskkill /f /im trustedinstaller.exe

    then deleted the CBS log in Windows Explorer and restarted the PC.

    Once Microsoft fix the update I'll decide whether or not to "Show" the update.

    I hope this helps.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2017-12-22T15:07:19+00:00

    Happy to report Microsoft's solution worked for me. Update was installed successfully and the problem with CBS.log was solved, too. Current compilation is 125. :)

    I also finally checked my Windows 10 laptop. It reports all updates being up to date. But, when I look under history - update KB4054517 is showing as failed. Yet, I haven't experienced any problems with the system itself and the current compilation is 125.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments