Ethernet not working on Windows 11 is deceptive because the cable is plugged in and the lights on the port might even be on — but nothing connects. The fix depends on which part of the Ethernet chain is broken, and that’s easier to figure out than it sounds. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Start with a 30-second check: is it only this machine, or is Ethernet broken on every device? If the router is showing a connected light for this port and other wired devices work fine, the problem is Windows-specific on this machine. If no wired devices work, the router or the cable to the ISP is the issue — restart the router and check with your provider if that doesn’t fix it.
Also: try a different Ethernet cable if you have one. Ethernet cables fail invisibly more than people expect, especially older ones that have been bent repeatedly. Swap the cable and test before changing any Windows settings.
Fix 1: The Network Stack Reset
The Windows TCP/IP and Winsock stacks accumulate configuration state over time, and certain events — failed VPN connections, abrupt network changes, some Windows updates — can leave them in a broken state that causes Ethernet to fail even when the hardware is fine. Resetting these takes two minutes and resolves a significant portion of Ethernet failures:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renewRun all five commands from an administrator Command Prompt in order, then restart the PC. After restarting, check whether Ethernet is working. This is the fix that resolves most Ethernet failures caused by software state rather than hardware — it’s worth trying before driver reinstallation because it’s faster and less disruptive.
Fix 2: Check the Adapter in Device Manager
Open Device Manager (right-click Start → Device Manager) → expand “Network Adapters.” Your Ethernet adapter should appear here without a yellow warning triangle. If it’s missing entirely or has a yellow triangle, the driver has a problem.
Yellow triangle: right-click → Update driver → Search automatically. If Windows finds nothing useful, go to your motherboard or laptop manufacturer’s support page and download the Ethernet driver directly. Manufacturer Ethernet drivers are generally more reliable than what Windows Update provides for Realtek and Intel NICs.
Adapter missing entirely: click View → Show hidden devices. If the adapter appears there (greyed out), it was disabled. Right-click → Enable. If it’s not visible even with hidden devices shown, try Action → Scan for hardware changes. If it still doesn’t appear, the adapter may have been disabled in BIOS — check BIOS/UEFI settings for an “Onboard LAN” or “Ethernet controller” option.
Fix 3: Update or Reinstall the Ethernet Driver
The Ethernet driver translates Windows network commands into signals the NIC (Network Interface Card) can understand. A corrupted or outdated driver causes the exact symptoms of Ethernet not working even when everything else is fine — the adapter is detected, the cable is connected, but data doesn’t flow.
For a clean driver reinstall: Device Manager → right-click the Ethernet adapter → Uninstall device → tick “Delete the driver software for this device” → Uninstall → restart. Windows reinstalls a driver automatically. If the reinstalled generic driver works, you can leave it or install the manufacturer driver for better performance.
For the manufacturer driver: check your PC’s model on the support site. Ethernet is typically handled by Realtek or Intel on most modern machines — the manufacturer provides specific driver packages rather than generic Windows versions. Realtek’s driver package from the motherboard manufacturer is almost always better than the inbox Windows driver.
Fix 4: Check Power Management Settings
Windows can power down the Ethernet adapter to save energy. When the power-save feature works correctly, the adapter wakes when traffic arrives. When it doesn’t — which happens with some driver versions and power plan configurations — the adapter stays powered down and Ethernet appears not to work, especially after the machine wakes from sleep.
Device Manager → right-click Ethernet adapter → Properties → Power Management tab → uncheck “Allow the computer to turn off this device to save power” → OK.
Also check the adapter’s Advanced tab for energy-related settings: “Energy Efficient Ethernet,” “Green Ethernet,” “Wake on Magic Packet,” and “Wake on Pattern Match” can all affect adapter behavior after sleep. Set Energy Efficient Ethernet to Disabled if present — it reduces power to the adapter when link activity is low and sometimes prevents proper reconnection after sleep or low-traffic periods.
Fix 5: Ethernet Not Working After Windows Update
Windows updates occasionally replace working Ethernet drivers with generic versions, or they change network stack settings that cause the adapter to stop functioning. If Ethernet stopped working immediately after an update:
Check Device Manager → Ethernet adapter → Properties → Driver tab → look at the Driver Date. If it matches the update date, roll it back: Driver → Roll Back Driver. If Roll Back Driver is greyed out, download the previous driver version from the manufacturer’s archive and install it manually.
Alternatively, check whether the “Use device IP settings” option was changed: Settings → Network and internet → Ethernet → your connection → DNS server assignment → verify it hasn’t been changed to a non-functional DNS configuration by the update.
Fix 6: Network Reset
When nothing else resolves Ethernet not working, a full Network Reset reinstalls all network adapters from scratch and returns every network setting to Windows defaults. This is more thorough than the winsock reset commands and handles cases where the adapter driver state has become fundamentally broken:
Settings → Network and internet → Advanced network settings → Network reset → Reset now → confirm.
Important notes: Network Reset removes VPN software adapters, clears all saved Wi-Fi passwords, and requires VPN software to be reinstalled. Have credentials and software installers ready. The reset takes about a minute and requires a restart. After restarting, the Ethernet adapter is reinstalled from scratch and usually begins working immediately.
Connected With No Internet: DNS and IP Issues
“Connected, no internet” is different from “Ethernet not working” — the physical connection is established but internet access fails. This is a DNS or IP configuration problem rather than a driver problem.
Check this: open Command Prompt and type ipconfig /all. Look at the IPv4 address for the Ethernet adapter:
- Starts with 169.254 — DHCP failed, Windows assigned a fallback address. Run
ipconfig /releasethenipconfig /renew, or restart the router to clear the DHCP lease table. - Valid address (192.168.x.x or 10.x.x.x) but no internet — DNS issue. Try
ping 8.8.8.8from Command Prompt. If ping works, DNS resolution is failing. Change DNS to 1.1.1.1 in adapter settings. - No address at all — DHCP server not responding. Router restart usually fixes this.
Router and Switch-Level Causes
Not all Ethernet failures are Windows problems. Router and switch issues produce identical symptoms from the Windows perspective:
DHCP exhaustion: If the router’s DHCP pool has assigned all available addresses to devices (including devices no longer connected), new connections can’t get an IP address. Restarting the router clears the lease table and resolves this immediately.
Spanning Tree Protocol delays: On managed switches, Ethernet ports go through a 30-second STP negotiation before allowing traffic. Windows shows “connected” but nothing loads for exactly 30 seconds, then it works. The fix is enabling PortFast on the switch port for end devices, but this requires switch administration access.
Specific port failure: Try a different port on the router or switch. If Ethernet works on port 2 but not port 1, that switch port has failed and simply avoiding it is the practical solution.
Our guide on Wi-Fi not working on Windows 11 covers many of the same network stack and driver approaches for wireless — if both Ethernet and Wi-Fi have stopped working simultaneously, the network stack reset is the most likely fix. For DNS-specific failures that persist even with a working Ethernet connection, our DNS server not responding guide covers the resolver and cache issues in depth. Microsoft’s Ethernet troubleshooting documentation covers 802.1X authentication failures on enterprise networks where Ethernet requires certificate-based authentication to function.
Checking the Physical NIC Health
The Ethernet port itself can fail — the physical RJ45 connector gets damaged, the magnetics inside the port corrode, or the NIC chip develops a fault. Physical NIC failure looks identical to a driver problem at the Windows level, but no driver fix resolves it because the hardware itself isn’t working correctly.
Signs that point to physical NIC failure rather than software: the link light on the Ethernet port (the small LED next to the connector) doesn’t illuminate at all when a known-good cable is plugged in, the adapter works briefly then disappears from Device Manager when under load, or the same symptoms appear on a different operating system (boot a Linux live USB and check if Ethernet works there — if it doesn’t work in Linux either with the same cable, the NIC is physically faulty).
For desktop machines with a physically failed NIC: a PCIe Ethernet card is an inexpensive fix (under $15 for a reliable Intel or Realtek card). For laptops with an integrated NIC failure: a USB-to-Ethernet adapter is the practical solution. Both work around the failed hardware without requiring board-level repair.
Enterprise and Corporate Ethernet: 802.1X Authentication
Corporate networks often use 802.1X port authentication — the switch requires the device to authenticate with a valid certificate or credentials before allowing traffic. On personal machines or unmanaged devices brought into a corporate environment, Ethernet connects at the physical level but the switch blocks all traffic until authentication completes. Windows shows “connected” but no internet, and the link lights are on — it looks exactly like a DNS problem but isn’t.
Check: connect the device to a home network via Ethernet and see if it works. If home Ethernet works but corporate Ethernet doesn’t on the same machine and cable, 802.1X authentication is almost certainly the issue. Corporate IT manages 802.1X; the fix is enrolling the device in the corporate authentication system or using a managed device that has the corporate certificate pre-installed. Checking Event Viewer → Applications and Services Logs → Microsoft → Windows → Wired-AutoConfig → Operational shows 802.1X authentication events with specific error codes that IT can use to diagnose the configuration issue.
Teaming and Virtual Adapters Interfering
Network adapter teaming (combining multiple NICs for performance or redundancy), VPN virtual adapters, VMware/VirtualBox virtual switches, and Docker virtual network adapters all create additional network interfaces in Windows that can interfere with the physical Ethernet adapter’s routing. When a virtual adapter has a higher priority in Windows’ routing table, traffic intended for the physical Ethernet adapter may route through the virtual one instead, causing apparent Ethernet failure while the physical adapter is technically connected.
Check for conflicting adapters: Settings → Network and internet → Advanced network settings → More network adapter options. This shows every network adapter including virtual ones. If VPN or VM software installed virtual adapters that are now disabled or inactive but weren’t properly cleaned up, disable them or uninstall the software that created them. After removing or disabling conflicting virtual adapters, Windows’ routing table updates and traffic flows correctly through the physical Ethernet adapter.
Wake-on-LAN Causing Intermittent Ethernet Issues
Wake-on-LAN (WoL) allows a machine to be powered on remotely by sending a magic packet to the sleeping NIC. When WoL is enabled but misconfigured — particularly when “Wake on Magic Packet” is combined with aggressive power management settings — the NIC can enter a semi-sleeping state during normal use that causes intermittent Ethernet drops rather than clean sleep/wake behavior.
The pattern: Ethernet works fine for hours, then drops without apparent cause and requires either unplugging/replugging the cable or disabling/enabling the adapter in Device Manager to restore. This intermittent pattern distinguishes it from a persistent failure. Fix: Device Manager → Ethernet adapter → Properties → Advanced tab → set “Wake on Magic Packet” and “Wake on Pattern Match” to Disabled. Also disable “Energy Efficient Ethernet” if present. These settings prevent the NIC from entering power states during active use that cause the intermittent drops.
Large Send Offload and Checksum Offload
Large Send Offload (LSO) and TCP/UDP checksum offload are hardware optimisations that let the NIC handle certain networking tasks that would otherwise require CPU processing. In theory this improves performance; in practice, certain combinations of NIC firmware, driver version, and network switch produce intermittent connectivity issues when these offloads are enabled — particularly on older or budget NICs.
If Ethernet is working but dropping packets, running slowly, or producing intermittent timeouts: Device Manager → Ethernet adapter → Properties → Advanced tab → find “Large Send Offload v2 (IPv4)” and “Large Send Offload v2 (IPv6)” → set both to Disabled. Also check for “TCP Checksum Offload” and “UDP Checksum Offload” settings and try disabling them. These don’t affect normal functionality for everyday tasks (browsing, email, streaming) but can resolve the underlying cause of the intermittent issues without requiring any hardware changes. Our guide on How to Fix Discord Not Working covers an adjacent issue.
