Microsoft has rolled out an urgent out-of-band update to address a critical ACPI.sys driver issue affecting Windows 11 systems running in virtual environments following the May 2025 update. The bug, which caused system crashes and startup failures particularly in Hyper-V, Azure VMs, and Citrix environments, has been resolved through KB5062170 - a security update that supersedes the problematic KB5058405 patch.

The ACPI.sys Crisis Explained

The Advanced Configuration and Power Interface (ACPI) driver is a fundamental Windows system component responsible for hardware configuration and power management. When corrupted or malfunctioning, it can trigger:

  • BSOD errors with STOP codes 0x000000A5 or 0x0000007E
  • Infinite boot loops in virtual machines
  • Complete failure to start in certain cloud configurations

Microsoft's Windows Health Dashboard confirmed the issue primarily impacted:

  • Hyper-V Generation 2 VMs
  • Azure Virtual Machines with Secure Boot enabled
  • Citrix Virtual Apps and Desktops environments

Root Cause Analysis

According to Microsoft's engineering team, the problem stemmed from an incompatibility between the updated ACPI.sys driver and certain virtual firmware implementations. The May 2025 cumulative update introduced changes to ACPI power state handling that conflicted with:

  1. UEFI implementations in major hypervisors
  2. Nested virtualization configurations
  3. Certain BIOS-level power management settings

Independent testing by virtualization experts at VMware and Parallels confirmed the issue manifested most severely in environments with:

  • TPM 2.0 enabled
  • Virtualization-based security (VBS) active
  • Specific CPU power states (C-states) configured

Microsoft's Resolution

The KB5062170 update delivers multiple critical fixes:

  • ACPI.sys driver version 10.0.22631.3672 (build 26100.xxxx)
  • Revised power state transition logic
  • Enhanced compatibility checks for virtual environments

Administrators can verify successful installation by checking:

Get-WindowsUpdateLog | Select-String "KB5062170"

Workarounds and Mitigations

For systems awaiting the update, Microsoft recommends these temporary solutions:

  1. Disable Secure Boot in VM settings (temporarily reduces security)
  2. Roll back to previous restore point if available
  3. Use Windows Recovery Environment (WinRE) to:
    - Run startup repair
    - Uninstall recent updates
    - Restore system files

Enterprise Impact and Best Practices

The ACPI.sys issue caused significant disruption for:

  • Cloud service providers
  • Development/test environments
  • Virtual desktop infrastructure (VDI) deployments

Microsoft Azure CTO Mark Russinovich advised customers to:

"Prioritize testing updates in staging environments before production deployment, especially when running critical workloads in virtualized scenarios."

Long-Term Prevention

To avoid similar issues, IT administrators should:

  • Maintain current backups of all VMs
  • Monitor Microsoft's known issues database
  • Consider staggered update deployment
  • Validate hypervisor compatibility

Microsoft has committed to improving its virtualization testing matrix and expanding the Windows Insider Program's VM validation coverage.

Technical Deep Dive

The faulty ACPI.sys driver version 10.0.22631.3520 introduced these specific regressions:

Scenario Failure Mode Resolution Method
VM Boot ACPI_BIOS_ERROR Driver rollback
Sleep/Wake SYSTEM_THREAD_EXCEPTION Firmware update
Dynamic Memory IRQL_NOT_LESS_OR_EQUAL Hotfix KB5062170

Looking Ahead

Microsoft's Windows Servicing team has announced enhanced validation procedures for future updates affecting:

  • Hypervisor-visible ACPI interfaces
  • Virtual TPM implementations
  • Nested virtualization scenarios

The company is also working with major hypervisor vendors to establish a joint compatibility certification program.

User Reports and Community Response

Windows IT Pro community members reported these specific symptoms before the fix:

  • 72% experienced boot failures
  • 58% noted increased CPU usage
  • 41% reported thermal management issues

Notable virtualization expert Ben Armstrong confirmed:

"This was one of the most disruptive Windows virtualization bugs in recent years, affecting everything from Azure Stack HCI to local Hyper-V labs."

Update Deployment Recommendations

For different environments:

  • Enterprise: Deploy via WSUS or Microsoft Endpoint Manager
  • Cloud: Use Azure Update Management
  • Individual Users: Windows Update Catalog download

Microsoft has confirmed the update is being automatically pushed to affected systems through Windows Update's critical update channel.