✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

You put the PC to sleep, and sometime before morning it is awake again: fans turning, case lights on, the monitor glowing at an empty desktop. Nobody touched it. It happens on random nights, or worse, at exactly the same time every night.

A wake like this is never random and never a hardware ghost. Windows records a reason for every wake, and the machine is simply obeying a standing order that something was given earlier: a timer, a network packet, a device, or a scheduled job. The wrong response is to give up on sleep mode or start unplugging hardware at random. The right response is a short investigation. This guide works like a case file: read the evidence first, then work through the five usual suspects in order and take away the one permission that is being abused.

As an Amazon Associate, we earn from qualifying purchases.

Quick Answer

A PC that wakes from sleep by itself is obeying an order, not failing. Windows logs every wake source, so run powercfg -lastwake, match the named culprit to a wake timer, the network adapter, a peripheral, or a scheduled task, then revoke that one wake permission and test sleep again.

Start With the Evidence: The Wake Log Names the Culprit

Do not change a single setting until you know who woke the machine. Run this check right after an unwanted wake, before the PC sleeps again, because Windows only remembers the most recent one.

Open a terminal as administrator and run powercfg -lastwake. The output names the wake source type: Device, Wake Timer, Power Button, or Unknown, and for devices it usually names the hardware itself. Cross-check it in Event Viewer under Windows Logs, then System: filter by the source Power-Troubleshooter and open the newest entry. It records the exact sleep time, wake time, and wake source in plain language.

Two more commands build the suspect list. powercfg -waketimers shows every timer currently armed to wake the machine, and powercfg -devicequery wake_armed lists every device that holds permission to wake it. With those three results you can route yourself: a named network adapter goes to Suspect Two, a named mouse or keyboard to Suspect Three, a timer to Suspects One and Four. If the source comes back Unknown, work the suspects in order anyway; the wake_armed list is short, and elimination is fast.

Suspect One: Wake Timers

A wake timer is a formal request: software asks Windows to wake the PC at a set time to do work. It is the prime suspect when the machine wakes at the same time every night.

Disarm the whole category in one move. Open Power Options, choose Change plan settings for your active plan, then Change advanced power settings. Expand Sleep, then Allow wake timers, and set it to Disable. On a desktop there is rarely a good reason to leave it on.

Then check the most common timer owner: Automatic Maintenance. In Control Panel, open Security and Maintenance, expand Maintenance, and choose Change maintenance settings. If the option to allow scheduled maintenance to wake the computer is ticked, the PC will rise in the small hours to run it. Unticking it does not stop maintenance; it just runs the next time the machine is awake anyway.

Suspect Two: The Network Adapter and Wake-on-LAN

A network adapter with wake permission listens while the rest of the PC sleeps, and it can be told to wake the machine by a magic packet or by ordinary pattern-matched traffic. Pattern match is the troublemaker: file shares, media servers, chatty smart TVs, and network scans can all trip it.

Open Device Manager, expand Network adapters, open your adapter, and go to the Power Management tab. The strict fix is to untick Allow this device to wake the computer. The balanced fix, if you actually use remote wake for game streaming, is to leave it ticked but also tick Only allow a magic packet to wake the computer, so normal network noise is ignored. The Advanced tab holds the matching Wake on Magic Packet and Wake on Pattern Match switches on many drivers.

Remember the rest of the chain. An unmanaged switch such as the TP-Link TL-SG105 forwards broadcast traffic to every port, so a magic packet sent anywhere on the network still lands on your PC. A router such as the TP-Link Archer AX21 keeps its own device list and schedules, and network storage boxes and phone apps are frequent silent senders of wake requests. If lastwake names the adapter but you never configured Wake-on-LAN, something on your network asked for the wake, and the sender is findable.

Suspect Three: Mice, Keyboards, and Wireless Dongles

On most gaming PCs the wake_armed list is short: a mouse, a keyboard, sometimes a controller. Any one of them can end sleep with a single input event, and wireless gear is the worst offender because the receiver stays armed and listening around the clock. A desk bump, a pet brushing past, or a mouse shifting inside a drawer is enough movement to count as a wake request.

A wireless mouse like the Logitech G305 LIGHTSPEED shows why the fix can be physical as well as digital: it has a power switch on its underside, and switching it off at night removes it from the case entirely. Wired gear is not innocent either. A Logitech G502 HERO can register a click if its cable is tugged, and a keyboard such as the Keychron V1 wakes the machine on any key press if it holds permission, which makes a cat crossing the desk a classic 3 a.m. culprit.

