Skip to content
anavem.com logoanavem.com logo
About
LatestAll updates
Windows power management (Modern Standby / S3)TutorialsWindows

How to Disable Modern Standby and Enable S3 Sleep in Windows 10/11

Disable Modern Standby (S0 Low Power Idle) on Windows 10/11 with the PlatformAoAcOverride registry value to fall back to traditional S3 sleep - but only where the firmware supports S3. This guide shows how to verify support first, back up, apply the change safely, and revert.

By Emanuel De Almeida

13 min read
Difficulty
Intermediate
Time required
15 - 25 minutes
Steps
7
Platform
Windows power management (Modern Standby / S3)
Version
Windows 10 (20H2+) and Windows 11
How to disable Modern Standby and enable traditional S3 sleep in Windows 10 and Windows 11, including registry changes.
View full image
Table of contents

Quick Answer

Go to the steps

Run powercfg /a to confirm S3 exists in firmware. If it does, back up, set PlatformAoAcOverride to 0 under HKLM\SYSTEM\CurrentControlSet\Control\Power, reboot, and re-check powercfg /a. If S3 is firmware-unsupported, don't apply the change - you'd lose sleep entirely.

  1. Run powercfg /a and check whether S3 is present or firmware-unsupported.
  2. Create a restore point and export the Power registry key.
  3. Set PlatformAoAcOverride to 0 (only if S3 is firmware-supported).
  4. Reboot and re-run powercfg /a to confirm the sleep state.
  5. If sleep breaks, delete the value and reboot to revert.
Admin path
regedit > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power > New DWORD (32-bit) PlatformAoAcOverride = 0 > reboot
Command
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Power" /v PlatformAoAcOverride /t REG_DWORD /d 0 /f

Expected result: After reboot, powercfg /a lists Standby (S3) as available and Standby (S0 Low Power Idle) as unavailable - but only if the firmware supports S3.

Key takeaways

  • How to check whether your PC supports S3 sleep, safely disable Modern Standby (S0 Low Power Idle) with the PlatformAoAcOverride registry value, verify the result, tune power settings, and revert cleanly if S3 isn't available.
  • Modern Standby can cause overnight battery drain, heat in a bag, and unexpected wake-ups on some devices. Switching to S3 can help - but only where the firmware supports it, so verifying first prevents you from losing sleep functionality entirely.
  • The override disables Modern Standby but only reveals S3 if the firmware has it; on S0ix-only devices you'd lose sleep entirely, so verifying first and keeping a backup are what make this safe.

Introduction

Modern Standby (S0 Low Power Idle) is Microsoft's smartphone-style 'instant on' sleep model that keeps parts of the system lightly active to stay network-connected. On well-behaved hardware it works fine, but misbehaving drivers or firmware can cause significant standby drain and heat. The traditional S3 ('Suspend to RAM') model powers down almost everything except RAM, cutting standby power at the cost of a few seconds' slower wake. The key caveat, and the most common mistake: the `PlatformAoAcOverride` registry value only *disables* Modern Standby - it can reveal S3 only if your firmware actually implements S3. On many modern laptops (including many Intel Evo and gaming models) S3 isn't in the firmware at all, so disabling Modern Standby leaves you with hibernation only - no sleep. That's why Step 1 (verification) is non-negotiable.

Who this is for: Windows users and IT admins troubleshooting sleep/battery behavior on laptops or desktops.

Before you start

Access
A local administrator account (needed to edit HKLM and run elevated commands).
Environment
Windows 10 (20H2+) or Windows 11. The outcome is dictated by the device's UEFI firmware, which you cannot change with the registry.
Vendor
Microsoft
Tested environment
Windows 10/11 with administrative access; behavior depends on the device's UEFI firmware
  • Administrator permissions required
  • Backup required

The registry value and commands are the same on Windows 10 (20H2 and newer) and Windows 11; the outcome depends entirely on your device firmware.

Allow 15 - 25 minutes including a reboot and verification.

This is a change-making tutorial: it edits the registry and alters system sleep behavior. Only Step 1 (powercfg /a) is read-only.

Warning: Back up before editing the registry

