Dear readers, I’m starting this post off by telling you that I’m doing this from a Windows 11 PC, more specifically a computer with Windows 11 updated yesterday. I say this because, given the circumstances, it’s possible that I won’t be able to continue writing at any moment, and like the message found by the Fellowship of the Ring in Moria, this will be the last message I can leave in writing before hordes of goblins fail me the system will prevent you from continuing to type.

Microsoft’s thing with Windows 11 updates at this point already escapes all logic, to the point where it starts to make sense to think it’s something they’re doing on purpose, like the prank of a young child left alone with the hilarious nature of the situation without thinking about its consequences. And as horrible as that option is, it still seems more acceptable to me than the other one, the one that common sense points to and tells us that they don’t care about the reliability of updates at all.

What’s the problem? Well It can be found in the KB5039302 update for Windows 11, released last Tuesday the 25th and which yes, at least it is not one of those that installs automatically, so it was necessary for the user to start its installation manually. And why am I speaking in the past tense? Well, because Microsoft temporarily pulled it after realizing that, surprise, we’re once again talking about an update that breaks Windows 11.

More specifically, users affected by the issue with Windows 11 update KB5039302, who are not all those who installed it, claim that after doing so Your systems have entered a reboot loop that is not easy to get out ofand that in some cases it was even necessary to resort to recovery features and tools to get their systems working normally again. Something that may not be easy for multiple user profiles.

After recognizing the problem, Microsoft removed the failed update and although they have not yet been able to determine the reason or reasons for this problem, they have confirmed that they are working on it, as we can read on the page dedicated to the update. But again, the big problem is that an update was released that, given what happened, wasn’t evaluated with the necessary level of depth before.

Windows 11 is exceptionally complex software (like the rest of general purpose operating systems these days) and I’ve stated a thousand times that it’s very, very difficult to fully evaluate the performance of an update before it’s released. The problem is that the bugs keep popping up in updates and there doesn’t seem to be any specific measures being taken to avoid them. And this is especially critical.