Computer Turns On By Itself: Why It Happens and How to Stop It

A computer that turns on by itself is triggered by a wake event, such as a scheduled task, network packet, hardware signal, or BIOS setting, that powers the system without user input.

Last updated: July 2026

Quick Answer: Why Does My Computer Turn On By Itself?

The most common reasons a computer turns on by itself are Wake on LAN, Windows wake timers, Fast Startup’s hybrid shutdown state, and scheduled maintenance tasks. In most cases, running powercfg /lastwake in an elevated Command Prompt will tell you exactly what triggered the last wake event. Fix that specific cause and the problem stops. The fixes below cover every OS from Windows 7 through Windows 11.

It’s annoying. You shut down at 11 PM, walk into your office at 7 AM, and find your PC running warm with fans spinning. Or worse, it wakes you up at 3 AM from the next room. Beyond the frustration, a PC cycling on and off unnecessarily puts real wear on your PSU, drives, and cooling system. This guide gives you a diagnostic-first approach so you’re not randomly trying fixes. Identify the cause, apply the right fix, and move on.

Why Does My Computer Turn On By Itself? (The 8 Most Common Causes)

Before touching a single setting, it helps to understand the landscape of possible causes. Some are Windows features working exactly as designed. Others are BIOS defaults that made sense in a server environment but not on a home desktop. A few are hardware problems entirely outside software’s control.

Here are the eight causes, ranked roughly from most to least common:

1. Wake on LAN (WoL): Your network card receives a “magic packet” from another device on your network and powers the PC on.
2. Windows Wake Timers: Windows schedules tasks during sleep that are allowed to wake the system, most often Windows Update.
3. Fast Startup: Windows 10 and 11 default to a hybrid shutdown that’s closer to hibernation than a true power-off, making it vulnerable to spurious wake events.
4. Scheduled Tasks: Task Scheduler has a per-task option called “Wake the computer to run this task.” Several built-in Microsoft tasks have this enabled by default.
5. BIOS Power Settings: RTC alarms, Power on by PCI-E, and similar BIOS-level triggers operate below the OS and bypass Windows settings entirely.
6. USB Device Wake: A wireless mouse dongle or USB hub can send a signal that wakes the system, even when you haven’t touched anything.
7. Automatic Maintenance / Windows Update: Windows 10 and 11 run a maintenance window (default: 2:00 AM) that can wake a sleeping or even shut-down PC.
8. Hardware Fault: A failing PSU, shorted power button header, or bad capacitors on the motherboard can cause erratic power behavior that mimics a wake event.

Cause	Affected OS	Frequency	Difficulty to Fix
Wake on LAN	Win 7 / 10 / 11	Very Common	Easy
Wake Timers (Windows)	Win 10 / 11	Very Common	Easy
Fast Startup	Win 10 / 11	Common	Easy
Scheduled Tasks	Win 7 / 10 / 11	Common	Moderate
BIOS Power Settings	All	Moderate	Easy-Moderate
USB Device Wake	Win 10 / 11	Moderate	Easy
Automatic Updates / Maintenance	Win 10 / 11	Common	Moderate
Hardware Fault (PSU/Mobo)	All	Rare	Hard

How to Find Out What’s Actually Waking Your PC (Before You Fix Anything)

Most guides skip straight to fixes. That’s the wrong approach. If you disable Wake on LAN when your actual problem is a scheduled task, nothing changes and you’ve wasted time. Two built-in Windows tools will tell you exactly what’s responsible. Use these first.

Method 1: Check the Windows Event Viewer Wake Log

Event Viewer records every wake event with a source identifier. Here’s how to pull it up:

1. Press Win + R, type eventvwr.msc, and hit Enter.
2. In the left panel, navigate to Windows Logs > System.
3. In the right panel, click Filter Current Log.
4. In the “Event sources” dropdown, select Power-Troubleshooter and click OK.
5. Look at the most recent entries. Each one will have a Wake Source field in the General tab below.

The Wake Source will say something like “Wake Timer,” “Device – USB Root Hub,” or “Network (NIC name).” That’s your culprit. Jump directly to the fix for that specific cause below.

Method 2: Run the PowerCFG Wake Report Command

This is the fastest diagnostic tool and it’s the one almost nobody mentions. Open Command Prompt as Administrator (right-click Start > Terminal (Admin) on Windows 11, or search “cmd” and run as administrator on Windows 10), then run this:

powercfg /lastwake

It outputs the exact device or timer that triggered the most recent wake. Clean and instant. If you want to go further, run:

powercfg /waketimers

