Wake on LAN (or Windows 11 WOL) is one of those features that feels kinda magic when it works — a way to turn on a PC remotely just by sending a special packet over your network. But, of course, it’s not as simple as flipping a switch; there are a bunch of steps, and sometimes things don’t work right out of the box. Whether you’re trying to access your PC when you’re away or set up a remote management system, knowing how to properly enable and troubleshoot Wake on LAN can save tons of hassle. Stuff that doesn’t work can be maddening, especially if you’re sure everything’s enabled but still can’t wake your PC. So, here’s how to get it all set up and hopefully eliminate some of that mystery.
Part 1: Enable Wake on LAN (Windows 11) in BIOS/UEFI
The first step is to make sure your PC’s firmware settings actually allow wake signals. By default, a lot of machines have this turned off or hidden behind some obscure menus. You’ll need to restart your PC and get into BIOS/UEFI — not always fun because keys vary widely depending on the manufacturer. Common keys are F2, F12, Delete, or Esc. On some laptops, you might find an option under Settings > Update & Security > Recovery > Advanced startup, then reboot into UEFI firmware settings. Sometimes, you’ll have to try a couple of times to hit the right key.
Step 1. Restart your computer, then hit the right key for your system. If not sure, check the screen during startup or look up your PC model. Alternatively, go to Settings > Update & Security > Recovery. Under Advanced startup, hit Restart now and select UEFI Firmware Settings.
Step 2. Once inside BIOS/UEFI, find the section related to Power Management or Integrated Peripherals. That’ll differ depending on your hardware — some call it “Power, ” “Power Options, ” or “Advanced.” You’re looking for options that mention Wake on LAN, Wake on PCIe, or “Power on by PCI-E device.”
Step 3. Look for options labeled:
- “Wake on LAN”
- “Wake on PCI-E”
- “Power on by PCI-E device”
- “Resume by PCI device”
- “Wake on Network”
They’re often a toggle or a dropdown, turn them all on or enabled. If you see anything related to “Deep Sleep” or “ErP, ” disable those first because they can interfere with waking from the network. Because of course, Windows has to make it harder than necessary sometimes.
Step 4. Save your changes — usually press F10 or find the Save & Exit menu, then confirm. Your PC will reboot with these settings enabled.
Part 2: Configure Network Adapter Settings in Windows 11
After BIOS is sorted, Windows needs to know it’s okay to listen for wake signals. That involves digging into your network adapter settings in Device Manager. Yeah, it’s kinda buried, but not super complicated.
Step 1. Right-click the Start button and choose Device Manager. Might be faster to just hit Windows + X and select it.
Step 2. Expand the Network adapters section, then right-click your Ethernet device (if your PC uses Ethernet for Wake on LAN — Wi-Fi can get a bit twitchy, but it can work too).
Step 3. Select Properties.
Step 4. Head over to the Advanced tab.
Here’s where things get tricky because different network cards have different property names, but look for options like:
- “Wake on Magic Packet”
- “Wake on Pattern Match”
- “Wake on Link Settings” (sometimes needs enabling too)
Set all relevant “Wake on” options to Enabled. On some machines I’ve seen, you gotta do it one at a time or Windows will revert them; just keep poking until it sticks.
Step 5. Hit OK to confirm and move on.
This makes Windows aware that your network card should listen for magic packets — the secret signals that wake the PC. Honestly, it’s kind of weird, but enabling these options on the adapter is usually the key to making Wake on LAN actually work.
Part 3: Configure Power Management Settings
Next, Windows needs permission to actually wake the system. Even if BIOS and the adapter are set right, Windows’ power management can override those settings and kill the magic packets when you’re not looking.
Step 1. Back in the same network adapter properties (from Part 2), switch to the Power Management tab.
Tick these boxes:
- “Allow the computer to turn off this device to save power” (sometimes it’s already checked, but worth verifying)
- “Allow this device to wake the computer”
- “Only allow a magic packet to wake the computer”
This ensures Windows is okay with letting the device do its job when it’s supposed to wake up. Because otherwise, Windows might just ignore those packets.
Step 2. Hit Apply and OK. If you’re feeling especially thorough, repeat these steps for any other network device that might be involved.
Part 4: Adjust Windows 11 Power Settings
Sometimes Windows’ own power plan settings get in the way. Hybrid sleep, fast startup, USB suspend — all these can mess with Wake on LAN. Believe it or not, getting these out of the way can make a difference.
Step 1. Press Windows + X and select Settings.
Step 2. Choose System then go to Power & battery, especially on laptops. You want to set your power mode to Balanced. If you’re on a desktop, it’s less critical, but still good to check.
Step 3. Scroll down and click Additional power settings (this opens the old Control Panel style).Then select Edit Plan Settings, and go to Change advanced power settings.
Here’s where to get non-obvious: expand Sleep, then set Allow hybrid sleep to Off. Also, expand USB Settings > USB selective suspend setting and disable it.
If these aren’t set right, Windows might put your Ethernet adapter into a sleep mode that can’t wake up properly.
Step 4. Click OK to save everything.
Part 5 (Optional): Disable Fast Startup or Configure Windows Firewall
Another oddball — Windows’ Fast Startup can sometimes totally block wake packets from getting through. If you’re still having issues, turn it off.
Step 1. Hit Windows + R, type powercfg.cpl, and hit Enter.
Step 2. Click on Choose what the power buttons do on the left sidebar. Then, click Change settings that are currently unavailable.
3. Scroll to Shutdown settings and uncheck Turn on fast startup (recommended). Save changes and exit.
In some cases, the firewall blocks magic packets too, so you might need to open port 9/UDP in Windows Defender Firewall. Sure, it’s a hassle, but here’s a quick rundown:
- Open Windows Defender Firewall advanced rules.
- Create a new inbound rule for port UDP 9.
- Allow the connection, name it “Wake on LAN, ” and finish.
This way, your magic packets aren’t blocked and can reach your NIC.
How to Use Windows 11 Wake on LAN
Once everything’s set up, testing it is straightforward. Just remember, your PC must be fully shut down (not sleep or hibernate).Take note of its MAC address — you can get that by opening Command Prompt and running ipconfig /all. Look for your network adapter and find the “Physical Address” line.
From another device on the same LAN, run your favorite Wake on LAN app or use a tool or script to send a magic packet to that MAC. A popular and simple choice is something like WakeOnLan. Make sure you specify the right MAC and port (usually UDP port 9).
If everything’s configured right, your PC should power on within a few seconds. Sometimes it takes a couple of tries, especially if network configs are a bit flaky. But hey, that’s part of the charm of Wake on LAN — not 100% reliable without some tinkering.
Hopefully this shaves off a few hours for someone. It’s a mix of BIOS fiddling, Windows tweaks, and network settings, but once it’s all working, it makes managing remote systems way more convenient.
Summary
- Enabled Wake on LAN in BIOS/UEFI.
- Configured network adapter properties to allow wake signals.
- Adjusted Windows power management and power plan settings.
- Turned off fast startup, and set up firewall rules if needed.
- Tested with a magic packet from another device.
Wrap-up
Getting Wake on LAN to work can be kinda frustrating because of all the moving parts — BIOS, drivers, Windows settings, network quirks. But once it’s dialed in, it’s super handy. Different systems behave differently, so expect some trial and error. On some setups, everything just clicks after a reboot. On others, you might need to revisit settings or adjust your network environment. Fingers crossed this helps someone finally get it running without pulling their hair out.