Windows 11 Update causes Error State 43 after two-stage reboot

[padixa]

Issue: Windows 11 Update causes Error State 43 after two-stage reboot

Environment

• GPU: AMD Radeon 890M
• Hypervisor: Proxmox VE (PVE) with VFIO PCI passthrough
• Guest OS: Windows 11
• Service version: Build date 2020/8/22 17:45:50

Problem Description

After a Windows Update reboot, the GPU is not recognized and shows Error State 43 in Device Manager. The VM must be gracefully shut down, then the entire PVE host must be power-cycled before the GPU is recognized again.

Normal reboots (not caused by Windows Update) work fine.

Root Cause (suspected)

This matches the "Unsuccessful reboots" scenario documented in the README, specifically the two-stage Windows Update reboot:

1. Windows Update initiates reboot → enters "Installing updates, step X of Y" screen
2. On this intermediate screen, Windows starts all services including RadeonResetBugFixService
3. However, Windows does not invoke the normal pre-shutdown sequence on this intermediate screen
4. The service starts and tries to disable the GPU, but it can't complete properly
5. Second reboot → GPU is in inconsistent state → Error 43

Note: This is on Windows 11, whereas the README states testing was primarily on Windows 10 VMs on Hyper-V.

Relevant Log Entries

Startup log after the failed update reboot:

[2026-04-12 01:18:49.984] Error: [ServiceBase.OnStart] [Startup] [Enabling AMD video] Device is in error state: 43
[2026-04-12 01:18:49.986] Error: [ServiceBase.OnStart] [Startup] [Enabling AMD video] Device is in error state: 43

Shutdown log from the update reboot:

[2026-04-12 02:45:28.331] Error: [ServiceBase.OnStop] [Shutdown] [Disabling AMD video] Device is in error state: 43

Questions

1. Is Windows 11 officially supported / tested?
2. Is there a way to detect the two-stage Windows Update reboot and handle it differently?
3. Could the service detect when it's starting from the "installing updates" intermediate screen and skip the GPU enable/disable cycle?

Workaround

Until this is fixed, the only workaround is to gracefully reboot the entire PVE host (not just the VM).

---

Reported from: Proxmox VE + AMD Radeon 890M + Windows 11