Computer Turning On by Itself at Night? First Work Out Whether It Was Asleep or Actually Off

You wake up at three in the morning and the office is glowing. The computer you are certain you turned off is sitting there with its fans spinning and the login screen up, or the monitor has come on and lit the whole room. It happens again the next night, and the night after, and it starts to feel less like a glitch and more like something is using your computer while you sleep.

The reassuring part first: this is almost never a sign that somebody is in your machine. In the overwhelming majority of cases it is a scheduled task, a device that is allowed to nudge the computer awake, a setting in the firmware, or the electricity coming back on after a brief interruption. All of those are findable, and most are a single checkbox.

The reason it takes people weeks to sort out is that nearly every guide on this topic hands you the same eleven-item checklist without asking the one question that decides which half of the list is relevant. So we will start there instead.

The question that splits this in half: asleep, or off?

A computer that was asleep and a computer that was shut down come back on for completely different reasons. A sleeping PC is woken, by something inside Windows or by a device that is permitted to wake it — and Windows keeps a record of it. A PC that was genuinely off is not woken at all; it is powered on, by the motherboard firmware or by the electricity supply, and Windows was not running to see it happen. Chasing Windows settings when the machine was off is the single most common way to lose an evening on this.

The easiest way to tell, and it costs nothing: look at what is on the screen when you find it running. If your programs and windows are still open exactly as you left them, it woke from sleep. If you are looking at the lock screen or a sign-in prompt with nothing open, and everything you had running is gone, the machine booted from a powered-off state. That single observation decides which half of this article you need.

There is a wrinkle worth knowing, because it explains a lot of confusing results. When you click Shut down in Windows 10 or 11, the default behaviour is not the old-fashioned full power-off. Microsoft calls it hybrid shutdown, and you know it as Fast Startup: it closes your session but writes the system half of Windows to disk, so the next start is quicker. Microsoft describes the resulting state as S4, the same power state as hibernation, even though it looks to you like a complete shutdown. So "it was off" is a slightly softer claim than most people realise, and if you want to remove that ambiguity while you are testing, turn Fast Startup off for a few days. Control Panel, Hardware and Sound, Power Options, "Choose what the power buttons do", then "Change settings that are currently unavailable", and untick "Turn on fast startup (recommended)". It is free, reversible, and it makes the rest of the diagnosis honest.

If it was asleep: make Windows tell you what woke it

Do not start changing settings. Windows already logged the answer, and guessing wastes days. Open the Start menu, type cmd, right-click Command Prompt and choose "Run as administrator", then run these four in turn. powercfg /lastwake reports what woke the machine most recently. powercfg /waketimers lists scheduled items that are currently permitted to wake it, and this is the one that usually names your culprit outright. powercfg /requests shows anything actively holding the PC awake. powercfg /devicequery wake_armed lists every device allowed to wake it — typically your keyboard, your mouse, and often the network adapter.

The better tool, and the one the checklists skip, is Event Viewer, because it keeps a history rather than only the last event. Press the Windows key, type eventvwr, and open it. Expand Windows Logs and click System. Right-click System, choose "Filter Current Log", and in the event sources list tick Power-Troubleshooter and Kernel-Power. You are looking for Event ID 1 from Power-Troubleshooter: open it and, at the very bottom of the General tab, it states the time it went to sleep, the time it woke, and a line reading "Wake Source". Now you can see whether it happens at the same time every night, which is itself a strong clue.

Be ready for that line to read "Wake Source: Unknown", because it often does — and treat that as information rather than a dead end. Windows reporting no identifiable wake source, especially alongside a boot rather than a resume, is a nudge towards the firmware and power causes further down this page rather than towards anything you can fix in Settings.

The 2 a.m. culprit hardly anyone checks: Automatic Maintenance

Windows runs a daily housekeeping pass — updates, security scanning, diagnostics, disk optimisation — under a feature called Automatic Maintenance, and by default it is scheduled for 2:00 a.m. precisely because that is when it expects nobody to be using the machine. There is a checkbox next to that schedule, and on a lot of computers it is ticked: "Allow scheduled maintenance to wake up my computer at the scheduled time." If your PC comes on at almost exactly the same time in the small hours, look here before anything else.

To find it, open Control Panel, go to System and Security, then "Security and Maintenance", expand the Maintenance section and click "Change maintenance settings". You can either move the run time to something civilised — an hour when you are usually at the desk anyway — or untick the wake box so maintenance simply waits until the machine is next on. Moving the time is the option we usually suggest, because the maintenance itself is doing useful work.

One honest limitation, and it is a useful test in its own right: this setting can only wake a computer that is asleep or hibernating. It cannot switch on a computer that is off. If your PC is powering up from a genuine shutdown, Automatic Maintenance is not your answer and you can stop looking at it.

Wake timers — and why "Disable" is usually the wrong choice

