Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Sleep works manually but not automatically | Check timers, screen/sleep settings and power requests |
| PC wakes immediately | Check wake devices and timers |
| Sleep option is missing | Check power states, policy and graphics/chipset drivers |
| Only one app prevents sleep | Update or close that app and inspect its power request |
Diagnose sleep entry and blockers with evidence first
Try Sleep once and record whether the PC ignores the command, wakes immediately, turns off the display only, or returns to the desktop. Note any active media, downloads, or connected devices.
Check whether a specific app, driver, device, or power request is blocking sleep. If the PC sleeps cleanly in a minimal startup state, keep the repair focused on the blocking component.
Complete these focused checks: save work and test manual Sleep; run powercfg /requests in an elevated Terminal; check screen and sleep timeouts for the active power mode; disconnect unnecessary USB devices for comparison. Take screenshots or notes before changing firmware, encryption, recovery, driver or power settings. Those records provide a return path if the first repair does not help.
Apply Windows, chipset, graphics, network, and firmware updates only when they relate to the identified sleep blocker or recent change.
Save open work before sleep tests and keep recovery keys available before firmware changes. Do not experiment with unsupported registry tweaks just to force sleep.
Find active power requests
Use powercfg /requests and close or update the named media, driver or application. Do not create permanent overrides before fixing the owner.
Try Sleep once and record whether the PC ignores the command, wakes immediately, turns off the display only, or returns to the desktop. Note any active media, downloads, or connected devices.
Check whether a specific app, driver, device, or power request is blocking sleep. If the PC sleeps cleanly in a minimal startup state, keep the repair focused on the blocking component.
Complete these focused checks: save work and test manual Sleep; run powercfg /requests in an elevated Terminal; check screen and sleep timeouts for the active power mode; disconnect unnecessary USB devices for comparison. Take screenshots or notes before changing firmware, encryption, recovery, driver or power settings. Those records provide a return path if the first repair does not help.
Apply Windows, chipset, graphics, network, and firmware updates only when they relate to the identified sleep blocker or recent change.
Save open work before sleep tests and keep recovery keys available before firmware changes. Do not experiment with unsupported registry tweaks just to force sleep.
Find active power requests
Use powercfg /requests and close or update the named media, driver or application. Do not create permanent overrides before fixing the owner.
Before changing sleep settings, compare manual sleep with automatic idle sleep. If manual sleep works but the PC never sleeps on its own, focus on timers, power requests, media activity, and timeout settings.
1Verification checkpoint
- Repeat the original action once.
- After addressing one blocker, invoke Sleep again and verify the PC enters sleep and remains there for a normal test interval.
- Restore diagnostic changes that did not help.
Check timers and connected devices
Review wake timers, network sharing and USB devices. Test with docks, controllers and external drives disconnected.
Review wake timers, network sharing and USB devices. Test with docks, controllers and external drives disconnected.
Use power requests or recent activity to identify the process, driver, or service keeping the system awake. Do not close or disable security, backup, or update services unless the evidence points directly to them.
2Verification checkpoint
- Repeat the original action once.
- After addressing one blocker, invoke Sleep again and verify the PC enters sleep and remains there for a normal test interval.
- Restore diagnostic changes that did not help.
Repair the power and driver layer
Install chipset, graphics and network updates from supported sources and restore default power settings only after recording custom choices.
Install chipset, graphics and network updates from supported sources and restore default power settings only after recording custom choices.
When testing connected devices, remove docks, controllers, external drives, and USB accessories one at a time. A clean result after one removal is more useful than disconnecting everything together.
3Verification checkpoint
- Repeat the original action once.
- After addressing one blocker, invoke Sleep again and verify the PC enters sleep and remains there for a normal test interval.
- Restore diagnostic changes that did not help.
Interpret the result before escalating
Manual sleep working while idle sleep fails usually means Windows is being told to remain awake or the idle timeout is being reset. That is different from a machine that cannot enter sleep at all.
If a specific application appears in power requests, close that application and retest before changing drivers or power plans. If the request disappears but sleep still fails, continue to the next blocker rather than assuming the app was the only cause.
If the system sleeps correctly in a clean boot but not during normal startup, re-enable startup items in small groups until the sleep blocker returns.
Verify the fix and choose the safe escalation
Set a short temporary sleep timeout and leave the PC untouched. Confirm that the display turns off and the system actually enters sleep rather than only blanking the screen.
Restore your normal timeout after the test and repeat once with your usual applications open. A fix that works only in an empty desktop session may still have an application-level blocker.
If power requests are clear and the PC still never sleeps, move to chipset, graphics, network, firmware, and supported repair checks instead of repeatedly resetting the same timeout.
Technical order checked against current Microsoft guidance. Exact controls vary by Windows build, hardware, edition and organization policy.
Frequently asked questions
What is powercfg /requests?
It lists applications and drivers currently asking Windows to stay awake.
Why does my PC sleep manually but not automatically?
A timer, power request, media session or incorrect timeout may block idle sleep.
Can USB devices prevent sleep?
Yes. Faulty or active USB devices and their drivers can block or immediately end sleep.