worked for me thank you a million.how do i find the build number? been fighting this issue for days.
regards,
rm
right click on start
select run
enter winver
press enter key
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
worked for me thank you a million.how do i find the build number? been fighting this issue for days.
regards,
rm
right click on start
select run
enter winver
press enter key
This is what worked for me:
Hope this will help you as it helped me
My issue with this update was described by code: 0x80070643
which I think means, that there were some windows files that were kinda damaged and they were the cause why the installation failed. Thankfully it seems that the diagnostic has repaired them.
worked for me thank you a million.how do i find the build number? been fighting this issue for days.
regards,
rm
The interesting thing is that there are several other updates that don't always show up. It seems that somehow Microsoft is determining which computer is trying to update and then customizing which updates to install. My computer is now successfully on build 1699.125 after using the Media Tool. It has KB4054517 installed, but also KB4055237, KB4055994, and KB4057247. These are all supposed to enhance the update process for computers running the Fall Creators update. It never did have KB4051693 installed. That was probably the problem with KB4054517 not installing. Microsoft needs to be more transparent in this stuff. Going through the hassle each time there is a cumulative update could get old.
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.
This worked for me as well. Thanks! Damn thing wasted hours of my time. People having this issue should try this solution. Uninstall if any of these updates were already installed first.