Fixing a Windows 11 PC That Keeps Waking From Sleep by Itself

You put the machine to sleep, the fans spin down, and twenty minutes later the screen lights up the room again. The symptom is common enough that Microsoft's own community forums carry repeated threads about it, including one user reporting a laptop that woke intermittently both at night and during daytime idle periods ^¹. Another thread describes a desktop waking roughly every fifteen minutes after being put to sleep, with the user tracing the change to a Windows update in May or June ^².

The important thing to understand before touching any setting is that Windows usually knows why it woke. The operating system logs the wake source, and in many cases it will name the exact program, device, or timer responsible. The work below is mostly about extracting that answer rather than guessing at fixes.

One caveat on the evidence: the published reports above describe individual machines, not a controlled study, and no source here establishes how frequently any particular cause appears across Windows 11 systems generally. Treat the ordered steps as a diagnostic sequence, not a ranked list of known probabilities.

Find the wake source first

1. Reproduce the problem, then immediately open the Start menu, search for cmd, right-click Command Prompt, and choose Run as administrator. Type powercfg -lastwake and press Enter. This reports what triggered the most recent wake. In one documented case, the answer was a cloud backup program running its scheduled evening backup, which made the fix a matter of changing that program's schedule rather than altering Windows power settings ^³.

2. If the last-wake report is vague or empty, run powercfg -waketimers in the same elevated prompt. This lists scheduled timers currently armed to wake the system, which is where update orchestrators, backup tools, and media applications typically appear. The same account recommends this as the follow-up when the first command gives nothing useful.

3. If both commands come back unhelpful, go to Event Viewer: search for it from the Start menu, open Windows Logs > System, click Filter Current Log, and narrow the results by event source to find the power-related entries around the timestamp of the unwanted wake. This is slower than the command line but catches cases where the wake came from a device or driver rather than a named process.

4. Note the time of each unwanted wake for a day or two. A regular interval, such as the fifteen-minute pattern in the Microsoft thread, points strongly at a scheduled task or timer. An irregular pattern points more toward a device or network event.

When the wake source is identified

If powercfg names a program, the decision is straightforward: open that program's settings and disable its scheduled wake behavior, reschedule it, or remove it if it is no longer needed. For backup and sync clients, moving the schedule to a time you are normally awake is usually sufficient and costs nothing in functionality.

If the source is a device, the fix lives in Device Manager. Open the properties for the named device, find the Power Management tab, and clear the option that allows the device to wake the computer. Network adapters are frequent candidates, particularly on machines configured for wake-on-LAN, though the sources here do not establish which device classes are most often responsible.

If the wake traces to a scheduled task, open Task Scheduler and review tasks with wake conditions enabled. Disabling the wake condition rather than the task itself preserves whatever maintenance work the task performs.

When the steps do not resolve it

Sometimes the diagnostics return nothing conclusive, or the wakes continue after an obvious culprit has been addressed. At that point the problem is likely to be a configuration issue or an interfering background service rather than a single identifiable trigger.

A Microsoft community answer to the fifteen-minute wake case recommends restoring the default power schemes by running powercfg -restoredefaultschemes from the Run dialog, then restarting. This discards custom power configurations, so note any deliberate changes you have made before running it.

The same answer suggests running the built-in power troubleshooter via msdt.exe /id PowerDiagnostic, again followed by a restart. The troubleshooter is undemanding and worth trying before more invasive steps, though it will not catch every cause.

If neither helps, perform a clean boot: open msconfig, go to the Services tab, tick Hide all Microsoft services, click Disable all, then review the Startup tab and disable third-party startup items. Restart and observe whether the wakes stop. If they do, re-enable services in batches to isolate the offender. The Microsoft answer describes this as a way to determine whether a background program is interfering. Be aware that a clean boot temporarily removes security software and driver utilities, so restore the configuration once testing is complete.

What remains unconfirmed

None of the sources establishes a definitive cause for self-waking in Windows 11 generally, and none provides a success rate for any of these steps. The May or June update mentioned in the fifteen-minute thread is the user's own attribution, not a confirmed Microsoft defect. If you exhaust these steps and the machine still wakes, the remaining suspects are firmware-level settings such as wake-on-LAN in the BIOS or UEFI, and hardware faults, neither of which the supplied sources address.

If your machine instead wakes instantly the moment it enters sleep, or if Wi-Fi fails to reconnect after waking, those are separate failure modes with their own diagnostic paths, covered in our guides to Windows 11 sleep mode waking instantly and Wi-Fi drops after sleep.

Sources

1. ¹ How do I prevent Windows 11 from waking up my laptop screen intermittently? - Microsoft Q&A - Skip to main content learn.microsoft.com
2. ² computer keeps waking up every 15 minutes - Microsoft Q&A - Skip to main content learn.microsoft.com
3. ³ My Windows PC Kept Randomly Waking Up From Sleep Mode. Here's How I Fixed it tech.yahoo.com