Microsoft pauses Windows 11 update as it’s sending some PCs into an infinite reboot hell

Windows 11 just got its latest update, but Microsoft has put it on hold following the discovery of a bug that’s seriously bad news.

This is the KB5039302 update, which is an optional download for Windows 11 22H2 and 23H2, so it’s still in preview, ahead of its release as the cumulative update for July 2024 next month.

The showstopper of a bug puts affected PCs into what’s known as ‘reboot hell’ whereby the PC keeps failing to start, rebooting, failing again, then rebooting, and so on ad infinitum – well, until the user intervenes and tries to initiative a recovery. (Or in some cases, unplugs their PC out of frustration, no doubt – never do this if you can at all avoid it, we should add, as cutting power at the wrong time can be bad news for your system drive, as it could corrupt files potentially).

What’s the root cause here? Well, it appears to have something to do with PCs using virtual machines (running another OS inside the current operating system, essentially).

Neowin noticed that in its release health dashboard, where this gremlin has been flagged up, Microsoft tells us: “This issue is more likely to affect devices utilizing virtual machines tools and nested virtualization features, such as CloudPC, DevBox, Azure Virtual Desktop. We are investigating to determine the precise conditions under which this issue can trigger.”

While that investigation is taking place, Microsoft has paused this update, so it won’t be offered to Windows 11 home users or businesses.


Unhappy millennial male employee work online on laptop at home office frustrated by gadget error or mistake. Angry young Caucasian man stressed with computer operational problem or breakdown.

(Image credit: Shutterstock / fizkes)

Analysis: Room for doubt

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.

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.

You might also like…

TechRadar – All the latest technology news

Read More

Windows 11 could soon deliver updates that don’t need a reboot

Windows 11 could soon run updates without rebooting, if the rumor mill is right – and there’s already evidence this is the path Microsoft is taking in a preview build.

This comes from a regular source of Microsoft-related leaks, namely Zac Bowden of Windows Central, who first of all spotted that Windows 11 preview build 26058 (in the Canary and Dev channels) was recently updated with an interesting change.

Microsoft is pushing out updates to testers that do nothing and are merely “designed to test our servicing pipeline for Windows 11, version 24H2.” The the key part is we’re informed that those who have VBS (Virtualization Based Security) turned on “may not experience a restart upon installing the update.”

Running an update without requiring a reboot is known as “hot patching” and this method of delivery – which is obviously far more convenient for the user – could be realized in the next major update for Windows 11 later this year (24H2), Bowden asserts.

The leaker has tapped sources for further details, and observes that we’re talking about hot patching for the monthly cumulative updates for Windows 11 here. So the bigger upgrades (the likes of 24H2) wouldn’t be hot-patched in, as clearly there’s too much work going on under the hood for that to happen.

Indeed, not every cumulative update would be applied without a reboot, Bowden further explains. This is because hot patching uses a baseline update, one that can be patched on top of, but that baseline model needs to be refreshed every few months.

Add seasoning with all this info, naturally, but it looks like Microsoft is up to something here based on the testing going on, which specifically mentions 24H2, as well.


Analysis: How would this work exactly?

What does this mean for the future of Windows 11? Well, possibly nothing. After all, this is mostly chatter from the grapevine, and what’s apparently happening in early testing could simply be abandoned if it doesn’t work out.

However, hot patching is something that is already employed with Windows Server, and the Xbox console as well, so it makes sense that Microsoft would want to use the tech to benefit Windows 11 users. It’s certainly a very convenient touch, though as noted, not every cumulative update would be hot-patched.

Bowden believes the likely scenario would be quarterly cumulative updates that need a reboot, followed by hot patches in between. In other words, we’d get a reboot-laden update in January, say, followed by two hot-patched cumulative updates in February and March that could be completed quickly with no reboot needed. Then, April’s cumulative update would need a reboot, but May and June wouldn’t, and so on.

As mentioned, annual updates certainly wouldn’t be hot-patched, and neither would out-of-band security fixes for example (as the reboot-less updates rely on that baseline patch, and such a fix wouldn’t be based on that, of course).

This would be a pretty cool feature for Windows 11 users, because dropping the need to reboot – to be forced to restart in some cases – is obviously a major benefit. Is it enough to tempt upgrades from Windows 10? Well, maybe not, but it is another boon to add to the pile for those holding out on Microsoft’s older operating system. (Assuming they can upgrade to Windows 11 at all, of course, which is a stumbling block for some due to PC requirements like TPM).

You might also like…

TechRadar – All the latest technology news

Read More