Windows 11 PC wakes itself? Trace the wake source

Put a Windows 11 PC to sleep, walk away, and come back to a lit screen? Start by checking what Windows recorded, then separate a wake event from a device or timer that is only allowed to wake the PC.

The built-in Powercfg checks below narrow down what to test. powercfg /lastwake reports the most recent sleep-to-wake transition, powercfg /waketimers lists timers active now, and powercfg /devicequery wake_armed shows devices currently permitted to wake the PC. Microsoft documents these commands in its Powercfg reference .

Run the three checks

Open Command Prompt or Windows Terminal and run these commands soon after the PC wakes unexpectedly:

powercfg /lastwake

powercfg /waketimers

powercfg /devicequery wake_armed

Save the results before changing a setting. They describe different things: the first is Windows’ record of the last wake; the other two show conditions that could allow a future wake.

Read each result for what it can tell you

• `/lastwake` — the last transition. If Windows names a keyboard, mouse, network adapter or other device, write down its exact name. This command reports the most recent sleep transition; it is not a full history, and an unclear result does not prove that nothing woke the PC.
• `/waketimers` — timers active now. A wake timer can bring a PC out of sleep or hibernation when it expires, if timer wake is enabled. A timer listed after the event is a lead to investigate, not proof that it caused that earlier wake. Some scheduled tasks can wake the system while the display stays off ( Microsoft documents this behavior for Task Scheduler ). Microsoft notes that Windows can use timers for scheduled work such as installing updates ( how Windows wakes for tasks ).
• `/devicequery wake_armed` — devices allowed to wake the PC. This is a list of currently enabled wake-capable devices, not a record of which one caused the last wake. Compare it with /lastwake. If the results do not match, test only one plausible device at a time.

Test one device at a time

If /lastwake names a device that also appears in the wake_armed list, temporarily remove only that device’s permission to wake the PC. In Device Manager, open the device’s Properties, select Power Management, and clear Allow this device to wake the computer if that option is available. Put the PC to sleep and repeat the same routine. If the unexpected wake stops, you have a useful lead; turn the setting back on if you still want that device to wake the PC.

Some drivers do not show a Power Management tab. You can also use Powercfg from an administrator Command Prompt. Copy the exact device name from the query output:

powercfg /devicedisablewake "Exact device name"

To restore the permission, find the device’s current name with powercfg /devicequery wake_programmable and run:

powercfg /deviceenableawake "Exact device name"

Disabling wake permission can stop that keyboard or mouse from waking the computer, so use the power button during the test. Do not disable several unfamiliar devices together; that makes the result harder to interpret and can remove controls you rely on.

If a timer appears, identify its task first

If /waketimers names a task or service, check which app owns it before changing anything. For a task you recognise and do not need to run while the PC sleeps, inspect its Conditions in Task Scheduler and change only its wake option. Windows and maintenance tools may schedule work, so do not switch off every wake timer as a first step. On a work or school PC, give the output to IT instead of changing managed tasks.

Check wake on approach

Does the PC wake when someone walks up to it? Some Windows 11 PCs have a presence sensor with a separate wake-on-approach setting. Open Settings > System > Power & battery > Screen and sleep and turn off Automatically wake up my device when I approach for one test, if the option is present. Microsoft says these controls appear only on supported devices and may be limited by the device maker or an organisation’s policy ( Presence Sensing settings ).

When the basic checks are inconclusive

Run powercfg /a to see which sleep states the PC supports. If the output lists Standby (S0 Low Power Idle), the PC supports Modern Standby. That result identifies an available sleep model; it does not name the last wake source.

If a supported Modern Standby laptop also loses battery while the screen is off, open Command Prompt as administrator and run:

powercfg /sleepstudy /output "%USERPROFILE%\sleepstudy.html"

Open the saved HTML report. Microsoft says SleepStudy summarizes Modern Standby sessions and activity, using the last three days by default. It can help investigate screen-off activity or battery drain, but it is not a guaranteed answer for one individual wake event ( Modern Standby diagnostics ).

These checks cover wake events from sleep or hibernation. If the PC was fully shut down and then powered on, that is a different problem; first confirm which power option you used. Our guide to Restart, Shut down and Fast Startup explains how those Windows choices differ.

Change one setting, repeat the same sleep test, and note whether the PC was on battery or plugged in. If Windows cannot identify a source, preserve the command output and ask the PC maker or your organisation’s IT team before changing firmware or broad power settings.

Sources

• Microsoft Learn: Powercfg command-line options .
• Microsoft Learn: Automatically wake for tasks .
• Microsoft Learn: TaskSettings.WakeToRun property .
• Microsoft Support: Managing Presence Sensing settings in Windows 11 .
• Microsoft Learn: Modern standby SleepStudy .