Underneath all of this sits a single power-plan setting that governs whether scheduled things are allowed to wake the machine at all. Open Control Panel, Hardware and Sound, Power Options, click "Change plan settings" next to your active plan, then "Change advanced power settings", expand Sleep and open "Allow wake timers".

Most articles tell you to set it to Disable and move on. Look closely, because there are normally three choices, not two: Enable, Disable, and "Important Wake Timers Only". That middle-ground option is almost always the right answer for a home or small-business machine — it blocks the routine wake requests that are annoying you while still letting genuinely important system events through. Turning wake timers off completely does stop the 3 a.m. start, but it also pushes update and maintenance work into the hours when you are actually trying to use the computer, which is how people end up complaining a month later that their PC now grinds to a halt every afternoon. On a laptop you will see two entries here, "On battery" and "Plugged in", and they can be set differently.

If powercfg /waketimers named a specific scheduled task, you can also deal with just that one rather than the whole category. Open Task Scheduler, find the task it named, open its properties and look at the Conditions tab: there is a checkbox reading "Wake the computer to run this task". Clearing it on that single task is the surgical version of this fix. Do not go on a deleting spree through the Task Scheduler library, though — plenty of what is in there is Windows doing its job, and the wake checkbox is the part you actually want gone.

The twitchy mouse on a shared desk

This one is far more common than its reputation suggests, and it produces the eeriest version of the symptom: the computer wakes when somebody walks past, when the dog jumps off the sofa, or when a truck goes by outside. An optical mouse only needs to register a fraction of a millimetre of movement to send a wake signal, and a mouse sitting on a hollow desk, a glass top, or a surface its sensor reads poorly will creep on its own with the smallest vibration.

Test it for free before you change any settings: put the mouse on a proper mat, or move it onto a different, more solid surface, and see whether the night-time wakes stop. If they do, you have your answer and you can decide whether you would rather keep the mouse where it is and disable its wake permission.

To do that, open Device Manager, expand "Mice and other pointing devices", right-click your mouse, choose Properties, open the Power Management tab and untick "Allow this device to wake the computer". Two practical notes. You will often find several "HID-compliant mouse" entries listed and no obvious way to tell which is the one on your desk, so unplug the mouse, see which entry disappears, and work on that one. And with some wireless receivers the keyboard and mouse share a single dongle, so you may have to untick the box on the keyboard entry as well before the wakes stop. If you do disable both, remember that you will then need the power button to wake the machine on purpose.

If it was actually off: the advice everyone repeats, and why it usually misses

Now the other branch, and this is where the standard checklist goes wrong. Search this problem and you will be told, near-universally, that your PC is being switched on by Wake-on-LAN — a feature that lets a network message power a computer up — and that you should go and disable it in Windows.

Microsoft's own documentation says otherwise for the shutdown case. Because Windows 10 and 11 shut down into hybrid shutdown by default, Microsoft states that Wake-on-LAN from that state, or from a classic shutdown, is unsupported: network adapters are, in its words, "explicitly not armed for WOL in these cases, because users expect zero power consumption and battery drain in the shutdown state". Wake-on-LAN is supported only from sleep, or from a hibernation you asked for deliberately. In other words, if your computer is starting from a Windows shutdown, the Windows-side Wake-on-LAN checkbox that every article points you at has already been switched off on your behalf, and unticking it again will change nothing.

That is not the same as saying the network is innocent, and the same Microsoft page is careful about it: the firmware and hardware on some systems can arm the network card for wake from those states on their own, without Windows being involved at all. So the setting worth checking is the one in your BIOS or UEFI — often listed as Wake on LAN, Wake Up on PCI-E, or Power On By PCI Devices — not the one in Windows. It is a small distinction that saves a lot of pointless clicking, and it is a fair test of whether a guide has any idea what it is describing.

Two firmware settings that really do switch a shut-down PC on

To reach these, restart and press the key your machine shows on the startup screen — usually Delete, F2, or F10 — to enter BIOS or UEFI setup. What you are looking for lives under a heading like Power Management, APM Configuration, or Advanced.

The first is a real-time clock alarm, listed variously as RTC Alarm Power On, Power On By Alarm, Resume By Alarm, or Wake up by RTC Alarm. It is a genuine scheduled power-on built into the motherboard, it works from hibernation and from a full shutdown, and it does exactly what your symptom describes: switches the computer on at a set time. If yours is enabled and you did not enable it, set it to Disabled. This one is worth checking first on any machine that starts at the same clock time every single night.

The second is the one that catches people out, because it is not a wake feature at all. It is usually called Restore AC Power Loss, AC Power Recovery, or After Power Loss, and it decides what the machine does when mains power returns after being cut. ASUS documents the three usual options plainly: Power Off leaves the machine off when power comes back, Power On boots it automatically, and Last State returns it to whatever it was doing before — so a PC that was on or asleep when the power blinked comes straight back on. ASUS ships Power Off as the default, but plenty of machines are set to Last State, either by the manufacturer or by whoever set it up. Worth knowing too: this setting only acts on a genuine loss of AC power, so it cannot be behind a PC that starts up on an ordinary, uneventful night.

