What's Waking Your PC? Find and Stop Automatic Wake-Ups
—
If your Windows 11 or 10 PC keeps waking itself from sleep, the fastest way to catch the culprit is to open an elevated Command Prompt and run powercfg -waketimers. If it lists a task by name, that task has permission to wake your PC and you can switch it off in Task Scheduler in under a minute. If it comes back empty, the cause is usually a device, not a timer, and Device Manager is where you go next. Here's the part almost nobody expects: Windows deliberately wakes idle PCs on purpose, by design, to run maintenance and download updates while you're not looking, and that "intelligent machine deciding to turn itself on" feeling people describe is, more often than not, exactly one specific, nameable, switchable-off setting.
Why Windows Wakes Itself Up At All
Jake, who runs a small phone and computer repair counter, brought this one in himself. A regular customer's laptop had been quietly waking up at 3 a.m. every night for weeks, fan spinning, screen glowing in an empty house, and the customer was one visit away from being talked into a $150 "deep security tune-up" Jake's counter had bundled together mostly to cover cases like this — reformat, reinstall, hope it goes away. Jake almost rang it up. He checked one command first instead.
There are really only three sources for an unwanted wake, and knowing which bucket you're in tells you exactly where to look:
1. A scheduled task with wake permission
Windows' Task Scheduler lets any task, built-in or third-party, request the right to wake a sleeping PC so it can run on time instead of waiting for you to be at the keyboard. Windows Update's maintenance tasks are the most common offender, but backup software, antivirus scan schedules, and even printer or webcam utilities sometimes request the same permission during installation.
2. A device allowed to wake the computer
In Device Manager, individual hardware, a mouse, a keyboard receiver, a network adapter, can be granted permission to bring the PC out of sleep on activity. This is meant for legitimate cases like waking a desktop by jiggling the mouse, but a cheap wireless dongle or a flaky network card can misread noise as a wake signal and fire at random.
3. Windows' own maintenance and update wake timers
Since Windows 8, the operating system has reserved the right to wake an idle, plugged-in PC briefly to run Automatic Maintenance, disk cleanup, and Windows Update checks, then put it straight back to sleep. This is intentional and, on a desktop that's plugged in overnight, mostly harmless. It becomes a problem mainly on laptops running on battery, or when the PC doesn't reliably go back to sleep afterward.
⚠️ What this actually breaks
A PC that wakes and never goes back to sleep isn't usually "waking up for no reason" at all — it's waking up correctly for a real task, then failing to re-sleep because something else (a stuck driver, an open network connection, a peripheral still reporting activity) is silently keeping it awake afterward. If your PC wakes once and then stays on, treat that as a separate, second problem from what fired the wake in the first place.
Every Way People Try to Diagnose This, Ranked
Before the exact steps, here's every route people actually take, including the ones worth skipping, so you can pick the right one for your situation instead of working through all six.
| Method | Works on Home? | Use it when |
|---|---|---|
powercfg -waketimers |
Yes | First thing to try, every time — free, instant, no reboot |
powercfg /lastwakeuptime |
Yes | The wake already happened and the timer's gone |
| Event Viewer (Power-Troubleshooter) | Yes | You need several days of history, not just the last wake |
| Device Manager > Power Management | Yes | powercfg came back empty — a device, not a task, is the cause |
| Reinstall / reset Windows | Yes | Almost never the right first move — see below |
| Third-party sleep-tracking app | Yes | You want a dashboard; adds nothing powercfg can't already tell you |
Ethan doesn't hide his opinion of that fifth row: "A reinstall to fix a wake timer is like repainting a car because one warning light is on. I've watched people burn an entire Saturday reinstalling Windows, restoring their apps, redoing their settings, and the PC still wakes up at 3 a.m. — because the actual cause was never the operating system, it was one checkbox in Task Scheduler that a fresh install doesn't even touch."
Step 1: Find Out Exactly What's Waking It
These steps are identical on Windows 11 and Windows 10 — the command line hasn't changed. Only the way you open a command prompt differs, so both are covered below.
On Windows 11
Right-click the Start button, or press Win + X, and choose Terminal (Admin). Windows 11's default terminal is a wrapper that can host either Command Prompt or PowerShell — either works fine for the commands below, since powercfg is a standalone Windows tool and doesn't care which shell is calling it.
On Windows 10
Click Start, type cmd, then right-click Command Prompt and choose Run as administrator. You need the elevated (administrator) prompt — running these commands as a standard user will either fail silently or show an incomplete result.
Once you have an admin prompt open on either version, run:
| Command | What it tells you |
|---|---|
powercfg -waketimers |
Any wake timer currently armed and due to fire, by name |
powercfg /lastwakeuptime |
What actually woke the PC the last time it happened |
powercfg /devicequery wake_armed |
Every device currently allowed to wake the PC |
powercfg /sleepstudy |
A full HTML report of recent sleep sessions (saved to the folder shown after it runs) |
If powercfg -waketimers replies "There are no active wake timers in the System," your PC isn't currently armed to wake itself, which means either the wake already happened and the timer cleared, or the real cause is a device, not a timer. If instead it shows a line like [Timer set by [SERVICE] Windows Update.], or names svchost.exe with a task like UpdateOrchestrator, you have your answer, and you can go straight to the Task Scheduler fix below.
Reading the result with Event Viewer, for the harder cases
If powercfg alone doesn't give you a clear name, or the wake happens on an unpredictable schedule you can't catch in the act, open Event Viewer (search for it in Start), expand Windows Logs > System, and filter by source Power-Troubleshooter. Event ID 1 is logged every time the PC wakes and includes a "Wake Source" field naming the exact device or timer, going back for as many days as your system log retains.
🙋♂️ Jake's Reality Check
"Do I need to buy some kind of monitoring software to catch this? I've got a laptop I can't watch all night."
No. Everything above ships with Windows already. Run powercfg /lastwakeuptime the next morning, and the answer is sitting there waiting for you — no software, no subscription, no watching the screen at 3 a.m.
Step 2: Turn Off the Wake Permission You Found
If a Task Scheduler task was the source, this is where you go turn it off, and it's the same three-click process on both versions of Windows.
Disabling a task's wake permission
Open Task Scheduler (search for it in Start), and use the library tree on the left to find the task powercfg named — Windows Update's own tasks live under Task Scheduler Library > Microsoft > Windows > UpdateOrchestrator; Automatic Maintenance lives under Microsoft > Windows > TaskScheduler. Right-click the task, choose Properties, open the Conditions tab, and clear the checkbox labeled Wake the computer to run this task. Click OK.
✅ Why this is the one to use
Unchecking the box instead of disabling the whole task is the right call almost every time. The task itself keeps running normally whenever the PC is already awake — you're only removing its permission to wake a sleeping PC specifically for that purpose. That's a much smaller, safer change than disabling Windows Update's maintenance tasks outright, which is a bad idea for anyone who isn't deliberately staging updates by hand.
Ethan is blunt about the tasks people find scary in that library: "Nine times out of ten it's UpdateOrchestrator or Automatic Maintenance, and neither one is malware, spyware, or anything sinister — it's Windows trying to be considerate by doing its housekeeping while you're not using the PC. The box you want isn't 'disable the task,' it's just the wake checkbox. Leave the rest alone."
If No Timer Showed Up: Check the Devices, Not the Tasks
An empty powercfg -waketimers result, combined with an Event Viewer entry naming a piece of hardware instead of a service, means a device has been given permission to wake the PC and something about it, noise, a stuck button state, a driver quirk, is triggering that permission when it shouldn't.
Revoking a device's wake permission
Open Device Manager (right-click Start > Device Manager on Windows 11, or search for it directly on Windows 10). Expand the relevant category, usually Mice and other pointing devices, Keyboards, or Network adapters. Right-click the specific device, choose Properties, open the Power Management tab, and clear Allow this device to wake the computer. Not every device shows this tab — only ones capable of sending a wake signal will have it.
On Windows 11 specifically, the right-click context menu is condensed by default, so if you don't see Properties in the shortened list, click Show more options first (or press Shift + F10) to reveal it. This one trips up almost everyone moving from Windows 10, where the full menu was always visible.
Wake-on-LAN, specifically
Network adapters get their own extra pair of settings on the same Power Management tab, or nearby under an Advanced tab: Wake on Magic Packet and Wake on Pattern Match. These let a specially formatted network packet wake the PC remotely, useful for remote administration, unwanted on a home PC that only ever gets woken by accident when other devices on the network chatter. Disable both if you're not intentionally using remote wake, and check the equivalent setting in your motherboard or laptop's firmware (usually under a Power or Advanced menu, labeled something like "Wake on LAN" or "Power On by PCI-E") — both the firmware and the Windows driver setting need to agree, or the wake will keep happening from whichever one is still enabled.
Laptops Are Different: Modern Standby vs. Old-Style Sleep
Most laptops sold in recent years use what Microsoft calls Modern Standby, or S0 low-power idle, instead of the traditional S3 sleep older desktops use. The difference matters here: Modern Standby keeps parts of the system lightly powered on purpose, so the PC can quietly sync email, receive VoIP calls, and run its own background wake-and-resleep cycles without you noticing — a laptop lid that's closed but warm to the touch, or a fan that spins up occasionally in a bag, is often Modern Standby doing exactly what it's designed to do, not a malfunction.
You can check which type your PC uses by running powercfg /a in an admin prompt — it will list "Standby (S0 Low Power Idle)" if you have Modern Standby, or "Standby (S3)" if you have the older style. Modern Standby PCs are more prone to visible screen flashes or fan spin-up during a background wake, but the diagnostic commands above work identically on both.
🕐 What changed since we first wrote this
- Then: we covered this on Windows 10, working from the single
powercfg -waketimerscommand and the classic Task Scheduler checkbox. - Now: the same command still works exactly as it did — but many more PCs today are laptops using Modern Standby rather than the older S3 sleep this originally assumed, which changes what counts as a "normal" background stir.
- What that means for you: run
powercfg /afirst if you're on a laptop, so you know which kind of sleep you're actually troubleshooting before you start hunting for a culprit.
A Note for Anyone Still On Windows 10
Windows 10 reached the end of free security updates on October 14, 2025. Everything on this page still works exactly the same on Windows 10 — the commands, Task Scheduler, Device Manager, none of that changed — but if your PC isn't enrolled in Extended Security Updates, it's no longer receiving security patches, which is worth knowing regardless of whether your issue is a sleep timer or something more serious. Enrollment in Consumer ESU is still open as of this writing: it's free if you sync your settings through Windows Backup, costs 1,000 Microsoft Rewards points, or a one-time roughly $30, and covers you into October 2027.
Jake sees this constantly at the counter: someone brings in a Windows 10 machine convinced it's "acting possessed," when really it's a perfectly healthy PC just past its support date, still running fine, still fixable with the same tools covered here.
Edge Cases Worth Knowing About
Desktop towers, tucked out of sight
Desktops are the most common place for a wake to go unnoticed for weeks, since there's no lid to prompt you to check, and no battery drain to make it feel urgent. If you only realized this was happening because a monitor showed a login screen glowing in a dark room, that's worth checking on a desktop too — run powercfg /devicequery wake_armed to see if the network adapter is the one holding the permission.
Remote Desktop and VMs
If you connect to this PC over Remote Desktop, or run it as a virtual machine host, be careful about disabling network-adapter wake permission wholesale — it's frequently the exact mechanism you rely on to bring the machine back up remotely. In that situation, keep Wake on Magic Packet enabled and instead confirm the wake events line up with your own remote sessions before assuming something's wrong.
Multi-monitor setups
A second monitor that "wakes up" on its own is sometimes just the display itself, not the PC — many monitors periodically poll their video input to check for a signal, and can appear to flash awake even while the PC genuinely stays asleep. Check whether the PC's own indicator LED or fan activity matches the monitor's behavior before troubleshooting Windows at all.
For the Person Who Wants This Checked Automatically
If this has happened more than once and you'd rather have a record waiting for you than remember to check by hand, Task Scheduler can run the diagnostic for you and log the result to a file. Create a new task (Task Scheduler > Action > Create Task), set a daily trigger for a time after you'd normally be asleep, and set the action to run:
cmd.exe /c powercfg /lastwakeuptime >> C:\wake-log.txt
Each morning, wake-log.txt has a new line showing what woke the PC overnight, without you needing to remember to check. It's a small setup cost for anyone whose PC wakes intermittently rather than on a predictable schedule, since a one-off check can easily miss the pattern that a week of logged entries makes obvious.
Do You Need Third-Party Software?
No. Every tool covered on this page, powercfg, Task Scheduler, Device Manager, Event Viewer, is built into both Windows 11 and Windows 10 at no cost. Third-party "sleep manager" utilities mostly wrap the same underlying Windows APIs in a nicer-looking dashboard; they're worth considering only if you specifically want a visual history of sleep sessions without touching a command prompt, not because they can see anything Windows itself can't.
One Thing Worth Checking Before You Move On
Before you write this off as routine maintenance, it's worth glancing at what Event Viewer named as the wake source at least once. The overwhelming majority of cases really are Windows Update, Automatic Maintenance, or an overly sensitive mouse receiver — but a PC that's genuinely being woken by unexpected network traffic, rather than a named scheduled task, is worth a closer look with your antivirus, particularly if it's a work laptop or one that handles anything sensitive. That's the rare case; for nearly everyone reading this, the fix ends at the Task Scheduler checkbox.
Frequently Asked Questions
Why does my Windows 11 or 10 PC wake up from sleep by itself?
Almost always one of three things: a scheduled task with wake permission, a device allowed to wake the PC in Device Manager, or a maintenance wake timer set by Windows itself. Run powercfg -waketimers to find out which.
What does powercfg -waketimers actually show me?
Any wake timer currently armed, including the name of whatever set it and when it's due to fire. An empty result points you toward a device instead of a timer.
How do I find out what actually woke my PC last time?
powercfg /lastwakeuptime for a quick answer, powercfg /sleepstudy for a full report, or Event Viewer's System log filtered to Power-Troubleshooter for a running history.
Is it safe to turn off "Wake the computer to run this task"?
Yes, for nearly every task. The task keeps running normally whenever the PC is already awake; you're only stopping it from waking a sleeping PC.
What is UpdateOrchestrator and why does it wake my computer?
It's the Windows Update task family that schedules downloads, installs, and maintenance, and it's allowed to set wake timers by design so updates can finish overnight.
Why does my mouse or keyboard wake my PC when I haven't touched it?
Wireless receivers and some peripherals can report electrical noise or state changes that Windows interprets as a wake signal. Revoke wake permission for that device in Device Manager's Power Management tab.
How is Modern Standby different from old-style Sleep?
Modern Standby (S0) keeps parts of the system lightly powered for background activity and self-manages wake cycles; older S3 sleep fully suspends the CPU. Run powercfg /a to see which your PC uses.
Does Fast Startup cause unexpected wakes?
Not directly — it affects shutdown, not sleep — but it's worth ruling out if the "wake" seems to follow what you thought was a full shutdown rather than sleep.
Can Wake-on-LAN wake my PC even when it's off?
Yes, on some hardware, if Wake on Magic Packet is enabled both in Windows and in firmware. Disable it in both places if you don't use remote wake intentionally.
My PC wakes up right after I close the lid. What's going on?
Usually a Lid Close Action combined with a device or timer that fires soon after. Check powercfg -waketimers immediately after it happens, since the window is short.
Is a wake timer bad for my laptop battery?
One predictable maintenance wake is a small, minor drain. Repeated, unpredictable wakes from a misbehaving device are the real cost, since the PC may not fully re-sleep between them.
Do I need third-party software to stop this?
No — powercfg, Task Scheduler, and Device Manager, all built into Windows, cover everything needed to diagnose and fix it.
Why didn't disabling Wake-on-LAN in my BIOS fix it?
Because the Windows driver setting and the firmware setting are separate and both need to be turned off — leaving one enabled keeps the wake armed from that side.
Can I automate this check so I don't have to remember to run it?
Yes — a daily Task Scheduler task can run powercfg /lastwakeuptime and log the result to a text file, so you have a running record without checking by hand each morning.
Revision note. Originally published December 4, 2016. Rewritten August 20, 2026 for Windows 11 and Windows 10. The core diagnostic, powercfg -waketimers, hasn't changed in a decade; what has changed is the hardware underneath it, with Modern Standby now common on laptops and Windows 11's condensed right-click menu hiding the Device Manager properties this guide relies on. Jake never rang up that $150 tune-up — the customer's laptop turned out to be Automatic Maintenance, unchecked in under a minute, and he's been a regular ever since. If you're reading this at 2 a.m. wondering why your PC just lit up the room, take a breath — it's very rarely anything sinister, and you're two commands away from knowing exactly what it was.