Tuesday , 26 June 2018
Home >> S >> Security >> Win10 FCU December patch KB 4054517 fails big time

Win10 FCU December patch KB 4054517 fails big time

Some subset of users of Windows 10 Fall Creators Update, version 1709, report persistent bugs with this month’s Patch Tuesday missive, KB 4054517. Many of those reporting problems are using recent Surface devices. Microsoft has not acknowledged any problems. Official sites only offer the old “Gawrsh, you need to Restore/Restore/Reinstall” pabulum — and it doesn’t help.

What kinds of problems? They run quite a gamut. @jwhiz56 reports on AskWoody:

This KB installed on my MS Surface Pro 3, my HP HPDV8T laptop but refuses to install on my 2017 Surface Pro (purchased just before Thanksgiving). I’ve reset it multiple ways (the OS) and the update either sits at 99% downloaded, or it fails on installation. my C:windowslogsCBS directory eats up ALL of my disk free space. I’ve tried all hints/suggestions on the Microsoft forums related to this KB. when I downloaded the standalone version for my computer x86/windows 10, it says it’s not applicable to my computer.

MountainBnJ reports on the Microsoft Answers forum:

The cumulative update KB4054517 failed with an error code of 0x80070643 … 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. … 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. … 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.

MortazaAnsari, also on the MS Answers forum, says:

close
==[ Click Here 1X ] [ Close ]==