The controlled fix is Device Manager again. Open each input device, go to Power Management, and untick Allow this device to wake the computer. Leave wake permission on exactly one device you trust, usually the keyboard, and wake the PC with that or with the power button. Check USB hubs and game controllers in the wake_armed list too; they hold the same permission and are easy to forget.

Suspect Four: Scheduled Tasks and Update Jobs

Some wakes are appointments. Any scheduled task can carry a condition that wakes the computer to run it, and the owner is often a maintenance or update job rather than anything you installed yourself. Update and reboot tasks are repeat offenders, and backup tools and media library scans are close behind.

When powercfg -waketimers names a task, open Task Scheduler, find that task, open its Properties, and clear Wake the computer to run this task on the Conditions tab. For update-related tasks, prefer changing the schedule instead of editing the task itself, because Windows may recreate edited tasks. Moving the maintenance window to a time when the PC is normally awake solves the wake without breaking the update cycle.

Suspect Five: Sleep States and Firmware Switches

If no suspect confesses, the trail leads below Windows. Run powercfg -a to see which sleep states the machine supports. A PC using classic S3 sleep wakes only through the routes above. A machine on Modern Standby stays partly network-connected by design and surfaces far more often, which is mostly a laptop trait but appears on some desktops too.

The firmware setup holds the master switches. Look for Wake on LAN from the deepest sleep state, Power On by PCI-E or network, and Power On by Mouse or Keyboard, and disable the ones you do not use. Enabling the ErP ready option, where offered, cuts standby power to the network and USB circuits and quietly kills most firmware-level wakes at once. Change one firmware setting at a time and sleep-test between changes, so you know which switch mattered.

How to Choose

Choose your end state first, then set permissions to match. If you never wake this PC remotely, the clean configuration is total: no wake timers, no device wake permissions except the power button, and firmware wake options off. If you stream from the PC with a remote tool, keep exactly one deliberate path, magic-packet-only on the network adapter, and close every other door.

Gear choices matter at replacement time. Prefer a wireless mouse with a physical power switch if it lives on a busy desk. Decide in advance whether the keyboard keeps wake rights or the power button does the job. And treat the network as part of the PC: an unmanaged switch passes every broadcast through, so the adapter settings on the PC itself are where control has to live.

Who Should Skip This Fix

Skip this guide if your PC will not wake from sleep at all. That is the opposite fault, with its own diagnosis, and it has a separate guide on this site. Skip it too if the machine turns itself on after a full shutdown rather than resuming from sleep; that trail runs through firmware power settings and fast startup, not wake permissions. A handheld that refuses to wake is a different device class with its own guide. And if your PC never falls asleep in the first place, that is an insomnia problem, not a waking problem, and it starts with a different powercfg report.

Frequently Asked Questions

Why does my PC wake up at the same time every night?

A fixed wake time almost always means a scheduled order rather than a device. Automatic Maintenance and update tasks run in the small hours and can hold wake timers. Run powercfg -waketimers to see the armed timer and its owner, then move the schedule or untick the option that lets maintenance wake the machine.

Can a mouse really wake a gaming PC from sleep?

Yes. Any movement or click from a device that holds wake permission ends sleep, and a wireless receiver listens all night. A bumped desk or a pet is enough. Either revoke the mouse wake permission in Device Manager, or use the power switch on the mouse itself if it has one.

Should I disable Wake-on-LAN completely?

Only if nothing on your network ever needs to wake the PC. If you use remote play or remote desktop, keep the feature but restrict it: set the adapter to respond to magic packets only, so ordinary traffic and network scans can no longer trip it.

Why does powercfg -lastwake say the wake source is unknown?

Some drivers do not report their wake events, so Windows records the wake without a name. Open the Power-Troubleshooter entry in Event Viewer for the timestamp, then eliminate suspects directly: clear the armed device list down to one device per night until the wakes stop.

Final Verdict

An unwanted wake is a permission being exercised, not a mystery. The wake log names the culprit in most cases, and every route in runs through a short list of timers, one network adapter, a handful of input devices, and a few scheduled jobs. Revoke the one permission that is being abused, keep only the wake paths you chose on purpose, and the PC will stay asleep until you decide otherwise.

Product and ASIN Reference

Product ASIN
Logitech G305 LIGHTSPEED Wireless Gaming Mouse B07CMS5Q6P
Logitech G502 HERO Wired Gaming Mouse B07GBZ4Q68
Keychron V1 Wired Mechanical Keyboard B09NLWG6X1
TP-Link TL-SG105 5-Port Gigabit Ethernet Switch B00A128S24
TP-Link Archer AX21 Wi-Fi 6 Router B08H8ZLKKK

Explore Our Guides & Free Tools