If an Intel Ethernet controller works before sleep or hibernate, then drops out after wake, the usual causes are Windows power management, a bad driver state, or a dock/USB-C path that does not resume cleanly. The safest first move is to check the cable and port, then the adapter’s power settings, then the Intel driver. What you do next depends on whether Windows still sees the adapter, the link light is out, or the device disappears.
What it usually looks like after wake
Start by sorting the failure into the three cases people usually see.
If the link light on the Ethernet port goes out after wake and never returns, the cable, the switch/router port, or the adapter may not be recovering. If Windows still shows the adapter but says there’s no network, that usually points to a driver or power-state problem. If the adapter disappears from Device Manager, Windows may not be reinitializing it cleanly.
A common pattern is simple: the PC wakes, Wi‑Fi still works, but wired Ethernet is disconnected, limited, or missing. Another is that the port looks alive, but Windows won’t use it until you disable and re-enable the adapter. That split matters. A dead link points you to the physical path first. A present-but-broken adapter points you toward Windows power settings and the Intel driver.
Before you start
Use the simplest checks first. That keeps you from treating a cable, switch port, or dock issue like a software fault.
- If this is an onboard Intel port, test with a different cable and a different switch or router port.
- If the connection goes through a dock or USB-C Ethernet adapter, try the built-in port instead, or remove the dock from the path for one test.
- If the same cable works on another device, the cable is less likely to be the cause.
- If the same dock path fails on another PC after sleep, the dock or its firmware is a stronger suspect than the Intel controller.
- If the adapter works again after a full reboot but not after sleep, that points more toward a wake-state problem than a dead port.
If the adapter is missing from Device Manager after wake, stop and note exactly what changed before you do anything else. That symptom usually means the device is not resuming correctly. It also helps you see whether the failure follows the cable, the dock, the driver, or the motherboard path.
The safest fix order
- Reseat the cable and try another port on the switch or router.
This is the least risky test, and it quickly tells you whether the problem is outside the PC. If the link returns, the fault was upstream, and you can stop there.
- Disable and re-enable the Ethernet adapter in Device Manager.
If that brings the connection back, the controller is probably stuck in a bad wake state rather than dead. That is a useful clue, but it is not a final fix. The next step is still to change the setting that let it get stuck.
- Test without the dock or USB-C chain.
If you normally use a dock or USB-C Ethernet adapter, bypass it for one wake test. A dock that works while the PC is awake can still fail to resume properly after sleep or hibernate.
- Check the Intel adapter power settings.
Open the adapter’s properties in Device Manager and look at the Power Management tab. Uncheck Allow the computer to turn off this device to save power if it is enabled. On some systems, that alone fixes wake-from-sleep behavior. Also check any advanced power-saving or Energy Efficient Ethernet options in the driver. Aggressive power saving can make wake recovery unreliable on some adapters.
- If the problem started after a driver change, roll the driver back first.
That is the quickest safe way to confirm whether the new driver is the trigger. If the adapter has been failing for a while and the installed driver is old, generic, or came from the wrong source for an OEM machine, update it from the PC maker first, or from Intel if the OEM does not provide a newer compatible package. Intel says that if the Ethernet controller is embedded on an OEM system, the generic Intel package may not be the right fit, and the manufacturer’s software is the safer choice.
- If the driver is still suspect, reinstall it cleanly.
Intel’s support guidance for the I225-V says to replace the network cable and perform a clean driver installation when the adapter suddenly stops working, and notes that the driver may need to be reinstalled to get it working again. If a disable/enable cycle only helps for one wake, a clean reinstall is a reasonable next step before you change firmware settings.
- Check sleep mode and Fast Startup.
Fast Startup can make a shutdown behave more like a hibernation-style resume than a full hardware reset, so a machine that fails after shutdown but not after a true restart may be showing the same wake problem through a different power path. Sleep, hibernate, and modern standby do not behave the same way, so test the mode that fails and the one that works before you assume the adapter itself is bad.
- Review BIOS or UEFI settings that affect the NIC’s recovery.
Look for settings tied to onboard LAN, wake on LAN, ERP, deep sleep power saving, and any option that changes PCIe or network wake behavior. The exact names vary by motherboard, so use the board manual or the vendor’s support page for your system. If a setting mentions power saving or wake behavior and you are not sure what it changes, change one thing at a time so you can reverse it cleanly.
When it is probably not the Intel adapter
It starts to look like hardware trouble when the failure follows the physical path, not the Windows state. If the problem happens across multiple cables and switch ports, if it shows up both through a dock and directly on the motherboard port, or if a clean driver reinstall does not change anything, the odds move away from a simple software issue.
Another clue is what happens when you disable and re-enable the adapter. If that reliably brings it back, the controller is still alive and is getting stuck during wake recovery. If that stops helping, or the device is gone until a full reboot, the problem is deeper and may be firmware or hardware.
The same caution applies when the failure only shows up through a dock, USB-C adapter, switch, or router path. In that case, the Intel controller may be fine, and the upstream device may be the real problem. When the same cable and port tests fail on more than one machine, or the adapter disappears no matter which wake setting you use, it is reasonable to stop tuning Windows and consider the NIC, dock, motherboard port, or firmware path as the thing that needs replacement or repair.
How to confirm the fix worked
Wake the PC from the same sleep or hibernate state that failed before. Then check all three signs: the adapter stays visible in Device Manager, the link light stays on, and Windows gets a normal network connection without needing a disable/enable cycle.
If the adapter only works after a manual toggle or a reboot, the fix is incomplete even if the connection comes back for the moment. The goal is a clean wake with no extra intervention. If you changed one setting and the problem disappeared, leave the rest alone so you still know which change mattered.
Frequently Asked Questions
Should I update or roll back the Intel Ethernet driver first?
If the problem started right after a driver change, roll it back first. If the installed driver is old, generic, or came from the wrong source for an OEM system, update to the current OEM or Intel package instead, then retest sleep and wake. That keeps you from chasing the wrong change.
Can Fast Startup really cause this?
Yes. Fast Startup can make a shutdown behave more like a hibernation-style resume than a full hardware reset, so an adapter that only fails after that path may look fine after a true restart. If that pattern fits, test Fast Startup before you change deeper firmware settings.
What should I do if disabling and re-enabling the adapter makes it work again?
Treat that as a clue, not a fix. It usually means the driver or power state got stuck during wake, so the next step is to change the adapter’s power-saving setting, then check the driver and sleep mode before you assume the hardware is bad.