Windows 11 Update KB5058405 Causing Boot Failures: What You Need to Know
A recent Windows 11 update, identified as KB5058405, is reportedly causing headaches for some users, leading to startup failures. Microsoft has acknowledged the issue and is currently investigating. This problem is particularly affecting users on versions 22H2 and 23H2 of Windows 11.
The error manifests as a 0xc0000098 recovery error related to ACPI.sys, a critical Windows system driver responsible for managing hardware resources and power states. The error message warns, "Your PC/Device needs to be repaired. The operating system couldn't be loaded because a required file is missing or contains errors."
While some physical devices are affected, Microsoft indicates that the issue primarily impacts virtual environments, including Azure Virtual Machines, Azure Virtual Desktop, and on-premises virtual machines hosted on Citrix or Hyper-V. According to Microsoft, home users running Windows 11 Home or Pro editions are less likely to encounter this problem, as virtual machines are predominantly used in IT environments.
However, reports suggest that even some physical Windows 11 PCs might be affected. Therefore, if you haven't yet installed the May update, it may be wise to delay the installation until Microsoft releases a fix.
Previous hiccups with Windows updates in May 2025 include an emergency out-of-band update to address a Windows 10 bug that triggered BitLocker recovery screens. Moreover, another issue concerning Windows 11 24H2 feature updates being blocked via Windows Server Update Services (WSUS) has recently been fixed. These past issues highlight the importance of proceeding with caution when installing updates.
What should you do? If you haven't installed the update, consider pausing updates for a while. This allows Microsoft time to investigate fully and release a patch. Windows 11 Home allows you to pause updates for over a month. This cautious approach is advisable, given that the potential consequences of encountering the boot failure could be quite severe.
Microsoft is actively investigating the issue. Keep an eye on the Windows release health dashboard for further information and updates on the situation.
Have you experienced this issue? Share your experiences and thoughts in the comments below.
