Ethernet Not Showing Up in Windows 11

“Ethernet is missing” can describe several different failures. The Ethernet adapter may be absent from Windows entirely, it may appear in Device Manager but not have a usable driver, it may be present and enabled but show no cable or link, or the physical link may exist while IP configuration or internet access fails farther up the network stack. Those states need different fixes.

Before resetting anything, open Settings > Network & internet and Device Manager > Network adapters. Note whether Windows lists an Ethernet connection and whether Device Manager lists the wired controller or USB Ethernet adapter. Then connect the cable and observe whether the PC and router or switch report a physical link. This establishes whether the failure is detection, link, or networking rather than treating every symptom as the same Windows problem.

A cable does not make a missing PCIe or onboard network controller appear in Device Manager. If the wired adapter is absent, first determine what kind of hardware you have. An onboard Ethernet controller depends on the motherboard or system firmware and platform hardware path. A PCIe network card depends on its slot and platform enumeration. A USB Ethernet adapter adds the USB port, hub, dock, cable, and adapter itself to the detection path.

For onboard Ethernet, check the exact PC or motherboard documentation before changing firmware settings; some systems expose an onboard-LAN enable/disable control and others do not. For a USB adapter, connect it directly to another known-good compatible USB port when practical and check whether Device Manager changes. If Windows shows an Unknown device or a device with a warning icon instead of a named Ethernet controller, treat that as useful evidence that hardware is enumerating but the driver or device state still needs attention.

Expand Network adapters in Device Manager and open the Ethernet device properties. A normally identified adapter, a disabled adapter, and a device reporting an error are materially different states. If it is disabled, enable it and recheck the connection. If Windows identifies the controller but reports a device problem, record the status and error code before changing the driver so you preserve the evidence.

When a driver repair is justified, prefer the supported driver from the PC, motherboard, or network-adapter manufacturer for the exact model. Microsoft’s Ethernet troubleshooting guidance also recommends having a backup driver available before uninstalling the network adapter, especially when the affected PC has no other internet connection. Avoid generic driver-download sites and do not force an unrelated driver merely because the vendor name looks similar.

Once Windows can see the adapter, a “network cable unplugged” or equivalent disconnected state points lower in the path than DHCP or DNS. Microsoft recommends checking that the cable is firmly seated at both the Windows PC and the router, and trying another Ethernet cable when one is available. On a router, use a LAN Ethernet port intended for client devices rather than the WAN or Internet port used for the modem or upstream connection.

Change one part at a time. Try a known-good cable, then a known-good LAN port on the router or switch. If practical, test the same cable and network port with another Ethernet-capable device, or test the PC with a known-good network path. Link LEDs can be useful evidence when the hardware provides them, but their colors and blink patterns are vendor-specific; use the device manual rather than assuming one universal LED meaning.

IP addressing sits above adapter detection and the physical Ethernet link. If the adapter is missing or Windows still reports that the cable is disconnected, changing DNS servers, flushing the DNS cache, or renewing DHCP cannot repair the missing hardware or physical link. Establish detection and link first.

When the adapter is present and linked but Windows still has no network or internet access, the problem becomes a different branch. Settings > Network & internet can show the connection state, and the Ethernet properties expose the assigned IP information. On a typical DHCP-managed network, then inspect addressing, default gateway, DHCP and DNS rather than continuing to reinstall the hardware driver without evidence.

Microsoft recommends testing the same Ethernet network with another PC when possible. A second device that links and connects through the same cable and router port makes the original PC, its adapter, firmware, or driver path more suspect. If neither device works on the same known path, the cable, router or switch port, or upstream network becomes more credible.

A known-good USB-to-Ethernet adapter can also be a useful comparison on a PC with a missing onboard controller, but it is evidence rather than an automatic replacement recommendation. If USB Ethernet works while the onboard adapter remains absent from Device Manager, that proves Windows can use the network through a different hardware path; it does not by itself distinguish a disabled onboard controller, firmware issue, driver problem, platform fault, or failed NIC.

Windows Network reset is not a first-line fix for an adapter that firmware or Device Manager cannot enumerate, and it cannot repair a bad cable or dead switch port. Microsoft describes Network reset as a last step: it removes installed network adapters and their settings, then reinstalls the adapters after restart. VPN software and Hyper-V virtual switches may need to be configured again afterward.

Use the narrowest fix supported by the evidence. Re-seat or replace a proven-bad cable, enable a disabled adapter, install the correct supported driver when driver state is implicated, or move away from a faulty router port. Reserve broad resets for cases where the hardware is detected and narrower Windows networking checks have failed.

For a missing Ethernet connection, check whether Windows detects the adapter first. If it does, establish whether a physical Ethernet link exists. Only after both are true should you spend time on IP addressing, DHCP, gateway reachability, DNS, VPN or proxy configuration, and the wider internet path. This ordering prevents higher-layer fixes from obscuring a lower-layer failure.

If the adapter remains absent after checking the exact system firmware configuration, supported driver, and the relevant onboard, PCIe, or USB hardware path, use the PC, motherboard, or adapter manufacturer’s diagnostics and support documentation for that model. At that point hardware replacement may become a reasonable branch, but the absence of Ethernet in Windows alone is not enough evidence to declare the controller dead.