Before changing anything, create a System Restore point and export the Power registry key to a .reg file (e.g. reg export "HKLM\SYSTEM\CurrentControlSet\Control\Power" C:\power_backup.reg). This lets you roll the registry back if sleep misbehaves.

Critical: If S3 is firmware-unsupported, do NOT proceed

If powercfg /a says S3's 'firmware does not support this standby state', disabling Modern Standby will not create S3 - it removes sleep entirely, leaving only Hibernate, and can cause crashes on lid close. The registry cannot add hardware support that doesn't exist.

Warning: This may break OEM features

Switching away from Modern Standby can disable Wake-on-LAN, break vendor power/thermal utilities that assume S0, and stop background sync while asleep. Major Windows feature updates or OEM firmware updates may also revert the change.

1Check which sleep states your system supports

Determine whether S3 exists in firmware before changing anything - the single most important step.

Admin path
Start (right-click) > Terminal (Admin) > powercfg /a

Right-click Start and open Terminal (Admin) or Command Prompt (Admin), then run `powercfg /a`. Read the output carefully. Three outcomes are possible: (1) S3 listed under *available* - S3 already works. (2) S3 listed under *unavailable* with 'This standby state is disabled when S0 low power idle is supported' - S3 is in firmware and the override will reveal it (good). (3) S3 unavailable with 'The system firmware does not support this standby state' - S3 is not in firmware, and disabling Modern Standby will leave you with no sleep (stop here).

PowerShell
powercfg /a

Expected result: You can clearly tell whether S3 is present in firmware (reveal-able) or genuinely unsupported (do not proceed).

Note

Only proceed to the registry change if S3 shows as available, or as disabled specifically because S0 low power idle is supported.

2Diagnose Modern Standby drain first (recommended)

Confirm Modern Standby is really the problem - often a driver is, and disabling S0 isn't needed.

Admin path
Terminal (Admin) > powercfg reports

Before committing to a power-model change, generate diagnostics. A sleep study shows how the system behaved during standby; an energy report flags inefficient drivers/devices. Update the flagged drivers and firmware first - many 'Modern Standby drain' cases are a single misbehaving driver, and fixing it is safer than switching to S3.

PowerShell
# Sleep study (Modern Standby activity)
powercfg /sleepstudy /output C:\sleepstudy.html

# Energy efficiency report (open the HTML and review errors/warnings)
powercfg /energy /output C:\energy-report.html

# See what is currently keeping the system awake
powercfg /requests

Expected result: You have a clear picture of what's draining power in standby; if it's a fixable driver, you may not need to disable Modern Standby at all.

Note

Hibernate is a good alternative for transport (a laptop in a bag) regardless of sleep model.

3Create a restore point and back up the key

Make the change trivially reversible.

Admin path
Win+R > sysdm.cpl > System Protection > Create

Create a System Restore point (Win+R then `sysdm.cpl` then System Protection then Create, or the PowerShell command below), then export the Power registry key so you have a one-click rollback file.

PowerShell
# Create a restore point
Checkpoint-Computer -Description "Before disabling Modern Standby" -RestorePointType "MODIFY_SETTINGS"

# Export the Power key for rollback
reg export "HKLM\SYSTEM\CurrentControlSet\Control\Power" C:\power_backup.reg

Expected result: A restore point exists and C:\power_backup.reg is saved; double-clicking it would restore the original Power key.

Note

If System Protection is off, enable protection for the system drive first, or rely on the .reg export.

4Check BIOS/UEFI for a sleep-state option (optional)

Some firmware exposes an S3/sleep toggle - many don't.

Admin path
Reboot > UEFI/BIOS setup > Power / ACPI settings > Sleep state

Reboot into UEFI/BIOS setup (commonly F2, F10, Del, or Esc depending on vendor) and look under power/ACPI settings for a sleep state option (sometimes 'S3', 'Legacy sleep', or a Windows/Modern-Standby toggle). If present, you can enable S3 there. If there's no such option, don't force anything at the firmware level - the registry method in the next step is what actually toggles the model in Windows. Note: some OEMs and Microsoft state the power-model switch isn't officially supported and historically suggested a clean install; in practice the registry override works on S3-capable firmware, but behavior varies by device.

