Windows 11 Sleep Mode Not Working? 8 Fixes That Work

Windows 11 sleep mode not working is really three separate problems wearing one symptom. The PC won’t sleep, it sleeps but wakes instantly, or the sleep option is missing entirely. Each needs a different fix, and the worst move is changing random power settings before you know which one you have. We tested these steps on a desktop running Windows 11 24H2 and a laptop on 23H2.

#Why Is Sleep Mode Not Working in Windows 11?

Sleep is a negotiation between Windows, your power plan, and every device that’s allowed to wake the system. When sleep misbehaves, one of those three is the cause, and the symptom tells you which. Guessing wastes time and can disable a wake feature you actually want.

Match your exact symptom to the right starting point before you touch a single setting.

Symptom	Likely cause	First action
PC never sleeps on its own	Power plan timers off	Check screen and sleep timers
Sleeps, then wakes instantly	A device or wake timer	Run powercfg /lastwake
Wakes a few minutes later	Scheduled wake timer	Check powercfg /waketimers
Sleep option missing or grayed	Driver or Modern Standby	Check available sleep states
Only the monitor won’t sleep	Screen timeout setting	Adjust the screen timeout

The wake-source commands below turn a frustrating guessing game into a two-minute diagnosis.

#Check Power and Screen/Sleep Settings First

Start with the obvious. Open Settings > System > Power & battery > Screen and sleep and confirm the sleep timer isn’t set to Never. A surprising number of “won’t sleep” reports are simply a timer that got switched off.

According to Microsoft’s guidance on how to sleep, shut down, or hibernate your PC, sleep uses very little power and puts you instantly back where you left off, so it’s worth getting working rather than reaching for full shutdowns. Set both the screen and sleep timers to a real value and test.

Also check the power mode. Best performance mode and some manufacturer “gaming” plans push back sleep timers or disable them outright, so switch to Balanced while you troubleshoot.

If only the monitor stays awake while the PC otherwise idles fine, that’s a screen-timeout setting, not a sleep failure. Separate the two before you go deeper.

#Find What Woke the PC With powercfg

When the PC sleeps but wakes instantly or a few minutes later, stop guessing and ask Windows directly. Open Command Prompt as administrator and run powercfg /lastwake. According to Microsoft’s powercfg reference, this 1 command reports exactly what woke the system from the last sleep transition.

The output names the culprit. It might read a mouse, a network adapter, or a wake timer. That single line usually solves the mystery.

When we tried this on the 24H2 desktop that kept waking at night, powercfg /lastwake pointed at the network adapter’s wake-on-LAN setting. One toggle fixed it. No power-plan roulette required. A flaky network adapter can cause other grief too, like the drops in our windows 11 wifi keeps disconnecting guide.

Next, run powercfg /devicequery wake_armed to list every device currently allowed to wake the PC. Microsoft’s powercfg command-line reference documents this query flag as the way to see which devices are armed to wake the system, and it’s the shortlist you’ll work from in the next section.

#What If Sleep Is Missing or Grayed Out?

A missing or grayed-out sleep option is a different animal. It usually means Windows can’t enter the sleep state your hardware claims to support.

Run powercfg /availablesleepstates as administrator. It reports which sleep states your system supports and, helpfully, tries to explain why any unavailable state is missing. If standby (S3) is listed as unsupported, that’s a hardware or firmware answer, not a settings one.

Many newer laptops use Modern Standby (S0 low-power idle) instead of classic S3 sleep. That’s expected on those machines, not a fault. Don’t chase a classic “Sleep” entry that was never going to exist there, because the behavior you’re seeing is exactly how the hardware was designed to idle, and forcing the old S3 path is usually impossible without a firmware that simply doesn’t offer it.

If sleep vanished after an update, a chipset or graphics driver is the likely cause, and rolling it back often restores the option. A shutdown that hangs is a related but separate issue covered in our windows 11 wont shut guide.

#Disable Wake Timers and Device Wake Permissions

Now act on what powercfg named. If a device is waking the PC, open Device Manager, find that device, and on its Power Management tab clear Allow this device to wake the computer. A USB mouse on a sensitive desk is a classic offender that nudges the system awake.

Be careful here, though. If you wake a desktop with the keyboard, don’t blanket-disable USB wake. Disable only the device powercfg /lastwake blamed.

For scheduled wakes, run powercfg /waketimers. Microsoft’s reference states that this command enumerates the active wake timers, which are the scheduled tasks and updates that pull the PC out of sleep. To stop most of them, open the advanced power settings, expand Sleep > Allow wake timers, and set it to Disable.

A maintenance task or a pending update is a frequent timer-based waker. If yours traces to Windows Update, our windows 11 update stuck guide covers settling the update so it stops scheduling wakes. To find a third-party background app that’s blocking sleep or scheduling wakes, Microsoft’s guide to how to perform a clean boot in Windows isolates the offender by starting with only essential services.

#Update Chipset, GPU, and Network Drivers Carefully

When sleep broke after an update, or powercfg keeps pointing at a network adapter or graphics device, the driver is your target. Chipset, GPU, and network drivers all touch power states directly.

Update them from the manufacturer first, not just Windows Update, since OEM power drivers are better tuned. If sleep worked before a recent driver change, roll it back instead from the Properties > Driver tab.

BIOS and firmware are the last software-adjacent stop. Some boards hide wake-from-USB or ErP/deep-sleep settings in firmware, and a BIOS update occasionally fixes stubborn S3 problems that nothing in Windows touches. Treat this as a careful last step, not a first move, and only once the powercfg diagnosis has come up completely empty and a clean driver reinstall hasn’t moved the needle either.

Display-driver issues that disrupt sleep can also surface as detection problems, covered in our windows 11 second monitor guide. A bad power driver can even crash on wake, which our windows 11 bsod fix guide untangles.

#Bottom Line

Don’t guess at random power settings. If Windows wakes immediately, run powercfg /lastwake to name the source, then disable only that device or wake timer rather than changing everything in sight. If sleep is missing entirely, check available sleep states and look at driver, firmware, or Modern Standby before assuming Windows is broken. The powercfg commands turn a guessing game into a targeted fix.

#Frequently Asked Questions