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-15T04:39:20+00:00

    Didn't work for me

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-15T04:54:59+00:00

    0x800F0845

    PS>net helpmsg (0x845)

    The operation is invalid on a redirected resource.

    FACILITY_SETUPAPI<br><br><br>15 The source of the error code is the Setup API.

    Try looking for clues in  setuperr.log  and  setupact.log  Use the timestamp of your event item as an index into those and then look back from there.

     assume at this point that there's a driver conflict

    There's a potentially relevant diagnostic for that.  SetupAPI.Dev.log  If you can find that there is a problem with a device that you can disable, do that.  Then hopefully next time you won't have such a symptom to look at.

    See also

    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died

    HTH

    Robert Aldwinckle

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-15T05:01:36+00:00

    yhank you, happy holidays!!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-15T10:05:04+00:00

    I have the same problem, tried different solutions, going back to a restore point, but then the update comes again and with the same failure

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. 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