Expected result: You've confirmed whether your firmware exposes an S3/sleep option; if not, proceed with the registry method.

Note

There is no CSM/Legacy-boot setting that enables S3 - CSM controls legacy boot, not sleep states. Ignore guidance that suggests it.

5Disable Modern Standby via the registry

Set the override that tells Windows to stop using Modern Standby.

Admin path
regedit > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power > New > DWORD (32-bit) Value > PlatformAoAcOverride = 0

Only do this if Step 1 showed S3 is firmware-supported. Set the `PlatformAoAcOverride` DWORD to 0 under `HKLM\SYSTEM\CurrentControlSet\Control\Power`. Use whichever method you prefer - Registry Editor (New then DWORD (32-bit) Value named `PlatformAoAcOverride`, value 0), or the command line below. Type the value name exactly as shown.

PowerShell
# Command Prompt / cmd
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Power" /v PlatformAoAcOverride /t REG_DWORD /d 0 /f

# or PowerShell
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Power" -Name "PlatformAoAcOverride" -Value 0 -Type DWord

Expected result: The PlatformAoAcOverride value exists and is set to 0. The change takes effect after a reboot.

Note

If, after rebooting, Modern Standby is still active on a stubborn device, some guides add a CsEnabled DWORD = 0 under the same key as a secondary fallback - use cautiously and keep your backup.

6Reboot, verify, and tune S3 power settings

Confirm the sleep state changed, and optimize settings for S3.

Admin path
Terminal (Admin) > powercfg /a ; Control Panel > Power Options > Change advanced power settings > Sleep

Reboot, then run `powercfg /a` again. On S3-capable firmware you should now see Standby (S3) available and S0 Low Power Idle unavailable. Test sleep (Start then Power then Sleep) and confirm the machine sleeps and wakes correctly. If S3 is active, you can tune settings: hybrid sleep isn't needed with S3, and disabling wake timers reduces unwanted wake-ups.

PowerShell
# Verify the active sleep model
powercfg /a

# Ensure standby is allowed and disable hybrid sleep (not needed with S3)
powercfg /setacvalueindex SCHEME_CURRENT SUB_SLEEP ALLOWSTANDBY 1
powercfg /setacvalueindex SCHEME_CURRENT SUB_SLEEP HYBRIDSLEEP 0
powercfg /setdcvalueindex SCHEME_CURRENT SUB_SLEEP HYBRIDSLEEP 0
powercfg /setactive SCHEME_CURRENT

# (Optional) disable wake timers via the GUI:
# Power Options > Change advanced power settings > Sleep > Allow wake timers > Disable

Expected result: powercfg /a confirms S3 is the active model, and a manual sleep/wake test works. If sleep is broken instead, go to Step 7 and revert.

Note

If the machine now shows only Hibernate (no S3), your firmware doesn't support S3 - revert in Step 7.

7Troubleshoot, revert, and manage at scale

Fix wake issues, roll back cleanly, or deploy the setting across a fleet.

Admin path
Terminal (Admin) > powercfg /requests ; regedit > delete PlatformAoAcOverride to revert

If the PC won't sleep or wakes immediately, find the cause with `powercfg /requests` and disable wake for the culprit device. If sleep is broken or you want Modern Standby back, delete the override and reboot. For managed environments, note there's no native Intune CSP for Modern Standby - deploy the registry value via a provisioning package, a remediation/PowerShell script, or a registry payload.

PowerShell
# See what blocks/wakes sleep, and which devices can wake the PC
powercfg /requests
powercfg /devicequery wake_armed
powercfg /devicedisablewake "Intel(R) Ethernet Connection"

# Revert: remove the override to restore Modern Standby (then reboot)
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Power" /v PlatformAoAcOverride /f

# Fleet deployment (no Intune CSP exists): push the same reg value via script/provisioning
# reg add "HKLM\SYSTEM\CurrentControlSet\Control\Power" /v PlatformAoAcOverride /t REG_DWORD /d 0 /f

Expected result: Wake issues are resolved, or the override is removed and Modern Standby returns after reboot; at scale, the value is deployed via script/provisioning.