This lists every active wake timer currently registered on the system, including which program created it and when it’s scheduled to fire. In my experience, this one command solves the mystery for the majority of users. You’ll either see a Windows Update timer pointing to a scheduled task, or you’ll see nothing (pointing to a hardware or network cause instead). You can find additional community-reported solutions at Tom’s Hardware Forums.

How to Stop Your Computer From Turning On By Itself: All Fixes

Work through these in order. Fix 1 and Fix 2 together resolve the problem for roughly 80-90% of users. If you’ve already confirmed your wake source using the diagnostic steps above, jump directly to the relevant fix.

Fix 1: Disable Wake on LAN (Most Common Cause)

Wake on LAN is a networking feature that lets other devices on your network boot your PC remotely. Useful in enterprise environments. Almost never needed on a home desktop. Disabling it requires two separate steps, and this is where most guides get it wrong. Doing only Part A often doesn’t stick because the Advanced NIC settings can override it.

Part A: Device Manager Power Management Tab

1. Press Win + X and select Device Manager (works on Windows 10 and 11).
2. Expand Network Adapters.
3. Right-click your primary network adapter (usually an Intel or Realtek NIC) and select Properties.
4. Click the Power Management tab.
5. Uncheck all three options, especially “Allow this device to wake the computer.”
6. Click OK.

Part B: Advanced NIC Settings (Required)

1. Back in the same Properties window, click the Advanced tab.
2. Scroll through the Property list and find Wake on Magic Packet. Set the Value to Disabled.
3. Find Wake on Pattern Match. Set it to Disabled as well.
4. Click OK.

Part C: Disable Wake on LAN in BIOS (Optional but Recommended)

If the above two steps don’t fully stop the behavior, the BIOS-level WoL setting can override Windows. Enter BIOS on boot (usually Delete or F2) and look for:

• ASUS: Advanced > APM Configuration > Power On By PCI-E/PCI > Disabled
• MSI: Settings > Advanced > Wake Up Event Setup > Wake Up By PCI-E Device > Disabled
• Gigabyte: Settings > Platform Power > Wake on LAN > Disabled

Fix 2: Disable Wake Timers in Windows Power Settings

Wake timers are Windows-level scheduled triggers that can wake a sleeping or hibernating PC. They’re enabled by default. This fix applies to Windows 7, 10, and 11, though the path varies slightly.

Windows 10:

1. Open Control Panel > Power Options.
2. Click Change plan settings next to your active plan.
3. Click Change advanced power settings.
4. Expand Sleep > Allow wake timers.
5. Set both On battery and Plugged in to Disabled.
6. Click Apply, then OK.

Windows 11: The same Control Panel path works. Alternatively, go to Settings > System > Power & sleep > Additional power settings, which redirects you to the same Control Panel screen.

Windows 7: Navigate to Control Panel > Power Options > Change plan settings > Change advanced power settings > Sleep > Allow wake timers > Disabled. Same logic, same path. Windows 7 doesn’t have Fast Startup, but wake timers absolutely exist and are worth disabling.

Fix 3: Disable Fast Startup

Fast Startup was introduced in Windows 8 and is enabled by default on every Windows 10 and 11 installation. It looks like a shutdown from the outside, but it’s actually a hybrid state closer to hibernation. The kernel session is saved to disk, and the system stays partially warm. That state is much more susceptible to spurious wake events than a true S5 power-off. Not a full shutdown. At all.

To disable it:

1. Open Control Panel > Power Options.
2. In the left sidebar, click Choose what the power buttons do.
3. Click Change settings that are currently unavailable (requires admin).
4. Under “Shutdown settings,” uncheck Turn on fast startup (recommended).
5. Click Save changes.

You can find more detail on exactly what Fast Startup does under the hood, and when else you might want to disable it, in our guide on Fast Boot in BIOS settings explained. The short version: unless boot speed is critically important to you, disabling it causes no downside and prevents a category of weird power behavior.

Fix 4: Audit and Disable Scheduled Tasks

Task Scheduler has a per-task setting called “Wake the computer to run this task” buried in the Conditions tab. Several built-in Windows tasks ship with this enabled. This is why your PC turns on at 3 AM even after you’ve disabled WoL and wake timers. Scheduled tasks operate independently.

1. Press Win + R, type taskschd.msc, and hit Enter.
2. In the left panel, expand Task Scheduler Library > Microsoft > Windows.
3. Check these specific subfolders and tasks:

• UpdateOrchestrator > Reboot: This one wakes PCs for Windows Update delivery.
• WindowsUpdate > Scheduled Start: Another update-related wake trigger.
• Power Efficiency Diagnostics > AnalyzeSystem: Runs battery and power diagnostics on a schedule.

For each task you find, don’t disable the task itself. Right-click it, select Properties, click the Conditions tab, and uncheck “Wake the computer to run this task.” the task still runs when you’re actively using the PC. It just won’t boot you up at night to do it.

