Advertisement

Windows 11 Ethernet stops working after sleep

If Ethernet works before sleep but fails after wake, the problem is usually in one layer: the adapter, Windows power management, DHCP, or the dock/router port. This article helps you match the symptom to the fault and fix the right setting first.

Windows 8 min read

If Windows 11 Ethernet works before sleep but drops after wake, the usual causes are a power setting that puts the adapter too far to sleep, a driver that mishandles resume, or a dock, switch, or router port that renegotiates badly after wake. The fastest fix path is to check whether the link is down, the adapter has no IP, traffic is dead even though Windows says connected, or the adapter disappears. Then change the least disruptive setting first.

What the symptom is really telling you

The first clue is what Windows shows right after wake. If the network icon says the cable is unplugged, the link itself is down. That usually points to the adapter, cable, dock, or switch port.

If Windows shows connected but there’s no internet, the adapter is probably still up. The failure is then higher up the stack: DHCP, DNS, or the driver’s resume path. If the adapter vanishes from Device Manager after wake, Windows is not bringing the NIC back cleanly.

If the icon looks normal but nothing loads, treat that as a connected-but-dead case. That pattern often behaves differently from a true link drop. It’s also the one where a driver can look fine all day and still fail only after sleep.

This split matters because a cable can look fine when the PC is awake and still fail only during resume. A USB Ethernet adapter, dock, or motherboard port can each fail in a different way after sleep. So the exact symptom is more useful than the brand name on the hardware.

Before you start

Work through the checks in this order so you don’t change more than you need to.

  • Use the active Windows 11 power plan you normally use, because sleep and resume behavior can differ from one plan to another.
  • If you’re using a dock or USB Ethernet adapter, note whether the problem happens on the built-in motherboard port too.
  • If you can, save your work before testing sleep again, because the quickest verification is a full sleep/wake cycle.
  • Keep a path back: if a change makes no difference, revert it before moving on so you know what actually helped.

If the adapter disappears entirely after wake, or the same failure happens on more than one port, cable, or dock, start thinking about a hardware or compatibility problem rather than a simple Windows setting.

Start with the Windows power settings that most often break Ethernet resume

  1. Open your active power plan and check the advanced settings.

Look for PCIe link-state power management and any adapter-related power saving options. On some systems the labels vary a little. The goal is the same: stop Windows from pushing the network path into a deeper power state than it recovers from cleanly.

  1. Turn off Fast startup for the test.

Fast startup can carry a bad network state across a shutdown and make the next boot look like a wake problem. Disable it temporarily, do a full shutdown, then power the PC back on and test again.

  1. If the problem only appears after sleep, also check whether the machine is using hybrid sleep or another mixed sleep state.

That’s worth checking because one Microsoft Q&A case described Ethernet and Wi-Fi both failing to come back after sleep. In that case, a workaround that briefly used a phone hotspot brought both back to life. A different Microsoft Q&A thread described a desktop that lost Ethernet during hybrid sleep and then took 15 to 20 seconds to reconnect after waking.

If the connection now survives a full sleep/wake cycle, stop here. If nothing changes, put the setting back and move on to the adapter itself.

Change the adapter settings in Device Manager

  1. Open Device Manager and open the Ethernet adapter’s Properties.

On many systems, the adapter will be under Network adapters. Right-click the Ethernet device, open Properties, and start with the Power Management tab.

  1. Clear the setting that lets Windows turn off the device to save power, if it’s present.

This is the first adapter-level change I’d make. It directly affects whether Windows can power the NIC down too aggressively during sleep and fail to wake it cleanly.

  1. Check the Advanced tab for sleep-related options.

The exact names differ by Intel, Realtek, and other drivers. The settings worth reviewing first are the ones tied to power saving, low-power idle behavior, and wake behavior such as wake on magic packet. A Microsoft Q&A reply specifically pointed users to the adapter’s advanced settings when diagnosing wake-related Ethernet loss.

  1. Change one thing at a time, then test.

Don’t disable every power-saving feature at once. If you change several settings together, you won’t know which one fixed the resume path. You may also create a new problem while trying to solve the old one.

If the adapter starts behaving after one of these changes, leave that setting in place and stop. If not, put the setting back before you go further so you have a clean baseline.

If the problem began right after a driver update, rollback is the cleaner first test. If the issue survives a rollback, or the current driver came from Windows Update rather than the device maker, reinstall the latest stable driver from the system or adapter vendor. A driver can work perfectly while the PC is awake and still mishandle sleep and wake.

If it stays connected but nothing loads

When Windows says the adapter is connected but web pages won’t open, check whether the adapter has a valid IP address after wake. If you can open a command prompt, run ipconfig /all and look at the Ethernet adapter.

Command Prompt
ipconfig /all

If the address is missing, self-assigned, or stale, DHCP did not recover cleanly. If the IP looks normal but name lookups fail, the problem may be DNS rather than the physical link. Either way, that pattern points more toward a resume or driver problem than a bad cable.

A common mistake here is to keep swapping the router first when the adapter itself is the part that woke badly. If a manual network reset helps once and the issue returns after the next sleep cycle, that strongly suggests the driver or its power settings are mishandling resume.

What to check on a dock, USB Ethernet adapter, switch, or router

If only wake-from-sleep fails, the dock or USB path is often part of the problem. A USB Ethernet adapter behind a hub or docking station can lose its place during sleep and come back differently from a built-in NIC.

Check these in a simple order:

  • Try a different USB port on the dock or PC.
  • If the Ethernet adapter is plugged into a hub, connect it directly.
  • Reseat the Ethernet cable at both ends.
  • Try another known-good cable.
  • Move the cable to another switch or router port if you have one.

If the failure disappears when you change ports, the fault is probably in that path rather than in Windows. A router or switch port can be fine during normal use and still behave badly after the adapter renegotiates link speed or duplex during resume.

If the pattern only appears on one dock port, one USB adapter, or one switch port, that points more toward hardware or compatibility than a Windows setting. If the built-in motherboard port wakes cleanly but the dock or USB adapter does not, I’d trust the direct port first.

How to test the fix without guessing

Use one full sleep and wake cycle, then check the same few things every time.

  1. Save your work and disconnect any VPN or remote session.
  2. Put the PC to sleep once.
  3. Wake it normally.
  4. Check the network icon and the Ethernet link light, if the port has one.
  5. Open a browser and load a site you don’t usually have cached.
  6. If needed, run ipconfig /all and confirm the adapter kept or regained a normal address.

If Windows shows connected, the link light is on, and browsing works after wake, the fix held through the part that matters. If the cable looks unplugged again, go back to the Windows power settings and adapter power options before you chase the router. If the adapter disappears from Device Manager after wake, that’s a stronger sign of driver or hardware trouble than a simple settings issue.

Conclusion

If one setting fixes it, keep that change and leave the rest alone. If the same failure returns after sleep on multiple cables, ports, or docks, stop treating it like a Windows-only problem and start suspecting the adapter, dock, or firmware.

Frequently Asked Questions

Should I reinstall the Ethernet driver if Windows 11 Ethernet stops working after sleep?

Not first. Try the power settings and adapter power management options first, because a lot of wake failures are caused by how the device sleeps and resumes. If the problem started right after a driver update, rollback is usually the cleaner first driver step.

Why does the cable show connected but nothing loads after wake?

That usually means the link is up but DHCP, DNS, or the adapter’s wake path did not recover cleanly. In that case, the cable isn’t the first thing I’d blame. I’d check the adapter settings, then the dock, switch, or router port.

Sources