Some subset of users of Windows 10 Fall Creators Update, chronicle 1709, news determined bugs with this month’s Patch Tuesday missive, KB 4054517. Many of those saying problems are regulating new Surface devices. Microsoft has not concurred any problems. Official sites usually offer a aged “Gawrsh, we need to Restore/Restore/Reinstall” nutriment — and it doesn’t help.
What kinds of problems? They run utterly a gamut. @jwhiz56 reports on AskWoody:
This KB commissioned on my MS Surface Pro 3, my HP HPDV8T laptop though refuses to implement on my 2017 Surface Pro (purchased usually before Thanksgiving). I’ve reset it mixed ways (the OS) and a refurbish possibly sits during 99% downloaded, or it fails on installation. my C:windowslogsCBS office cooking adult ALL of my hoop giveaway space. I’ve attempted all hints/suggestions on a Microsoft forums associated to this KB. when we downloaded a standalone chronicle for my mechanism x86/windows 10, it says it’s not germane to my computer.
MountainBnJ reports on a Microsoft Answers forum:
The accumulative refurbish KB4054517 unsuccessful with an blunder formula of 0x80070643 … this appurtenance will not arrangement a other 3 PC’s on a network when we name “Network” in File Explorer. But all 3 other PC’s can “see” and entrance this PC no problem. … We’ve run Windows Update Troubleshooter and told it to Apply Fixes whenever it stirred us, and it DID news that it found and bound 3 issues. … After exiting a Troubleshooter, we clicked on “Check for Updates” again and it pronounced “Your device is adult to date.”… We beheld that a build series after a “failed” refurbish had altered to 16299.125. So a complement thinks it DID implement something newer than it had before, though Windows Update thinks a accumulative patch unsuccessful to install.
MortazaAnsari, also on a MS Answers forum, says:
I recently upgraded my mechanism from Windows 7 Home to Windows 10 Home regulating a giveaway upgrade. The ascent was successful though i wanted to purify implement so i used a built-in recovery. … EVERYTIME i start my mechanism it automatically boots to Windows 10 and thats where it loads for about 7 seconds and afterwards an blunder comes adult saying that there is an INACCESSIBLE_BOOT_DEVICE.
Mortaza reports that reaching into a PC, unplugging a tough drive, booting from a USB revive picture solved a problem — though others on that thread haven’t been so lucky.
Paula Stichbury posted a different problem:
Carried out a reset liberation procession (with gripping files option) twice though a refurbish KB4054517 stops during “status: Installing – 99%”. If we do a restart, it takes a really prolonged time for a “getting windows ready” summary to go away. The refurbish standing emanate stays any time.
Eric Van Norman, @kf0s, tweets:
Looks like KB4054517 competence be really bad for some @MicrosoftHelps (maybe @Dell or @nvidia related). Leads to Inaccessible Boot Device and/or multi hour foot times. No specific fixes found nonetheless though others have spent days to resolve. Windows Restore didn’t help.
To that both Microsoft Support @MicrosoftHelps and a Dell support criticism @Dell responded with invalid non-answers.
@ComradeArthur tweets that a problem comes behind again and again:
I’ve given adult on regulating it. I’d settle for simply restraint serve attempts by Windows10UpdateAssistant. But we can’t get a damn thing off my computer. It tries to refurbish 2 or 3 times a day! Do we know how to BLOCK it?
That’s a repeated theme. Not usually does KB 4054517 take over Win10 FCU systems to run an update, it persists in re-installing over and over again.
Mountain BnJ has an engaging analysis of a problem:
Based on a practice of a other people who have already replied on this thread (including a purify implement and re-update that unsuccessful again!), we don’t consider behaving a RESTORE and re-running Windows Update would outcome in any opposite outcome.
After installing a 12/12/2017 Quality refurbish on 4 opposite PC’s, we trust a designation problems are being caused by opposite versions of a Windows Update Client software. …
During a 12/12/2017 Quality Updates, we celebrated VERY poignant differences in a refurbish method and messaging, depending on a pre-update Build number. This leads us to trust that a Windows Update program being used was opposite for Build 16299.64 contra 16299.98.
That doesn’t seem to explain all of a problems that people are encountering, though it might criticism for some.
Microsoft, as usual, has not reliable a problem and a determined “advice” is to Reset or reinstall Windows — a routine that’s been shown, time and time again, to be ineffective. No, a Windows Update Troubleshooter doesn’t work either.
If you’ve followed along with me here on Computerworld, we know that we suggest we don’t implement this month’s patches usually yet. And we know that we don’t suggest moving to Win10 FCU until Microsoft has some-more of a bugs jarred out. According to a aged Current Branch for Business advice, we should wait 4 months for an ascent to simmer, so a delinquent beta testers can perform their destinies. By that measure, Win10 1709 won’t be prepared for primary time until January.
Frankly, I’m astounded we haven’t heard some-more outrage from a Win10 1703 business who were forcibly upgraded to 1709. Microsoft stomped all over a environment in Creators Update that blocked a ascent to Fall Creators Update, offering no involuntary correction, and got divided with it.
Have a improved solution? Join us on a AskWoody Lounge.