If a Realtek Ethernet adapter stops working only after sleep, the usual fix is to separate three cases: the link dropped, the driver stalled, or Windows failed to reconnect. Start with the adapter’s power settings in Device Manager, then check Windows power options like Fast Startup, then rule out cable, port, driver, and BIOS/UEFI resume settings one at a time.
What usually fails after sleep
The symptom tells you where to look first. If the Ethernet link light on the PC or switch stays off after wake, the adapter probably never renegotiated link. If Device Manager still shows the Realtek adapter but Windows says there’s no network, the driver or Windows resume path is more likely.
If the adapter is gone after wake, that usually points to a stronger power-management or firmware issue than a simple cable problem.
A quick Disable/Enable in Device Manager is a useful clue. If that brings the connection back, the hardware is usually alive and the problem is more likely to be power saving, driver behavior, or Windows not reconnecting cleanly. If the link light returns but Windows still shows no connectivity, that leans toward a Windows resume or driver issue rather than a dead port.
Check the easy settings first
Start with the Realtek adapter’s power settings in Device Manager, then check Windows sleep options, then look at BIOS or UEFI LAN settings. That order matters because these changes are reversible and don’t require guesswork. Change one thing at a time, then test sleep and wake before moving on.
- Open Device Manager, expand Network adapters, and open your Realtek Ethernet adapter.
- On the Power Management tab, clear the option that lets Windows turn off this device to save power.
- If you see a wake-related option on the same tab, leave it alone for now unless your motherboard manual tells you that a specific LAN wake setting needs it.
- If there’s an Advanced tab with energy-saving or wake features, note the names before changing anything. The exact options vary by Realtek model and OEM driver.
- Reboot, then put the PC to sleep and wake it once before changing anything else.
Next, check Windows power behavior that can interfere with Ethernet resume. Fast Startup is a common one because it changes how Windows comes back from a shutdown and can muddy troubleshooting when sleep and wake are the real problem. For a sleep issue, turn Fast Startup off while you test.
Control Panel > Hardware and Sound > Power Options > Choose what the power buttons do > Change settings that are currently unavailableThen clear Turn on fast startup and save changes.
If your motherboard BIOS or UEFI has LAN wake, deep sleep, ErP, or onboard LAN power-saving options, review those too. Names vary by board, and the setting that affects resume depends on the manufacturer. On some systems, a LAN power-save or deep-sleep option can keep the adapter from coming back cleanly after sleep. If you change one BIOS setting, record the original value first so you can put it back if it doesn’t help.
Rule out the cable, port, and network gear
Before you blame the driver, make sure the fault follows the PC. A bad cable or a flaky switch or router port can look exactly like a Realtek wake problem after sleep.
Use a simple swap test.
- Try a different Ethernet cable that you know works.
- Move the cable to another port on the switch or router.
- If possible, test the same cable and port with another computer or device.
- After each change, put the PC to sleep and wake it again.
- Watch the link light after wake before you open Windows network settings.
If the problem stays with the PC no matter which cable or port you use, the adapter, driver, or power settings are still the likely cause. If the problem follows the cable or port, stop chasing software fixes and replace the bad part. A negotiation issue on the switch or router can also show up only after wake, especially if the adapter is trying to come back at a speed or duplex setting the network gear doesn’t like. In that case, the link light after wake is the clue: no light usually means link negotiation failed, not that Windows forgot the network name.
Try the driver fix in the safest order
Use the safest sequence: update first if you have a clearly newer OEM driver, roll back if the problem started after a driver change, and only then do a clean reinstall. Change one thing at a time and test sleep and wake after each step.
- Check the PC or motherboard maker’s support page for the latest Realtek LAN driver for your exact model. In 2026, that OEM package is still the first driver to trust for wake-resume fixes, but the current support page is the source you should check before installing anything new.
- If the wake problem started right after a driver update, try Roll Back Driver in Device Manager instead.
- If the adapter behaves oddly after wake and a Disable/Enable fixes it only temporarily, uninstall the device from Device Manager and let Windows reinstall it, or install the OEM package again.
- Reboot and test sleep before making any other changes.
A newer OEM driver is usually safer than a random generic package because the board maker may have tuned it for that motherboard’s power behavior. If the newest driver made the wake problem worse, rolling back is a cleaner first test than piling on more changes. If the adapter works after Disable/Enable but not after sleep, that pattern often points to power-saving behavior rather than a damaged Ethernet port.
If Windows keeps loading the wrong driver, use the OEM package from the board or PC manufacturer rather than relying on whatever Windows Update picked. Check the current support page for your exact model before you install anything new.
Confirm it stays fixed after multiple sleep cycles
A single successful wake is not enough. The real test is whether the adapter survives repeated sleep and wake cycles without losing the link or needing a manual reset.
- Save your work, then put the PC to sleep.
- Wake it and check the Ethernet link light first.
- Open Windows network status and confirm the adapter has a live connection.
- Repeat the sleep and wake cycle a few times.
- Watch for the same failure pattern each time.
If the connection returns every time, keep the change and stop there. If it fails again, try the next reversible fix in the sequence rather than changing several things at once. If the adapter still disappears from Device Manager, or the link never returns after a clean driver reinstall and a known-good cable and port, the next practical step is a USB Ethernet adapter or hardware replacement.
A USB Ethernet adapter makes sense when you need a quick workaround and the built-in Realtek port is unstable after sleep. Hardware replacement makes more sense when the adapter fails across multiple cables, ports, and driver versions, or when the motherboard’s LAN behavior stays broken after BIOS and power-setting checks. At that point, the built-in port is no longer the best place to spend time.
Frequently Asked Questions
How do I tell if the adapter is dead or just not waking up?
If the adapter disappears from Device Manager after wake, or the link light never returns, you’re looking at a wake or power problem, not just a Windows display issue. If it stays present and works after Disable/Enable, the hardware is usually still alive and the fix is more likely in power settings or the driver.
Can Fast Startup cause the same problem?
Yes. Fast Startup can make shutdown and sleep behave differently, so it can hide what’s really happening. It’s worth turning off during testing and then checking whether the Ethernet adapter resumes normally after a real sleep-and-wake cycle.