Performance

Windows PC will not sleep or wakes immediately

Distinguish an idle sleep blocker from an immediate wake event using power settings, read-only powercfg reports, and controlled device tests.

Updated: September 17, 2026
Reading time: 5 min read
Windows support: Windows 11 · Windows 10

Quick diagnosis

A display turning off, a computer entering sleep, and a computer waking are different events. First determine whether Windows never starts sleeping or successfully sleeps and then wakes. Each case needs different evidence; disabling every wake feature can hide the cause and remove useful access.

Symptoms

The display turns off but the PC remains active
Manual Sleep works but idle sleep never occurs
The PC wakes seconds after selecting Sleep

Likely causes

Separate plugged-in or battery sleep timers set to Never
An application or driver requesting continued operation
A device or scheduled timer waking the system

Quick reversible checks

Save work, finish active transfers, and close media playback or conferencing apps normally.
Check both display-off and sleep timeouts for the current power source.
Select Sleep manually once and record whether it stays asleep or immediately resumes.

Establish a repeatable sleep test

Open the power settings under System in Settings: Windows 11 uses Power & battery or Power, while Windows 10 uses Power & sleep. Names vary by device and release. Record the existing timers before setting a short temporary sleep timeout for the power source being tested.

Leave the mouse and keyboard untouched during the idle test. If manual Sleep works but the idle timer does not, investigate an idle blocker. If the PC resumes immediately, collect wake evidence instead. Fan noise alone is not a reliable way to identify the sleep state.

Check which sleep states the PC supports

Open Terminal or Command Prompt as administrator and run the report below. It lists available sleep states and reasons others are unavailable. Some PCs use Modern Standby rather than traditional S3 sleep; absence of S3 is not by itself a defect.

If Sleep is unavailable, retain the stated reason and compare it with the PC maker’s documentation. Do not force a different sleep model through registry edits or undocumented firmware changes.

powercfg /a

Identify a request preventing idle sleep

While the idle failure is happening, run powercfg /requests in the elevated terminal. It reports application and driver power requests. Close an identified user application normally, rerun the report, and repeat the idle test.

A listed request may be intentional, such as an active recording. A report with no requests is only a snapshot, so compare it at the time the fault occurs. Avoid request overrides: they can force sleep while software still needs the machine awake.

powercfg /requests

Collect evidence immediately after an unwanted wake

Run the following reports after the PC wakes. The last-wake report concerns the previous sleep transition; active wake timers describe scheduled wake opportunities. A timer’s presence is not proof it caused the event, and an empty report does not prove no wake occurred.

Correlate the reported device or task with the time you observed. If a USB accessory is implicated, safely disconnect that accessory and repeat the same test, keeping another way to wake and control the PC.

powercfg /lastwake
powercfg /waketimers

Change only the confirmed cause

For an identified device, inspect its Device Manager power options if available. Record any change to its permission to wake the computer, then test again. Do not disable every keyboard, network, and mouse wake option together.

If a driver remains implicated after peripherals and applications are isolated, use the PC maker’s driver guidance. Compare before and after one change. Leave organization-managed maintenance schedules and remote wake requirements to the administrator.

Verification

Test both manual Sleep and the idle timeout with the original workload closed.
Wake the PC deliberately and confirm display, keyboard, and network operation.
Restore the desired power timers and repeat on battery and mains separately when applicable.

When to stop

Seek device-maker or administrator help if the PC overheats, cannot resume without forced shutdown, reports unsupported sleep states you do not understand, or requires managed wake policies. Preserve the powercfg output and the exact sleep/wake timing instead of applying broad power resets.

Review the safe troubleshooting workflow before any broader recovery step.