Check this first
The short answer
Immediately after the unwanted wake, inspect powercfg /lastwake. Compare a named device’s wake permission individually; compare an active timer’s scheduled time with the real event. The wake_armed list identifies allowed devices, not proof of what caused this wake.
- Confirm the PC entered sleep, rather than only turning its screen off.
- Record wake time and /lastwake, /waketimers, wake_armed and /a results.
- Change only the device or timer setting supported by that evidence, then compare the same conditions.
Choose your next check
Start with the row that matches your situation. Change one setting at a time so you can tell what helped.
| What you see | What to compare | Go to |
|---|---|---|
| Only the screen turns off and on; sleep is unconfirmed | Compare manual Sleep and separate display/sleep timeouts. | Step 1 |
| /lastwake names a mouse, USB or network device | Match its name against the allowed devices. | Step 3 |
| Waking happens at the same time as an active timer | Compare the timer owner/deadline with the actual wake. | Step 4 |
| /lastwake is unknown or zero and /a shows S0 low-power idle | Review the matching Modern Standby SleepStudy interval. | Step 5 |
| /lastwake is unknown or zero and /a shows S3 | Review same-time system events without disabling every candidate. | Step 5 |
| The PC never enters sleep | Inspect sleep timeout and current power requests. | Step 1 |
Check in this order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1: Distinguish screen-off from sleep and record the time
- Save work and select Start → Power → Sleep. Leave the mouse and keyboard untouched. Record the delay before the display returns and whether the PC uses AC or battery; check for accidental mouse movement.
- Under Settings → System → Power & battery, inspect screen and sleep timeouts separately. The section name varies by version/device. A screen-off timeout alone does not establish a sleep transition.
- If manual Sleep also wakes unexpectedly, collect Step 2 before sleeping again. If the PC will not sleep, inspect powercfg /requests in Command Prompt for app/driver requests preventing idle sleep. That command does not identify a previous wake source.
- Expected result or what you learned
- An unwanted return after manual Sleep provides a time to investigate in Step 2.
- If something is wrong or unclear
- If only screen-off is involved or the PC never sleeps, inspect timeouts/requests first. Starting from shutdown is a different symptom.
- How to undo changes
- Restore any recorded timeout values changed for comparison. These inspection commands do not change power settings.
Step 2: Separate the last wake from active timers and allowed devices
- Immediately after the unwanted wake, open Command Prompt as administrator. Run separately: powercfg /lastwake; powercfg /waketimers; powercfg /devicequery wake_armed; powercfg /a. Record each output and the wake time. On managed PCs, ask the administrator if elevation is unavailable.
- /lastwake reports the last sleep transition’s wake information. /waketimers lists currently active wake schedules. wake_armed lists devices permitted to wake the PC. /a reports supported sleep states. A keyboard in wake_armed does not prove it caused the wake.
- A named last-wake device leads to Step 3; a matching timer time to Step 4. For unknown or zero results, use /a to distinguish S0 from S3 in Step 5. An empty timer list now does not rule out an earlier timer.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| /lastwake reports a specific device | It is reported as the previous wake source. | Compare that device only in Step 3. |
| /waketimers lists an owner and deadline | This is a current schedule, not proof of a past wake. | Use Step 4 when its timing matches the symptom. |
| Only wake_armed lists device names | These are permitted candidates. | Compare them with /lastwake or logs; do not disable all of them. |
| /lastwake is unknown or zero | This output does not identify the cause. | Use /a and Step 5. |
- Expected result or what you learned
- You can choose one evidence-supported setting to compare.
- If something is wrong or unclear
- Empty or unknown output is inconclusive; inspect matching-time records in Step 5.
- How to undo changes
- All four commands inspect state without changing settings.
Step 3: Compare wake permission for the named device only
- Record the /lastwake name. Open Device Manager and the matching mouse, keyboard or network adapter’s Properties → Power Management. Match similar device names carefully.
- Record Allow this device to wake the computer, then clear it only for the identified device and select OK. For a network adapter this can affect Wake-on-LAN; check with its users/administrator first. Before removing keyboard wake permission, confirm that the power button can wake the PC.
- Compare the same sleep method, connected devices and time. If the tab is absent or locked, skip the UI change and consult model-specific power guidance. If the symptom recurs, restore the permission and collect a fresh /lastwake.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| The wake stops under the same conditions | That device’s wake permission may contribute. | Verify intended manual wake still works before keeping the change. |
| Another device is reported or waking continues | The previous candidate does not explain every event. | Restore its permission and repeat Step 2. |
| There is no Power Management tab | This device/driver may not expose the control. | Use Step 5 and manufacturer guidance instead of modifying a different device. |
- Expected result or what you learned
- The unwanted wake stops while an intended wake method remains available.
- If something is wrong or unclear
- If it continues, restore the setting and investigate new evidence. Do not disable the mouse and keyboard together.
- How to undo changes
- Return the same device’s Power Management checkbox to its recorded state.
Step 4: Compare wake timers only when their time matches
- Record the owner and deadline from /waketimers and compare the next real wake time. Identify whether a required update or backup depends on that schedule before interrupting it. A listed schedule alone does not prove the previous wake.
- Press Windows + R, enter control.exe powercfg.cpl and open the selected plan’s Change plan settings → Change advanced power settings → Sleep → Allow wake timers. If present, record the value and temporarily select Disable for only the affected AC or battery state, then Apply.
- Compare across the same scheduled time and power state. If the option is missing, do not force hidden settings to appear; inspect the named app’s schedule or the manufacturer’s power options. Do not stop all update services or scheduled tasks.
- Expected result or what you learned
- No wake at the corresponding time suggests the timer setting contributed; also verify necessary updates/backups still run.
- If something is wrong or unclear
- If waking continues or times do not match, restore the value and collect Step 2 again before Step 5.
- How to undo changes
- Restore each changed AC/battery Allow wake timers value and Apply.
Step 5: For unknown causes, compare sleep type and matching records
- If powercfg /a lists Standby (S0 Low Power Idle), use the Modern Standby path. In an elevated Command Prompt, run powercfg /sleepstudy /output "%USERPROFILE%\sleepstudy.html". Open %USERPROFILE%\sleepstudy.html through File Explorer and inspect the matching interval’s start/end, Screen Off and Sleep states. If /a lists S3, do not assume SleepStudy is applicable.
- Open Event Viewer → Windows Logs → System → Filter Current Log. Select Power-Troubleshooter as the event source and inspect wake records at the actual time, such as Event ID 1. Record an absent wake source as unknown; do not assign a different-time event to this incident.
- On S0, distinguish internal activity without a lit screen from the reported screen turning on. If S3 logs remain inconclusive, compare removable external devices one at a time under the same conditions. Give the manufacturer results, model and recent connection/update changes.
What the result means and what to do next
| Situation | What it tells you | Next action |
|---|---|---|
| S0 SleepStudy covers the relevant interval | It helps distinguish Screen Off, Sleep and active processing. | Match the actual display-on time before selecting a device/app candidate. |
| S3 logs report a wake source | The recorded device or timer can be investigated. | Use Step 3 for a device or Step 4 for a matching timer. |
| Both remain unknown or have no record | These checks have not established the cause. | Send times, power state, model and change history to the manufacturer. |
- Expected result or what you learned
- Matching time and power-state records identify a device or timer worth testing individually.
- If something is wrong or unclear
- If records are absent or inconclusive, collect two occurrence times and ask the manufacturer instead of forcing a diagnosis.
- How to undo changes
- Viewing logs changes no settings. You may delete the generated sleepstudy.html when it is no longer needed.
When to ask for help
Provide PC model, Windows version from winver, AC/battery state, manual-Sleep result, two wake times, /a, /lastwake and /waketimers output, and tested/restored settings. SleepStudy and system logs can reveal device and usage details; review them before sharing publicly. Do not reset every power plan or alter BIOS power settings before narrowing the cause.
FAQ
Does zero or Unknown in /lastwake mean there is no cause?
No. Record the time and use /a to choose Modern Standby SleepStudy or matching system-event investigation.
Should I disable every device in wake_armed?
No. It lists devices allowed to wake, not the actual source of this event. Match other evidence and change one device; keyboard wake and remote Wake-on-LAN may be affected.
Why is /waketimers empty despite waking at a fixed time?
It lists active schedules at the moment you run it. Compare the immediate /lastwake output and same-time logs; use SleepStudy on a supporting S0 PC.
Does a fan running after the screen turns off prove an unwanted wake?
No. Screen-off and sleep timeouts differ, and Modern Standby may involve internal activity with the screen off. First compare Start → Power → Sleep.
Sources
English adaptation preserving the Japanese guide’s diagnostic branches, steps, result tables and restoration conditions. Official sources support the controls; the order of comparisons is editorial guidance, not proof of a particular cause or a claim of testing every PC. Consult the administrator for managed devices.
Microsoft Learn: powercfg query and report commandsMicrosoft: screen and sleep timeoutsMicrosoft: manual SleepMicrosoft Learn: Modern Standby SleepStudyMicrosoft Learn: wake sources versus display-on eventsVAIO: unwanted Windows 11 wake, devices and timers (Japanese)