Ethernet Not Working on Windows 11? How to Fix a Wired Connection

Ethernet Not Working on Windows 11? How to Fix a Wired Connection

The cable is plugged in, both ends look seated properly, and yet Windows insists the connection is unplugged, limited, or just won’t pull an IP address at all. It’s an especially frustrating kind of problem because there’s no signal strength icon to check and no password to re-enter — the cable either works or it doesn’t, or so it seems.

A wired connection failing has a genuinely different set of causes than a Wi-Fi problem, since there’s no radio, no signal strength, and no nearby network to interfere with it — just a cable, a port, a network adapter, and the driver and configuration behind all three. Working through those pieces in order finds the cause far faster than guessing.

Quick explanation: this guide covers ruling out the simplest physical causes first, confirming Windows sees the network adapter at all, an outdated or corrupted Ethernet driver, a connection that shows as limited or no-internet specifically over Ethernet, a duplex or speed mismatch with the router or switch, and resetting the network configuration as a last resort.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A wired connection that won’t work is most often either a driver problem Device Manager will flag directly with a warning icon, or a “limited connectivity” state where the adapter connects physically but never gets a working IP address from the router. Testing the cable and port with a different device first rules out the simplest physical causes — a bad cable or a dead port — before you spend time on anything Windows-side.

Rule Out the Cable and the Port First

Before touching any Windows setting, it’s worth eliminating the simplest possible causes: the cable itself and the port it’s plugged into. A cable that’s been stepped on, bent sharply, or just worn out over the years can fail in ways that look identical to a genuine software problem, and it’s the cheapest thing to test.
Trying a different cable, and plugging into a different port on the router or switch, isolates the problem quickly. It’s also worth glancing at the port’s activity lights — on the router, the switch, and the port on the PC itself — since lights that never turn on at all usually mean the connection isn’t being detected at the hardware level, before Windows even gets involved.
If a different cable and a different port both behave the same way, the problem is very likely on the Windows side rather than the physical connection, which is where the remaining checks in this guide come in.

Confirm Windows Sees the Network Adapter at All

A missing Ethernet adapter, or one showing a yellow warning icon in Device Manager, means Windows hasn’t properly loaded a driver for it — a different problem entirely from an adapter that Windows recognizes fine but simply isn’t connecting. It’s worth checking this before assuming the issue is anything more complicated.
If the adapter doesn’t appear under Network adapters at all, or appears with an error marker next to it, that’s usually enough on its own to explain why nothing works no matter what cable or port you try — Windows can’t use hardware it hasn’t properly recognized.
Fixyfier’s Windows Tools section puts a Device Manager shortcut right in the launcher, getting you straight to this view without digging through Windows Settings first to find it.

An Outdated or Corrupted Ethernet Driver

This is one of the more common causes behind a wired connection that suddenly stops working after being fine for months, especially right after a Windows update. An update can occasionally replace a manufacturer’s Ethernet driver with a generic one that doesn’t fully support the adapter’s features, even though the adapter still technically shows up.
The result is a connection that behaves unpredictably — dropping intermittently, refusing to negotiate a proper speed, or simply not working at all — despite the hardware itself being completely fine. Updating to the manufacturer’s proper driver, or rolling back to the one that was working before the update, resolves this more often than people expect.
Fixyfier’s System Tools section includes a List Installed Drivers tool that shows every driver currently installed and active, useful for spotting whether the Ethernet adapter is quietly running a generic driver instead of its proper manufacturer one.

“Limited” or “No Internet” Specifically Over Ethernet

When the adapter connects physically — the port lights are on, Windows shows the cable as plugged in — but the connection is still marked as limited or without internet access, that points at a DHCP or IP configuration problem rather than a hardware fault. The adapter is working; it just isn’t getting a usable address from the router.
Running ipconfig /all shows the full configuration for every adapter on the PC, including whether the Ethernet adapter actually received a valid IP address, a default gateway, and working DNS servers. An address in the 169.254.x.x range, or no address at all, confirms the adapter never successfully got a lease from the router.
ipconfig /all
Fixyfier’s Network & Connectivity section includes a Release & Renew IP tool that forces the device to drop whatever address it currently has and request a fresh one from the router, which is often enough to clear a stuck or invalid lease without any deeper troubleshooting.
NordVPN
One Thing Worth Knowing

A Wired Connection Isn't Automatically a Protected One

It's easy to assume a cable plugged straight into your own router at home or the office is the "safe" connection, with Wi-Fi being the only thing that actually needs securing. Traffic on a wired connection is just as visible to your ISP and anyone else positioned to see it — NordVPN encrypts it either way, cable or wireless.

Protect This Connection

A Duplex or Speed Mismatch With the Router or Switch

This one is rarer but real: the Ethernet adapter and the router or switch on the other end of the cable negotiate mismatched speed or duplex settings during the handshake that happens the moment a cable is plugged in. The result is a connection that appears physically fine yet behaves as unstable, slow, or unreliable in ways that don’t match the hardware everyone involved is actually capable of.
This tends to show up more with older or mismatched networking hardware — an adapter and a switch from very different generations, for instance — than with two modern devices talking to each other. It’s also more likely if the connection was fine on one port or switch and only started acting up after moving to a different one.
Manually forcing the adapter’s speed and duplex setting to match the router or switch, in the adapter’s advanced driver properties, resolves this by removing the automatic negotiation that’s producing the mismatch in the first place.

Resetting the Network Configuration as a Last Resort

If none of the steps above resolve it, a full reset of the network stack is worth trying even without knowing exactly what’s corrupted underneath. Network configurations accumulate small changes over time — from software installs, VPN clients, or Windows updates — and any one of those can leave behind a setting that quietly breaks a wired connection.
A reset clears all of that out at once, restoring the network stack to a clean, default state rather than asking you to hunt down which specific setting is responsible. It’s a broader step than anything earlier in this guide, which is exactly why it belongs last rather than first.
Fixyfier’s Network & Connectivity section includes both a Reset Network Configurations tool and a Reset TCP/IP tool, which together restore all network-related settings to their factory defaults in a couple of clicks rather than working through each one manually.

Frequently Asked Questions

Why would a wired connection ever have a driver problem if it’s just a cable?

The cable itself has no software in it, but the network adapter it plugs into does. That adapter needs a driver to talk to Windows the same way a Wi-Fi adapter, graphics card, or printer does, and that driver can go missing, get corrupted, or get quietly swapped for a generic one after an update — none of which has anything to do with the cable being fine.

Does a duplex mismatch actually happen often on home networks?

Not often, no. Most home routers and modern network adapters negotiate speed and duplex automatically without issue, so this is more of an edge case worth knowing about than something to suspect first. It shows up more with older networking hardware or mismatched equipment than with a typical home setup bought in the last several years.

Should I try a USB-to-Ethernet adapter if the built-in port seems dead?

Yes, and it’s a genuinely useful diagnostic step, not just a workaround. If a USB-to-Ethernet adapter gets online without any of the problems the built-in port was having, that strongly points to the built-in port or its onboard hardware as the actual cause, rather than anything in Windows’ network configuration.

Let Fixyfier Help You Get a Wired Connection Working Again

Fixyfier’s Windows Tools section puts Device Manager a click away for confirming the adapter is actually recognized, its System Tools section includes List Installed Drivers for spotting a generic driver where a proper one should be, and its Network & Connectivity section includes Reset Network Configurations for clearing out whatever’s left once everything else has been ruled out — together, a clear path from a dead cable icon back to a working connection.
Get Fixyfier from the Microsoft Store