Fix 5: Disable USB Device Wake

A wireless mouse receiver, keyboard dongle, or powered USB hub can send low-level signals that your system interprets as a wake command. Common culprit in setups where sleep mode is used instead of full shutdown.

1. Open Device Manager (Win + X > Device Manager).
2. Expand Universal Serial Bus controllers.
3. Right-click the first USB Root Hub and select Properties.
4. Click the Power Management tab and uncheck “Allow this device to wake the computer.”
5. Repeat for every USB Root Hub in the list.

Use powercfg /lastwake before doing this step. If the output doesn’t mention a USB device, skip it. No need to change settings that aren’t causing the problem.

Fix 6: Check and Adjust BIOS/UEFI Power Settings

BIOS-level power settings operate completely below Windows. Even a clean Windows install with every wake setting disabled won’t stop a BIOS-triggered wake. Enter your BIOS at boot and look for:

• Wake on RTC Alarm: Disable this. It’s a time-based BIOS wake trigger, often set by some OEM software.
• Power On By PCI-E: Disable to block network card-triggered wakes at the hardware level.
• Resume by Alarm: Disable if present.
• ErP Ready (EuP Ready): Set this to Enabled (or S4+S5). This forces a true S5 shutdown state with under 1W of standby draw, effectively blocking all wake signals from reaching the system.

The ErP setting is the nuclear option and it works. A user on Reddit confirmed that enabling ErP Ready to S4+S5 in BIOS under Advanced > APM Configuration solved persistent self-wake behavior that survived every Windows-level fix. When ErP mode is active, the system draws so little power in the off state that WoL magic packets can’t reach the NIC. For a full breakdown of what this setting does and the tradeoffs, see our explanation of ErP mode in BIOS.

Manufacturer-specific paths:

• ASUS: Advanced > APM Configuration > ErP Ready > Enable (S4+S5)
• MSI: Settings > Advanced > Wake Up Event Setup
• Gigabyte: Settings > Platform Power > ErP

Computer Turns On and Off By Itself: Is It Different?

Yes. Completely different problem. If your PC turns on and immediately shuts off (or cycles repeatedly), that’s not a wake event. That’s a hardware or POST failure.

• Turns on, stays on: Wake event. Use the diagnostic and fix sections above.
• Turns on, immediately shuts off: Failed POST, PSU fault, or CPU protection triggering before the system can initialize. Check for a missing CPU power connector, misseated RAM, or a dead PSU.
• Turns on, runs for 30-60 seconds, then shuts off: Thermal shutdown. The CPU is hitting a protection threshold, usually from a failed cooler, a dried-out thermal paste job, or a heatsink that’s worked itself loose.
• Repeating on/off cycle with no display: This is often a PSU that can’t hold its voltage rails under load, or bad capacitors on the motherboard causing unstable power delivery.

If your system is stuck in that repeating power cycle loop, check out our guide to signs of a failing power supply before buying anything. A cheap PSU doing this after a few years is not surprising. Less common, but real.

Can a Hacker Turn On Your Computer Remotely?

Technically possible. But probably not what’s happening to you.

Wake on LAN works by sending a “magic packet” to a network card’s MAC address. For this to work from outside your home network, your router would need to be specifically configured to forward incoming WoL packets to your internal IP. That’s not a default setting on any consumer router. An external attacker can’t cold-boot your PC over the internet without having previously configured that port forwarding themselves.

On a local network, yes, any device on the same subnet can send a WoL packet if it knows your NIC’s MAC address. That includes a NAS doing a scheduled backup sync, a smart home hub, or another PC running remote management software. These are the more realistic “remote wake” scenarios in a home environment.

A PC in true S5 shutdown with ErP mode enabled is effectively unreachable. Sub-1W standby draw means the NIC isn’t actively listening. Disabling WoL at both the Device Manager and BIOS level (Fix 1 above) eliminates this vector entirely for all practical purposes.

For external attackers to turn on your PC remotely, they’d need prior access to your network infrastructure. Random internet scanners can’t do it.

When Hardware Is the Culprit: Rare but Real

If you’ve worked through every software and BIOS fix and the problem persists, hardware is the remaining suspect. This category is less common, but it’s also the one most guides completely skip.

Failing PSU: An aging power supply with degraded capacitors can produce voltage fluctuations on the 5VSB (standby) rail. That rail stays live even when the PC is off, and erratic voltage on it can mimic a power button press to the motherboard. PSUs over five years old, or cheap units without an 80 Plus rating, are the most likely candidates.

