Windows wakes from sleep by itself

• Estimated time: 5 min
• Easy
• Low risk

Collect evidence before disabling features.

1. Save work. After an unexpected wake, open Terminal or Command Prompt and inspect the last transition. Record time, power source, and connected peripherals; do not provoke repeated cycles if the computer overheats or loses work.

2. Command PromptCopy

   powercfg /lastwake

   Displays the last-wake information Windows exposes; it does not change settings.

3. If it identifies a device, keep its name for the device branch. If it offers no cause, inspect timers and permissions: do not blame the first installed adapter.

• Estimated time: 5 min
• Easy
• Low risk
• Administrator required

These queries describe different evidence.

1. Open Terminal as an authorized administrator to inspect timers; if you lack permission on a work computer, give IT the time. Run the queries without adding modification commands.

2. Command PromptCopy

   powercfg /waketimers

   Lists active wake timers. Compare owner and expiry with the observed time; a current timer does not prove a past event.

3. Command PromptCopy

   powercfg /devicequery wake_armed

   Lists devices currently configured to wake the system. Presence does not prove they caused the wake.

4. If a timer matches, follow its responsible task; if a device matches lastwake, follow that device. Without a useful match, compare context before changing permissions.

• Estimated time: 5 min
• Easy
• Low risk
• Administrator required

The test must be reversible and retain another way to wake the computer.

1. If the identified device exposes Power Management in Device Manager properties, record Allow this device to wake the computer. Only if you do not need that function and are authorized, clear that permission; do not disable the whole device. If the option is absent, consult the manufacturer without editing the Registry.

2. For a network adapter, first confirm whether remote wake is needed. Test one normal cycle after saving. If the pattern disappears, the permission is relevant; if unchanged, restore the setting and retain the new lastwake rather than disabling every device.

• Estimated time: 5 min
• Easy
• Low risk
• Administrator required

A maintenance task may be intentional.

1. Use timer name and time to identify the application or task. If you created and manage the task, consult its documented wake setting and record the value before adjusting only that condition. If it belongs to the system or organization, ask its owner to review it.

2. Observe whether waking stops at the expected time and whether the task still performs its function. If unchanged, restore the setting. Do not disable Windows Update, maintenance, or all timers as an experiment.

• Estimated time: 5 min
• Easy
• Low risk

A controlled difference provides more than repeated broad tweaks.

1. If it happens only with a dock or peripheral, save work and eject drives before removing it. Compare one normal sleep without that accessory while keeping other conditions unchanged. If the pattern changes, report that combination to the manufacturer; it does not alone prove a broken accessory.

2. If no useful cause emerges, keep outputs, times, and lid/dock/power relationships for Windows or OEM support. Do not change sleep model, firmware, or Registry to compensate for missing evidence.