Cumulative Update KB5008212 will not install

Hi Josh, getting stuck at 20% during the installation process is exactly what happens here. I don't have any problem downloading KB5008212 nor do I have high disk or cpu usage.

I have tried a dozen times now and each time the installation sticks at 20% and then fails. I have tried deleting the contents of Software Distribution/Downloads and several other tips but with no success.

With this being Patch Tuesday I'm hoping that a fix has been rolled out and KB5008212 will install now and also the updates contained in today's patch.

I'll let you know as I try later today. For the record only one of the five Win 10 systems I have has failed to update and that is my studio system. It is the newest system with no third party AV or browsers. It remains a mystery why it fails to update while the others have not.

@MarcHoppe, I could not agree more with your philosophy. I, too, refuse to install anything 3rd party on my main laptop. I also respect the music production. I worked years ago with Fruity Loops, Arturia, Cakewalk and Sonar. I'm sure the technology has progressed vastly since my time.

So I landed on this thread after trying to determine why my Disk and CPU usage where spiked at 100%. I did a factory reset on my laptop (HP AMD Windows 10 Home); and the problem persisted. I found my way to the Windows Update admin page; and noticed I was stuck downloading an update at 66% (KB5008212). Could this be the reason for my high resource usage? Surely not... but maybe??

I tried to get the download to progress, unsuccessfully. I tried stopping services; restarting the computer; nothing worked. FINALLY, I came across a thread which instructed to press Windows + R, run the services.msc command, find "Windows Update" and stop the service. THEN, go to the c:/Windows folder and delete the "SoftwareDistribution" folder. THIS WAS KEY. Once I restarted, my resource usage dropped drastically back down to the 5% range for both CPU and Disk usage.

So, like you, I have paused the updates and will wait for MS to resolve. I think of the time I have wasted; the money lost while I could be doing other work; all for what should have been a simple MS update.

Please, MS, take a look at this. I understand it could be computer related; but this is a new laptop, never any 3rd party apps installed, only using genuine MS software; with a fresh reformat. I have tried the update numerous times; and fail every single time. It either hangs while downloading or while installing. I have never made it past the 20% mark when I make it to the installing portion of the update.

I have now tried everything. I downloaded Win10_21H2_x64.iso from the windows update catalogue and I just tried the Update Assistant linked above by Venerable Nelson. Every time it does the same thing. The Catalogue .iso update returns this error message:

"We've set your PC back to the way it was right before you started installing windows 10.

0xC1900101 - 0x40017

The installation failed on the SECOND_BOOT phase with an error during BOOT operation"

The Update Assistant doesnt return an error message, but it seemed to go through exactly the same sequence during reboot. At the 75% mark it fails and an error message flashes briefly indicating an error during reboot and "attempting to collect additional information. It the proceeds to "undo."

I have a less than two-year old Lenovo Ideapad, high end with i7 processor, 500gb STD, that has worked flawlessly since I got it new in March 2020

Any thoughts?

Given the limited statistics we have from this thread, and projecting to the "bigger picture" that KB5008212 has probably installed successfully on significantly more computers than on which it failed, leads me to suspect that when KB5008212 fails to install successfully on a computer, there is an issue with that computer. This is probably the reason that MS hasn't responded. In other words, there may not be anything "wonky" with this update; rather, there may be something "wonky" with the computers on which it fails to install.

Firstly, thank you for your previous post on the fix. Using "Update Assistant" from this link, Download Windows 10 (microsoft.com). I didn't really do anything else other than that.

There was one difference I noticed afterwards that may (or may not) help others with this issue. Originally, I had tried to manually download the update from Microsoft's Update Catalog. The update that my computer was trying to use was "2021-12 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5008212)". After using the Update Assistant and letting the computer update, my Windows is now on Version 21H2.

That's nothing more than speculation. There are other people reporting the issue outside this thread:

Dated December 30th:

"But unfortunately, several users complain, Windows Update failed to install certain updates. Or windows update KB5008212 download stuck at 0% or at 99%."

https://windows101tricks.com/windows-update-failed-to-install/

There is nothing wrong with the one computer of mine that KB5008212 fails on. It has no third party AV software, no third party browser. It is the most pampered system you can imagine. It is a mission specific computer and all it is used for is music production. It never surfs the net, never opens e-mails and anything installed on it gets scanned on this system beforehand. It is 100% virus and malware free.

The only thing wrong with that system is that it's infected with Windows 10. People said the same thing when some of us who actually pay attention to what Windows is doing to our systems noticed the WasSMedic bug. They blamed the systems or the users but after months of bugging MS and submitting feedback reports MS found the problem and a fix was issued in a KB in October. Problem solved.

The fact that the majority of systems updated fine doesn't mean there isn't something wonky about KB5008212. The fact that the update continues to fail over and over on those systems even after repair procedures are run points more to an error caused by Windows that it can not fix at this time.

The reason MS Agents haven't responded is most likely because they have no clue what's going on or they know there is a bug in the update and simply don't want to admit the fact.