The Southern California version: it was not your computer, it was the power

That last setting deserves its own moment, because out here it is a live explanation rather than a theoretical one. A power interruption does not have to be a blackout you would notice. A flicker of a second or two — the sort that resets the microwave clock and makes the lights dip when the air conditioning kicks in on a 108-degree afternoon in the Coachella Valley, or the sort that comes with a windy autumn night in the foothills — is more than enough. If the BIOS is set to Last State or Power On, the computer comes back up the instant the power does, at whatever hour that happens to be.

The tell is that nothing in Windows will ever explain it, and that is the point. Event Viewer will show a boot, not a wake. powercfg /lastwake will have nothing useful to say. No wake source is ever logged, because nothing woke the machine — it was switched on by the electricity returning. If you have been hunting for a wake source for a fortnight and finding none, this is the possibility to take seriously. Corroborate it the cheap way: check whether other clocks in the house are blinking, whether it lines up with hot nights or windy ones, and whether anyone else in the neighbourhood mentions a blip.

It is also the one version of this problem where the fix is a piece of hardware rather than a checkbox, and where the hardware is worth it on its own merits. A small UPS — a battery backup the computer plugs into — rides straight through a flicker, so the PC never loses power and never has to decide whether to come back on. That matters far more for what it protects than for the 3 a.m. nuisance: an abrupt power cut in the middle of a write is one of the more reliable ways to corrupt a drive, and repeated dirty shutdowns are hard on a power supply. Changing the BIOS setting to Power Off fixes the symptom; the UPS fixes the cause, and covers your router and modem while it is at it.

Laptops: the wake that happens inside a closed bag

On laptops this problem often shows up in a nastier form. You close the lid, put the machine in a bag, and take it out an hour later to find it hot to the touch and the battery down by half. Nothing switched itself on visibly, but it did wake — repeatedly — in an enclosed space with no airflow.

The cause is usually Modern Standby, the newer sleep behaviour that most recent Windows laptops use instead of the old deep sleep. It is designed to work like a phone: near-instant resume, and permission to do quiet background work such as syncing mail and collecting notifications while the lid is shut. When a driver or a background task misbehaves, those short wake windows stack up and the machine effectively runs in your bag. To see which type of sleep your laptop actually has, run powercfg /a in an administrator Command Prompt and read the list of available states: "Standby (S0 Low Power Idle)" means Modern Standby, while "Standby (S3)" is the older deep sleep.

The clean fix is not to fight Modern Standby but to sidestep it: hibernate the laptop before it goes in the bag instead of sleeping it. Hibernation writes everything to disk and genuinely stops, so there is nothing left running to wake up. Turn it on with powercfg /h on in an administrator Command Prompt, then add Hibernate to the Start menu power button and set the lid-close action to Hibernate under Power Options, "Choose what closing the lid does". You will find advice online for disabling Modern Standby outright with a registry edit — be careful with that one, because it only works if your laptop actually supports S3, and the powercfg /a output above is what tells you whether it does. If S3 is not listed as available, that edit can leave you with a laptop that has no working sleep at all.

When it is not a setting at all

A short list for completeness, because occasionally the cause is physical. A power button that has become sticky — worn, or with something lodged behind it — can register a press on its own; if the case button is the suspect, a desktop can usually be tested by unplugging that button's connector from the motherboard for a night. An ageing or failing power supply can send the board a false start signal. And it is always worth ruling out the least technical explanation before any of that: a smart plug on a schedule, a switched wall socket, a power strip somebody knocks with their foot, or another household member who genuinely did turn it on.

One thing this is generally not is an intruder. Remote access tools do not power up a computer that is off, and while Wake-on-LAN can in principle be used that way, it needs a machine already set up for it and a device on your own network to send the message. If you are worried on that front, the reassurance is in the same logs you have already been reading: a night-time wake with an ordinary wake source and nothing signed in afterwards is housekeeping, not a visitor.

How we can help

Most of this is a genuinely do-it-yourself job once the problem is split correctly — ask whether the machine was asleep or off, read the answer out of Event Viewer or powercfg, and go to the right half of the list. The evenings get lost when somebody works through a generic checklist that was written for the other branch, or disables Wake-on-LAN in Windows six times because six articles said to.

We look after computers for households and small businesses across Southern California and the Coachella Valley, and this is a quick job for us — finding the wake source, checking the firmware settings that actually power a machine on, and telling you honestly when the answer is that your power flickered rather than anything being wrong with the computer. If it turns out to be the power, we will get a UPS sized and set up properly, so the next flicker costs you nothing at all. And because we do not sell software, nobody here is going to point you at a paid tool for a problem that is one checkbox deep.