Wake-on-LAN (WoL) lets you power on or wake a PC remotely by sending it a "magic packet" over the network. It depends on the hardware, the BIOS/UEFI, the network adapter driver and the state in which Windows left the PC. The most common case: WoL works from sleep, but not after a shutdown, because of Fast Startup.
What to know before acting
- Fast Startup and shutdown: Microsoft explains that on Windows 10, the default shutdown is a hybrid shutdown (Fast Startup, S4 state). In that case, and from a full shutdown (S5), WoL is not supported: Windows does not arm the network adapter for wake. WoL is supported from sleep (S3) or from an explicitly requested hibernate. Some hardware and firmware can still wake the PC from S4 or S5 without Windows being involved.
- Ethernet cable: Intel and Dell document WoL for the Ethernet adapter. Dell specifies that you need the built-in network adapter or a WoL-compatible USB adapter.
- Mains power required on laptops: according to Dell, WoL does not work when the computer is on battery, and this is by design.
- Same network: Intel states that both machines must be on the same subnet, with no separation other than a single router.
- Not every PC supports it: Dell refers to the computer's manual to check.
Step 1: test from sleep first
When to use it: always first, to find out whether the problem comes from the basic configuration or only from shutdown.
Expected result: the PC wakes from sleep. If so, the basic configuration is fine: only waking after shutdown is a problem, so go to step 4.
Step 2: configure the network adapter in Device Manager
When to use it: the PC does not wake up, even from sleep.
Expected result: the step 1 test wakes the PC.
When to stop: the names and availability of the Advanced tab options depend on the driver. Do not change the adapter's other settings. Intel also points out that on a PC using Modern Standby, these options may be greyed out.
Rollback: uncheck the boxes you checked and set the Advanced tab options back to their original values (note them before you start).
To check what Windows has taken into account, Microsoft documents these powercfg commands, to run in a command prompt:
powercfg /devicequery wake_armed
powercfg /lastwake
The first lists the devices currently allowed to wake the PC: the Ethernet adapter must appear in it. The second shows what woke the PC last time.
Step 3: enable Wake-on-LAN in the BIOS/UEFI
When to use it: the Windows settings are correct, but the PC still does not wake up, or the network port light goes out at shutdown.
Expected result: once the PC is shut down, the network port's link light stays on. According to Dell, if it is off, the network adapter cannot receive the magic packet.
When to stop: if your BIOS offers no Wake-on-LAN option, check the manual or support of your PC or motherboard manufacturer. Do not change other BIOS settings.
Rollback: disable the option the same way.
Step 4: waking after shutdown does not work (Fast Startup)
When to use it: WoL works from sleep, but not after Shut down.
Expected result: on hardware that allows it, the PC wakes up after a shutdown.
When to stop: Microsoft states that it does not recommend disabling Fast Startup, and that WoL from shutdown is not officially supported by Windows: it depends on the hardware and firmware. If your use allows it, leaving the PC in sleep remains the supported solution.
Rollback: check Turn on fast startup (recommended) again in the same window.
Special cases
| Situation | Documented lead |
|---|---|
| The PC wakes up on its own after the change | Check Only allow a magic packet to wake the computer (Intel). For other causes of unwanted wake-ups, see the French guide PC qui sort tout seul de la mise en veille sous Windows 10. |
| The packet does not seem to arrive | Check that the device sending the packet can ping the PC, and that the MAC address used is that of the PC's Ethernet adapter (Dell). |
| An IP address is entered in the WoL tool | Dell states that you may need to use the network's broadcast address: for a PC at 192.168.1.12, for example 192.168.1.255. |
| Intel adapter and waking from shutdown | Intel states that waking from shutdown (S5) on Windows 10 requires an updated Intel driver, and advises enabling the driver's wake on magic packet from power off state option, disabling power-saving options such as Energy Efficient Ethernet and reduced link speed, disabling Fast Startup and enabling WoL in the BIOS. |
Final check
- ☐ The PC is connected over Ethernet (and to mains power for a laptop).
- ☐ Allow this device to wake the computer is checked for the Ethernet adapter.
- ☐
powercfg /devicequery wake_armedlists the Ethernet adapter. - ☐ Wake-on-LAN is enabled in the BIOS/UEFI and the network light stays on once the PC is shut down.
- ☐ Waking works from sleep, and from shutdown if your hardware allows it.
Sources
- Microsoft Learn: Wake on LAN (WOL) behavior in Windows 10 (KB 2776718, updated 02/12/2026: hybrid shutdown S4, WoL unsupported from S4/S5, supported from S3 sleep or hibernate, disabling Fast Startup not recommended)
- Microsoft Learn: Powercfg command-line options (
/devicequery wake_armed,/lastwake) - Intel: Enabling Wake-on-LAN (driver options, Modern Standby, same subnet, magic packet only)
- Intel: Intel Ethernet Adapter Unable to Wake-on-LAN from S5 in Windows 10 (waking from shutdown with an Intel adapter, updated Intel driver required)
- Dell: Wake-on-LAN (WOL) troubleshooting best practices (Energy Efficient Ethernet, Deep Sleep, battery, link light, USB adapter, ping, MAC address and broadcast address)
Still having the problem?
Reply with the PC or motherboard model, the network adapter model (Device Manager), whether waking works from sleep, the output of powercfg /devicequery wake_armed, whether the network light stays on once the PC is shut down, and the tool used to send the packet. Mask part of the MAC address and your IP addresses before posting them.