Windows only sleeps when its idle timer expires and nothing is actively holding it awake. A download, a browser tab playing audio, a stuck driver, or a scheduled wake timer can block sleep indefinitely — silently, with no warning on screen. One command names the exact culprit: powercfg /requests.
Open Terminal or Command Prompt as Administrator and run:
This prints every active power request — the things currently telling Windows do not sleep — and exactly which process or driver made it, grouped under a few categories: SYSTEM (blocks sleep entirely), DISPLAY (keeps the screen on), and EXECUTION (keeps an app running unthrottled). If you see a line under SYSTEM like [PROCESS] chrome.exe or [DRIVER] Realtek Audio — that's the culprit, named and confirmed.
| Culprit | What you'll see | Typical fix |
|---|---|---|
| Audio playing anywhere | A browser or app under SYSTEM/EXECUTION | Pause or close the tab/app |
| Download or backup in progress | [PROCESS] under SYSTEM naming the app | Let it finish, or whitelist it |
| Driver won't release | [DRIVER] — network, audio, or \Driver\srvnet | Update or reconfigure the driver |
| Wake timer armed | Not in /requests — check powercfg /waketimers | Disable the scheduled task or its wake trigger |
| Device armed to wake it | Not in /requests — check powercfg /devicequery wake_armed | powercfg /devicedisablewake "device name" |
Once powercfg /requests names the culprit, close the app, end the download, or update the driver. To force Windows to ignore one specific request without closing anything, run powercfg /requestsoverride. Stray wake timers live under Power Options → Sleep → Allow wake timers, or can be disabled directly on the task in Task Scheduler.
Best for: A one-off mystery you want solved right now. Limit: It only fixes today's culprit — tomorrow a different app can quietly do the exact same thing.
That's the real problem with the manual route: it's a recurring problem, not a one-time fix. Every new download, media tab, or driver update can quietly re-block sleep, and you only find out when the fans are still roaring at 2 a.m. PowerDoze flips the model — instead of hunting down whatever's holding your PC awake today, you decide up front which apps and contexts are allowed to (a download, a render, a meeting, a fullscreen game), add them to the keep-awake whitelist, and let a sleep schedule handle everything else automatically.
Best for: Anyone tired of re-diagnosing the same problem every few weeks. The only approach that doesn't need you to remember to check.
Windows only sleeps when the idle timer expires and nothing is actively holding it awake. Any open power request — from a download, background audio, or a stuck driver — overrides the timeout completely, no matter how it's configured.
Open Command Prompt or Terminal as Administrator and run powercfg /requests. It lists every active power request and names the exact process or driver behind it.
SYSTEM blocks sleep entirely. DISPLAY keeps the screen on (system sleep may still be allowed). EXECUTION keeps an app running unthrottled. A SYSTEM entry is almost always why your PC won't sleep.
Run powercfg /waketimers for scheduled wake tasks, and powercfg /devicequery wake_armed for devices — network adapters, mice, keyboards — allowed to wake it.
Close the app, update the driver, or run powercfg /requestsoverride to force Windows to ignore that request. Disable stray wake timers under Power Options → Sleep, or in Task Scheduler.
PowerDoze doesn't hunt down rogue requests for you — powercfg /requests is still the fastest manual diagnosis. What it automates is prevention: whitelist the apps that should legitimately keep the PC awake, and a schedule handles sleep for everything else.
PowerDoze is free to download. Scheduled sleep rules and the keep-awake whitelist — everything this page recommends — are available in the free tier, no Pro upgrade needed.
Download free for Windows 10/11See also: Windows sleep settings guide · Stop sleep during downloads · More use cases