Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| PC wakes at the same time | Check scheduled tasks, maintenance and wake timers |
| PC wakes when mouse moves | Disable wake for that device if not needed |
| PC wakes with network activity | Review Wake-on-LAN and network adapter settings |
| Wake source is unknown | Use powercfg reports and firmware event information |
Diagnose unexpected wake sources with evidence first
Record the time of each unexpected wake and whether the PC was asleep, hibernating, or shut down. Use the wake history to identify whether a device, timer, network event, or scheduled task triggered it.
Determine whether wakes happen only with network connected, one USB device attached, or at a predictable time. That pattern is more useful than disabling every wake source globally.
Complete these focused checks: run powercfg /lastwake after the event; list active wake timers; identify devices allowed to wake the computer; note whether wake happens on AC, battery or network activity. 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.
Install supported chipset, network, USB, and firmware updates when the wake source points to those components. Avoid blanket scripts that disable all wake functionality.
Save work before changing firmware wake options or device power settings. Keep any remote-wake features documented so they can be restored if needed.
Identify the last wake source
Run powercfg /lastwake and powercfg /waketimers immediately after an unexpected wake. Correlate it with Task Scheduler.
Record the time of each unexpected wake and whether the PC was asleep, hibernating, or shut down. Use the wake history to identify whether a device, timer, network event, or scheduled task triggered it.
Determine whether wakes happen only with network connected, one USB device attached, or at a predictable time. That pattern is more useful than disabling every wake source globally.
Complete these focused checks: run powercfg /lastwake after the event; list active wake timers; identify devices allowed to wake the computer; note whether wake happens on AC, battery or network activity. 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.
Install supported chipset, network, USB, and firmware updates when the wake source points to those components. Avoid blanket scripts that disable all wake functionality.
Save work before changing firmware wake options or device power settings. Keep any remote-wake features documented so they can be restored if needed.
Identify the last wake source
Run powercfg /lastwake and powercfg /waketimers immediately after an unexpected wake. Correlate it with Task Scheduler.
Note the approximate wake time before changing anything. After the next unexpected wake, compare it with recent wake information and scheduled activity so you can test the actual trigger rather than disabling every wake source.
1Verification checkpoint
- Repeat the original action once.
- After changing one wake source, put the PC to sleep under the same conditions and confirm it stays asleep through the previous wake window.
- Restore diagnostic changes that did not help.
Control only the responsible device
Use Device Manager Power Management for the named mouse, keyboard or network adapter. Keep at least one intentional wake method.
Use Device Manager Power Management for the named mouse, keyboard or network adapter. Keep at least one intentional wake method.
When disabling device wake permission, start with one likely device such as a mouse, network adapter, or USB controller. Keep the keyboard able to wake the PC if you depend on it.
2Verification checkpoint
- Repeat the original action once.
- After changing one wake source, put the PC to sleep under the same conditions and confirm it stays asleep through the previous wake window.
- Restore diagnostic changes that did not help.
Review firmware and maintenance
Check BIOS wake-on-LAN, USB wake and real-time-clock alarms plus Windows maintenance settings. Change one trigger at a time.
Check BIOS wake-on-LAN, USB wake and real-time-clock alarms plus Windows maintenance settings. Change one trigger at a time.
If you disable wake timers for testing, remember that maintenance, updates, backups, or alarms may legitimately use them. Restore required timers once the source is identified.
3Verification checkpoint
- Repeat the original action once.
- After changing one wake source, put the PC to sleep under the same conditions and confirm it stays asleep through the previous wake window.
- Restore diagnostic changes that did not help.
Interpret the result before escalating
A wake event that consistently names the same device or timer gives you a narrow target. Update its driver or change only that device's wake permission rather than globally disabling sleep features.
If the PC wakes only when connected to Ethernet or a dock, Wake-on-LAN or the dock's network controller becomes more likely. Test once with that connection removed.
If no useful wake source is recorded, compare scheduled tasks, maintenance windows, firmware wake settings, and USB devices. Absence of a recorded Windows source can mean the wake was initiated below the normal Windows event layer.
Verify the fix and choose the safe escalation
Put the PC to sleep under the same conditions that previously caused the random wake and leave it through the usual problem window. A quick five-minute test is not enough if the wake normally happens hours later.
After identifying the trigger, restore unrelated wake permissions and timers. The goal is a normal sleep system with one bad source corrected, not a PC that can no longer wake for legitimate tasks.
If the machine wakes even with network, USB wake, timers, and scheduled tasks ruled out, review firmware wake settings and vendor diagnostics before resetting Windows.
Technical order checked against current Microsoft guidance. Exact controls vary by Windows build, hardware, edition and organization policy.
Frequently asked questions
How can I see what woke my PC?
Run powercfg /lastwake soon after the event and inspect the reported device or timer.
Why does Windows wake at the same time nightly?
A scheduled task, maintenance window, update or firmware alarm may be configured to wake it.
Can the network wake a sleeping PC?
Yes, when Wake-on-LAN or pattern matching is enabled in the adapter and firmware.