Nope I have a 4 months old HP laptop with 7th gen Intel core i3.
I feel like I'm the only one with a relatively recent computer. Hmm... conspiricy?
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.
Nope I have a 4 months old HP laptop with 7th gen Intel core i3.
I feel like I'm the only one with a relatively recent computer. Hmm... conspiricy?
You may have a point here.
My OLD computer with an Intel Motherboard and the 945 Chipset, did all the updates perfectly !
Both computers having issues, were AMD machines. Conspiracy?
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.
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.
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.