Your PC wakes itself at 3 a.m. Find out who's doing it

Quick answer: Open Command Prompt as administrator and run powercfg /lastwake. It names whatever woke the machine. Then shut off that device's wake permission, turn off wake timers, and move Windows maintenance to a time you're awake. This is all Windows. It takes about fifteen minutes.

Start by catching the culprit

Guessing wastes an evening. Windows keeps a record, so ask it.

Right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin), and run these one at a time:

• powercfg /lastwake shows what pulled the PC out of sleep most recently.
• powercfg /devicequery wake_armed lists every piece of hardware allowed to wake it.
• powercfg /waketimers lists scheduled wake-ups, if any.
• powercfg /requests shows what's currently telling Windows not to sleep at all.

Write down what comes back. Most of the time it's one of four things: the mouse, the network adapter, a wake timer, or Windows maintenance. Work through them in that order.

The mouse is the usual suspect

A wireless mouse on a desk that shares a wall with a washing machine will wake a PC. So will a cat. So will you, brushing the desk with your knee on the way past at midnight.

Open Device Manager, expand Mice and other pointing devices, double-click your mouse, open the Power Management tab, and uncheck "Allow this device to wake the computer."

Leave the keyboard alone if you like waking the machine with a key. A keyboard doesn't get bumped the way a mouse does. If you'd rather it only wake on the power button, uncheck it there too.

The trade-off is small. You press a key or a button instead of nudging the mouse. That's the whole cost.

The network adapter wakes it for other people

Expand Network adapters in Device Manager, open your Ethernet or Wi-Fi adapter, and go to the same Power Management tab. You'll see "Allow this device to wake the computer" and, under it, "Only allow a magic packet to wake the computer."

Tick the magic packet box. That means the PC only wakes on a specific, deliberate signal, not on any stray traffic on your network. If you never wake the machine remotely, uncheck the wake permission entirely.

One exception. If you stream games from this PC to a laptop or a TV and wake it from another room, you need that magic packet setting. Leave it on and accept it.

Kill the wake timers

Programs can schedule the PC to wake at a set time. Windows allows it by default.

Go to Control Panel, then Power Options, then Change plan settings and Change advanced power settings. Open Sleep, then Allow wake timers, and set it to Disable. On some Windows 11 builds you'll also see "Important wake timers only." That's a fair middle setting, but start with Disable and see if the problem stops.

Windows maintenance is the quiet one

If powercfg /lastwake mentions a scheduled task, a timer, or something with "Update" or "Maintenance" in the name, this is it. Windows runs housekeeping overnight and is allowed to wake the machine to do it.

Two places to check:

1. Control Panel, Security and Maintenance, expand Maintenance, click Change maintenance settings, and uncheck "Allow scheduled maintenance to wake up my computer at the scheduled time."
2. Open Task Scheduler and go to Task Scheduler Library, then Microsoft, Windows, UpdateOrchestrator. Find the task named Reboot, open its properties, go to Conditions, and uncheck "Wake the computer to run this task."

Windows will sometimes switch that second one back after a big update. If the 3 a.m. wake-ups return a month later, look there first.

Don't respond by turning updates off. Security patches matter, and a gaming PC with a stack of saved logins on it's worth protecting. Set your active hours in Windows Update to cover when you play, and run updates yourself before bed. Let the machine patch while you're watching it, then let it sleep.

When it won't sleep at all

Different problem, same tool. Run powercfg /requests and read the output. Under SYSTEM or DISPLAY, Windows names the program holding the machine awake.

Common offenders: a game launcher in the middle of a download, a media player left paused, a remote desktop tool, or the control software that runs your RGB lighting. Close the program named, wait a minute, and test sleep again.

If a launcher is the one, finish the download before bed or pause it. A 90 GB patch will keep a machine awake until it's done, and it should.

Sleep, or shut down?

Here's the rule of thumb. Stepping away for an hour or two, let it sleep. Leaving for the night or a workday, shut it down. A sleeping PC still draws a little power, still feeds a fan header or two on some boards, and still has a dozen ways to wake up that you haven't thought of.

On cost, run your own math instead of trusting a round number. Watts divided by 1,000, times hours, times your rate per kilowatt-hour. Your utility bill lists the rate. For most people the electricity is small. The real costs are fan wear, a hot room, and the lost sleep when the thing hums or glows through the night.

If the one awake at 2 a.m. is a person

Sometimes the PC isn't waking itself. Somebody's up playing.

If that's your kid, a software fix is a stopgap, and a determined teenager gets around it. Windows has built-in screen-time controls for child accounts through Microsoft Family Safety, and they're worth setting up. But the lasting fix is agreement, not a lock. Gaming limits that survive contact with a real household covers how to set rules your kid will actually live with, and Count sessions, not minutes, and gaming stops being a fight gives you a cleaner way to frame the limit.

If it's you, be honest. A rig that stays on all night often belongs to a man who stays up all night. The PC does what you let it do. Set a shutdown time, and treat it like a work deadline.

A five-minute check you can run tonight

1. Run powercfg /lastwake and write down the answer.
2. Disable wake on the mouse.
3. Set the network adapter to magic packet only, or off.
4. Set Allow wake timers to Disable.
5. Turn off the maintenance wake in both places.
6. Put the PC to sleep and check it in the morning.

If it's still asleep at 7 a.m., you're done. If it isn't, run powercfg /lastwake again. The answer will be different, and that's how you close in on it.

If you're still planning the machine itself, Spend your first PC build money in the right order is worth reading before you buy a single part.

A well-set-up PC does one thing at night. It sleeps.