Clearly, given that having a PC trapped in a reboot loop is a dire scenario, it’s a good idea that Microsoft has pulled this update until the firm can work out what’s really going on here. This is an optional update anyway, so it’s not like KB5039302 is crucial, or even finished – which is why this flaw is present, no doubt.
Although you’d really have hoped Microsoft would have picked up on such a calamitous bug before the final preview release of the update – but at least it’s being fixed now. This also goes to illustrate why it’s always a risk to download an optional update for Windows 11 – we’d recommend steering clear of these in case there is a last-minute showstopper, just like this glitch.
Virtualization and Home Users
Granted, as Microsoft observes: “Users of Windows Home edition are less likely to experience this issue, as virtualization is less common in home environments.”
Even so, some Windows 11 Home users will use virtualization features, no doubt, and Microsoft isn’t 100% clear about the bug not affecting other PCs either. The language used is that the problem is “more likely” to hit PCs using virtual machines in some way, leaving room for doubt that it could affect other systems too. This is likely why the update has been retracted, for now, we’d wager.
The crucial thing is that Microsoft fixes this one up, or at least pushes the feature or code that’s caused the problem aside, before the full release of the July 2024 cumulative update, clearly enough.
