Microsoft has acknowledged that a segment of Windows 11 systems may experience startup failures following the installation of the KB5058405 cumulative update, which was rolled out during this month’s Patch Tuesday. Users encountering this issue are met with the 0xc0000098 recovery error related to ACPI.sys, indicating that the operating system could not be loaded and requires repair.
Details of the Issue
The ACPI.sys file is a crucial component of the Windows Advanced Configuration and Power Interface (ACPI) driver, which plays a vital role in power management and device configuration for systems equipped with an ACPI BIOS. In a recent update to the Windows release health dashboard, Microsoft stated, “We are investigating reports of the May 13, 2025 Windows security update (KB5058405) failing to install on some Windows 11, version 22H2 and 23H2 devices.”
The error message displayed to users reads: “Your PC/Device needs to be repaired. The operating system couldn’t be loaded because a required file is missing or contains errors.” This known issue predominantly affects Windows 11 22H2 and 23H2 systems within enterprise settings, particularly impacting Azure Virtual Machines, Azure Virtual Desktop, and on-premises virtual machines hosted on platforms like Citrix or Hyper-V.
Microsoft has reassured home users operating Windows Home or Pro editions that they are less likely to encounter these issues, as the affected virtual machines are primarily utilized in IT environments. The company is actively investigating the matter and has promised to share further updates as they become available.
Earlier this month, Microsoft addressed another known issue that was obstructing Windows 11 24H2 feature updates via Windows Server Update Services (WSUS) following the installation of the April 2025 security updates. Additionally, the company previously issued emergency out-of-band updates to resolve a Windows 10 bug that inadvertently placed affected PCs into BitLocker recovery mode after the May 2025 security updates were applied.
In April, Microsoft also tackled a “latent code issue” that caused certain devices to upgrade to Windows 11 automatically, despite existing Intune policies designed to prevent such upgrades.
