Update For Windows 10 For X64-based Systems

[Gibert Chisholm]

Thenew 2021-12 Cumulative Update for Windows Server 2019 for x64-based systems (KB5008218) hangs at 24% for a long time before completing. It completes but what is it doing at 24% that makes it the longest percentage? Couldn't they take the whole time it takes to install this update divide that by 100 (for 100%) then more evenly nudge the percentage number? Instead, it takes 90% of its install life sitting at 24%.

The Windows Server 2012 R2 version of this update was installed much faster than the Server 2019 version. I've installed these on numerous machines and the result is the same, even with SSD-backed storage. It works.... just have patience when you see 24%.

This post is more like curiosity, what exactly is happening behind the scenes at 24%, and then also to Microsoft, feedback, that the update progress time should be more evenly distributed from 1 to 100%. Anyways, thanks for the overtime Microsoft. Glad I get paid by the hour!

Actually I'm staring at one now... 24% whatever it is, takes a very long time. Fortinately it does install. I only had one server give me a hexadecimal error code, but I resolved that by just downloading it from the Microsoft Windows Update Catalog and running it by hand. If you run it by hand the progress bar does not have a percent on it, but it does fill only maybe 1/10th of the way and sits there for about 45 minutes and then BOOM, its filled out and goes to the installation successful screen.

I hope in the future Microsoft changes it, or maybe don't put a percentage at all, put a thin progress bar. Does Microsoft employees read this? Anyway I did leave feedback on that site, and on my computer I'll hit Win+F and leave feedback there too.

I guess there's nothing else you can really do, and the updates install, they just chill at 24% for a while. Like I said there's no issue, the main reason for this post was more of a curiosity thing. I think I can mark your post as an answer because unless an actual engineer that wrote windows update comes on here and explains, I don't think we will get a better, more accurate answer.

3a8082e126