Microsoft recently encountered an issue with the delivery of the KB5039302 update on June 25th. This particular update, although containing some interesting features, has been found to cause Windows 11 PCs to enter a continuous reboot loop. The affected versions of Windows 11 include version 23H2 and version 22H2, while Windows servers remain unaffected.
The good news is that KB5039302 is an optional update, meaning it has not been installed on all Windows 11 computers. This update serves as a preview for the standard update that will be released on Patchday in July 2024. Therefore, it will only be present on your Windows 11 computer if you explicitly installed it.
Microsoft has acknowledged the issue and stated that devices may restart repeatedly after installing the update. Devices utilizing virtual machine tools and nested virtualization features, such as CloudPC, DevBox, and Azure Virtual Desktop, are more likely to experience this problem. However, Windows Home Edition users are less likely to encounter this issue due to virtualization being less common in private environments.
While Microsoft is actively working on resolving this issue, the update is currently not being offered through Windows Update and Windows Update for Business. This means that the update may not be available for installation on your device at this time.
If your computer is stuck in a reboot loop after installing the update, you will need to access the Windows 11 recovery environment. From there, select Troubleshoot, then Advanced Options, followed by Uninstall Updates. Finally, click on Uninstall latest quality update and confirm the removal of the update. Once KB5039302 has been successfully removed, restart your computer to resolve the issue.
It’s important to note that Microsoft is investigating the root cause of the problem and is working on a solution that will be included in a future update. In the meantime, users are advised to follow the steps outlined above to address the reboot loop issue caused by the KB5039302 update. Stay tuned for further updates on this issue as Microsoft continues to work towards a resolution.
