Fix 0x00000474: Change power state vetoed by driver

You're not crazy — Windows blocked sleep for no obvious reason

Error 0x00000474 pops up when you try to put your machine to sleep, and some driver or app says "no." The system doesn't tell you which one right away. This is common on Windows 10 22H2 and Windows 11 with older USB drivers, Bluetooth stacks, or network adapters. Let's jump straight to what actually fixes it.

The real fix: find and disable the vetoing driver via power policy

1. Open Command Prompt as administrator.
2. Run:

   powercfg /lastwake

   This shows what woke the system last. Often it's irrelevant here but quick to check.
3. Run:

   powercfg /requests

   This lists any driver or service actively holding a system sleep veto. You'll see something like "A driver is preventing the system from entering sleep" with details.
4. If that gives you nothing — and it often won't for this specific error — run:

   powercfg /devicequery all_devices_that_are_not_wake-capable

   Look for devices with Veto in their power state. Usually it's a HID-compliant mouse, Realtek PCIe GBE Family Controller, or a Bluetooth radio.
5. Once you identify the device, disable its ability to veto sleep:

   powercfg /devicedisablewake "Device Name Here"

   For example: powercfg /devicedisablewake "Realtek PCIe GBE Family Controller"
6. Reboot and test sleep.

If that doesn't work — and it fails on some machines because the veto comes from a kernel driver that powercfg can't see — you go to the registry.

Registry path for power policy — only touch this if powercfg fails

Open Registry Editor, go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238C9FA8-0AAD-41ED-83F4-97BE242C8F20\0e796fdb-100d-47d6-a2d5-f7d2daa51f51

This is the GUID for the System Sleep Veto policy. Set Attributes DWORD to 2 — this hides it from the GUI but doesn't fix the root cause. Better yet, look at the subkeys under PowerSettings for any key named after your offending driver's vendor. For Intel Management Engine or AMD SMBus drivers, you'll find keys like e69603a9-4b7f-4b9a-8b1c-9c9b1c2d3e4f (varies). Delete the key for the vetoing driver — back up first.

Why step 3 works

What's actually happening here is that Windows' power manager sends an IRP_MJ_POWER request with minor code IRP_MN_SET_POWER to each driver in the device stack. If any driver returns STATUS_VETO (exactly your error 0x00000474), the entire sleep transition aborts. The driver doesn't have to be buggy — it could be holding an open handle to a COM port or a network share. powercfg /requests reads from the same power manager queue that logs the veto, but some drivers (especially HID and Bluetooth) report the veto at a lower IRQL level that powercfg's user-mode tool can't query. That's why you sometimes need the registry or a kernel debugger to see it.

Less common variations of the same root cause

1. USB Selective Suspend veto

Same error 0x00000474, but only when the system tries to suspend individual USB ports. Check Event Viewer under System for source Kernel-Power event ID 506. The fix: disable USB selective suspend in Power Options → Change plan settings → Change advanced power settings → USB settings.

2. Network adapter wakes but then vetoes sleep

If powercfg /lastwake shows your NIC, but sleep still fails with 0x00000474, the driver is allowing wake but blocking the initial sleep. Go to Device Manager, find your network adapter, Properties → Power Management, uncheck "Allow this device to wake the computer." Then re-test.

3. Third-party antivirus or VPN filter driver

Some VPN drivers (looking at you, OpenVPN TAP) install a filter that intercepts power IRPs. If the above steps fail, boot into Safe Mode with Networking and try sleep there. If it works, the veto is from a non-Microsoft driver. Uninstall the VPN client and use the built-in Windows VPN or WireGuard instead.

4. BIOS-level power state conflict

On Dell and Lenovo laptops with Modern Standby (S0ix), the error can be spurious. Update your BIOS to the latest version — vendors fixed many of these in 2023–2024 patches.

Prevention — stop it from coming back

• Keep your chipset drivers current. Intel and AMD publish monthly updates for their power management drivers.
• Disable wake timers for devices you don't need. Run powercfg /devicequery wake_armed and disable any device you don't explicitly need to wake your PC (mice, keyboards, network adapters).
• Avoid using generic Windows drivers for USB peripherals — download the manufacturer's driver. Generic drivers often lack proper power IRP handling.
• If you run VMs, shut them down before sleep. VirtualBox and VMware add veto-prone filter drivers.

That's it. No fluff, no reboot loops, just the actual fix for 0x00000474.