Note

After reverting, powercfg /a should show S0 Low Power Idle again (on Modern Standby-capable firmware).

Confirm the sleep model changed as intended

Confirm configuration

Success means powercfg /a reflects the model you want and a manual sleep/wake test works. On S3-capable firmware you'll see Standby (S3) available and S0 unavailable; the machine sleeps low-power and wakes in a few seconds.

Normal result: powercfg /a lists Standby (S3) as available and S0 Low Power Idle as unavailable, and the PC sleeps and wakes correctly.

Abnormal result: powercfg /a shows only Hibernate (no S3) - the firmware doesn't support S3, so revert; or the PC crashes/immediately wakes - check powercfg /requests, or revert by deleting the override.

Troubleshooting

After the change, only Hibernate is available (no S3)

Critical

Cause: The firmware doesn't implement S3, so disabling Modern Standby removed sleep entirely.

Delete the PlatformAoAcOverride value and reboot to restore Modern Standby; the registry cannot add S3 that firmware lacks.

PC crashes or hard-hangs when entering sleep

Critical

Cause: Firmware/driver can't handle S3 on this device.

Force shutdown (hold power), boot, and revert by deleting the override; consider staying on Modern Standby.

PC won't sleep or wakes immediately

Warning

Cause: A device or process is holding a wake/sleep request.

Run powercfg /requests to find the culprit, then disable wake for the device with powercfg /devicedisablewake.

Wake-on-LAN or a vendor utility stopped working

Note

Cause: OEM features that assumed Modern Standby (S0) may not function under S3.

Weigh the trade-off; if these features matter, revert to Modern Standby by deleting the override and rebooting.

S3 shows unavailable but firmware clearly supports it

Note

Cause: S3 is disabled because S0 low power idle is enabled.

That message ('disabled when S0 low power idle is supported') means the override will reveal S3 - proceed with the registry change.

Frequently asked questions

Will this actually give me S3 sleep?

Only if your firmware implements S3. The PlatformAoAcOverride value disables Modern Standby; it can't add S3 support that isn't in the firmware. If powercfg /a says the firmware doesn't support S3, you'll be left with hibernation only - so verify first.

Is editing this registry value safe?

It's a documented, easily reversible override, but it changes sleep behavior system-wide. Always create a restore point and export the Power key first, and be ready to revert if sleep misbehaves.

How do I revert to Modern Standby?

Delete the PlatformAoAcOverride value (reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Power" /v PlatformAoAcOverride /f) and reboot. Modern Standby returns on firmware that supports it.

Does disabling Modern Standby break Windows Update or performance?

No. Active performance is unchanged, and updates still install while the PC is awake. You do lose 'connected standby' behavior (background sync, some notifications, Wake-on-LAN) while asleep.

Why does Microsoft say switching isn't supported?

Microsoft's guidance notes the power model isn't officially switchable via UEFI and historically suggested a clean install, and many manufacturers no longer ship S3. In practice the registry override works on S3-capable firmware, but results vary by device - hence verifying and backing up first.

Can I deploy this across many devices with Intune?

There's no native Intune CSP for Modern Standby. Push the same registry value using a provisioning package, a remediation/PowerShell script, or a registry payload - and validate each hardware model, since firmware support for S3 varies.

Conclusion

You verified whether S3 exists in firmware with powercfg /a, backed up, and (where supported) set PlatformAoAcOverride to 0 to disable Modern Standby and fall back to S3 sleep - then confirmed with powercfg /a and kept a clean way to revert.

The override disables Modern Standby but only reveals S3 if the firmware has it; on S0ix-only devices you'd lose sleep entirely, so verifying first and keeping a backup are what make this safe.

Main path
powercfg /a to verify then back up then set PlatformAoAcOverride=0 under HKLM\SYSTEM\CurrentControlSet\Control\Power then reboot then re-check powercfg /a.

Sources4

Reader actions
Was this helpful?
Rate this articleRate
45 readers viewed this article

Reader reviews

Rate this articleBe the first to rate
No written reviews yetRate the article above, or be the first to share your experience.

More to explore