/industry-wired/media/agency_attachments/2024/12/04/2024-12-04t130344212z-iw-new.png)
/industry-wired/media/agency_attachments/2024/12/04/2024-12-04t130332454z-iw-new.jpg)
/industry-wired/media/media_files/2025/05/30/ctoIg1vencTMv7nOc4fj.jpg)
/industry-wired/media/media_files/2025/05/30/ctoIg1vencTMv7nOc4fj.jpg)
Microsoft Investigating Boot Failure Bug in May Update: Bug Linked to ACPI.sys Crashes, Full System Wipes May Be Needed
Microsoft is looking into a serious bug tied to its cumulative update (KB5058405) for Windows 11. The issue, reported mainly in enterprise setups, stops systems from booting after the update. Affected users see a recovery message pointing to a missing or corrupted ACPI.sys file with error code 0xc0000098.
Virtual Machines Most Affected by the Bug
The problem strikes virtual machines the hardest. Systems hosted on Azure Virtual Machines, Azure Virtual Desktop, Citrix, and Hyper-V are seeing the most cases. Although Windows 11 Home and Pro users are said to be safe, isolated incidents suggest the bug might reach physical PCs as well.
Recovery Tools Most Times Prove Useless
When the bug strikes, a device will not load into Windows; it'll just end up in recovery mode. Recovery tools that try to fix it are often futile. In some instances, a full reinstall of Windows would be the solution.
Advice for Users Yet to Install the Update
Skipping the May update may be the safest move for someone yet to install the update. Delay in applying the patch ensures they do not hit the boot errors until a solution comes from Microsoft. It is just wise to create backups before any major update for a Home user.
Microsoft Acknowledges the Issue
Microsoft has admitted that it is aware of the bug, and an investigation into the matter has been launched. Any updates and maybe a fix will be stated on the Windows release health dashboard. For now, no specific timeline has been made public for the resolution.
Growing Concerns Over Windows Update Stability
This bug adds yet more laundry to a long list of recent Windows troubles. Prior updates induced a Remote Desktop failure and forced recovery prompts from Windows 10. The trend is worrisome for the quality of Microsoft's patches and system stability.
Impact Limited to Specific Windows Versions
As of now, the boot failure mainly affects enterprise-level virtual machines running Windows 11 22H2 and 23H2. Devices on the newer 24H2 version are not affected.
A Wake-Up Call for Enterprise IT Teams
This incident serves as a clear reminder of the risks tied to large-scale software updates, especially in enterprise environments. As Microsoft works toward a fix, IT teams must stay watchful, prioritize data protection, and test updates in controlled environments before full deployment. Strong system management and cautious patching are no longer optional—they're essential.