Go to ...

RSS Feed

August 11, 2020

Why KB4512941 Persists Despite Growing Issues List

Last week, MS first dropped CU KB4512941 into the 1903 Release Preview ring to Insiders. Then on Friday, August 30, that update hit general availability. Interestingly, lots of folks have been reporting issues with this update. This includes yours truly, who blogged here at Win10.Guru about the 0X800F081F install error (and its fix). In the meantime, issues related to KB4512941 CPU usage spikes, SearchUI.exe hangs and failures, and gotchas from tweaking tools such as O&O Shutup10 and MSI Afterburner have also surfaced. This raises an interesting question: given a fair number of issues with this update, why hasn’t Microsoft yanked it to try again another time? I have a theory, for which I offer visual proof from Microsoft’s own 1903 Status Page.  If you count the number of current active issues at the head of the Known Issues list it totals 15. Of those 15, forty percent — six to be precise — are resolved with the release of KB4512941. They also appear as the top 6 items in the Known Issues list, as shown here:

Why KB4512941 Persists Despite Growing Issues List.issues

With 40% of the known issues addressed in this single CU, I figure MS has too much invested to give up and try again.
[Click image for full-sized view.]

What a Wonky KB4512941 Means Right Now, and in the Future

Right now, it means that many organizations (and smaller-scale users) may want to hold off on updating to KB4512941. OTOH, for more adventurous types, it may make sense to try the upgrade, with a rollback (or image upgrade restore from beforetimes) should problems manifest themselves. For myself, even though I did encounter the persistent 0X800F081F error (and upgrade failure), I was ultimately able to work around it and get the upgrade installed anyway. At this point, I have yet to be bitten further by the other problems reported. I hasten to add that I lean much more heavily on Voidtools (Search) Everything for local search capability on my Win10 machines, rather than using its built-in search capabilities much or often.

I’m also of the opinion that MS will be working feverishly to address the issues that have popped up in KB4512941’s wake. As I’ve said, they’ve got a substantial investment in this CU. I’m pretty sure they’re going to do everything they can to protect that investment by finding and fixing the issues that this latest Cumulative Update has introduced. In turn, I can’t help but think that we’ll see more (and perhaps bigger) CUs from the Windows team over the next month or two than has been typical of late. With September now underway, and a 19H2 release to make ready for general availability, developers and testers alike are undoubtedly keenly aware that a stable, working release with decent performance or better is an absolute must. That’s why I’m watching what’s coming into the Release Preview channel very closely right now. At a minimum, it should be pretty darn interesting to see what happens next. Stay tuned!

Author: Ed Tittel

Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.

One Response “Why KB4512941 Persists Despite Growing Issues List”

  1. CountMike
    September 5, 2019 at 19:33

    I just found that Search which is supposedly tied up with Cortana (that I disabled a while ago) is occupying large portion of CPU, 2 cores/threads loaded up to 100% which takes upwards to 25%+ of whole CPU (8 cores, 16 threads). I disabled Windows Search Service, yet Search is still showing in Task manager and it takes several tries to stop it. It is really stubborn problem that repeats itself at every restart.
    If it was happening to Insider version, it would be somewhat understandable bu it is not, Skippy doesn’t have that problem.
    I can’t uninstall this KB and my earliest backup is not practical to restore because it’s tied up to a lot of SW used and installed since.

Leave a Reply

More Stories From 1903