Microsoft on Wednesday confirmed that its latest June 2024 optional non-security preview update (KB5039302) for Windows 11 is causing some devices to restart repeatedly.
For those unversed, KB5039302 was released on June 25, 2024, for Windows 11 version 23H2 and Windows 11 version 22H2. It included new features and addressed several issues, such as distorted audio in Snipping Tool recording and issues with ejecting USB devices.
However, after installing the KB5039302 update, owners of some PCs experienced infinite rebooting issues, where the devices restarted repeatedly without their intervention.
The Redmond giant has now acknowledged the issue and said it is likely to affect devices utilizing virtual machines and other nested virtualization tools on their PCs, such as CloudPC, Azure Virtual Desktop (AVD), and DevBox.
Meanwhile, Microsoft has paused the rollout of KB5039302 through Windows Update and Windows Update for Business, as there are no workarounds.
“After installing updates released June 26, 2024 (KB5039302), some devices might fail to start. Affected systems might restart repeatedly and require recovery operations in order to restore normal use,” Microsoft noted in a support document.
“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,” it added.
“While our investigation is underway, we are pausing the offering of this update via Windows Update and Windows Update for Business. For this reason, this update may not be presently offered to your device.”
According to Microsoft, users of Windows Home edition are less likely to be affected by the bug, as virtualization usage is less common in home environments.
If you use virtual machines on your Home device, it is advisable not to download and install the KB5039302 update until Microsoft rolls out a fix.
The company is still investigating the root cause of this severe bug and working on a resolution.
It is expected to provide an update in an upcoming release.