Shorted or sticky power button: A front panel power button that’s stuck slightly depressed, or has a shorted header connector, will continuously signal the motherboard to power on. Test this by physically disconnecting the front panel power header from the motherboard’s JFP1 pins. If the self-starts stop, the button is your culprit.

Bad capacitors on the motherboard: Bulging or leaking capacitors near the power delivery circuitry cause erratic power behavior. Look for caps with domed tops or crust around the base. Flat-topped capacitors are normal. Dome-topped ones are not.

PCIe card generating spurious wake signals: A non-essential PCIe card (capture card, old network card, USB expansion card) can generate wake signals. Remove non-essential cards one at a time and see if the behavior stops.

Quick-Reference Fix Checklist

Use this as a bookmark. Work top to bottom, and stop when the problem stops.

• ☐ Run powercfg /lastwake in CMD (Admin) to identify wake source
• ☐ Run powercfg /waketimers to list all active scheduled timers
• ☐ Disable Wake on LAN in Device Manager > Network Adapters > Power Management tab
• ☐ Disable Wake on Magic Packet and Wake on Pattern Match in NIC Advanced settings
• ☐ Disable Wake Timers in Control Panel > Power Options > Advanced settings > Sleep
• ☐ Disable Fast Startup in Control Panel > Power Options > Choose what power buttons do
• ☐ Check Task Scheduler for tasks with “Wake the computer to run this task” enabled
• ☐ Disable wake permissions on all USB Root Hubs in Device Manager
• ☐ Enter BIOS and disable Wake on RTC Alarm, Power On By PCI-E, Resume by Alarm
• ☐ Enable ErP Ready (S4+S5) in BIOS for full lockdown of standby wake signals
• ☐ Disconnect front panel power header to test for a sticky or shorted power button

Frequently Asked Questions

Why does my computer turn on in the middle of the night?

The most common reason is Windows Update’s automatic maintenance window, which defaults to 2:00-3:00 AM. Task Scheduler tasks like UpdateOrchestrator\Reboot and WindowsUpdate\Scheduled Start are set to wake the computer by default. A NAS or smart home device on your network sending Wake on LAN packets during a scheduled backup sync is another frequent cause. Run powercfg /lastwake after one of these episodes to see exactly what fired.

How do I stop my computer from automatically turning on?

Start with Fix 1 (disable Wake on LAN in Device Manager, both the Power Management tab and the Advanced tab) and Fix 2 (disable Wake Timers in Power Options). Together these solve the problem for the majority of users. If those don’t fix it, disable Fast Startup and audit Task Scheduler for tasks with wake permissions enabled. If software fixes don’t work, check BIOS for ErP mode and RTC alarm settings.

Can hackers turn on your computer remotely?

Only under specific conditions. Wake on LAN requires the attacker to be on your local network, or your router must be specifically configured to forward magic packets from the internet (not a default setting). A random external attacker cannot cold-boot your PC over the internet without prior access to your network infrastructure. Disabling WoL at the Device Manager level and in BIOS eliminates this vector completely.

Why does my computer turn on by itself when in sleep mode specifically?

Sleep mode (S3 state) keeps the system in a low-power listening state where the NIC, USB controllers, and wake timers are all still active. It’s dramatically more vulnerable to wake events than a full shutdown (S5 state). A wireless mouse receiver, a WoL packet from your NAS, or an active wake timer can all pull the system out of S3. Full shutdown breaks more of those pathways. If sleep-specific wake events are the problem, disabling USB Hub wake permissions and wake timers (Fixes 2 and 5 above) are the most targeted fixes.

Does this problem behave differently on Windows 7 compared to Windows 10 or 11?

Yes, in a few ways. Windows 7 doesn’t have Fast Startup (that was introduced in Windows 8), so Fix 3 doesn’t apply. Wake on LAN and Wake Timers exist in Windows 7 and use the same Control Panel fix path. Windows 7’s automatic restart behavior for Windows Update is more aggressive than Windows 10 and 11, with fewer user controls over delivery scheduling, so update-triggered wakes are more common on 7. The powercfg /lastwake command works on Windows 7 as well and is your best starting diagnostic tool regardless of OS version.

The Bottom Line

Don’t start randomly disabling settings. Run powercfg /lastwake first, check Event Viewer if you need more detail, and then go directly to the fix that matches your specific wake source. For 90% of cases, the combination of disabling Wake on LAN properly (both the Power Management tab and the Advanced NIC settings), turning off Wake Timers in Power Options, and disabling Fast Startup is all it takes. If that doesn’t work, enabling ErP mode in BIOS is the definitive solution that blocks wake events at the hardware level. Still seeing issues after going through every step here? Drop your specs and what powercfg /lastwake returned in the comments and we’ll help you track it down.