Ethernet doesn't have a valid IP configuration fix

When this error hits

You're connected via Ethernet, the cable is plugged in tight, and your router's lights are blinking like a Christmas tree. But Windows throws up the network troubleshooter with the message: "Ethernet doesn't have a valid IP configuration". This usually happens after a sudden power outage, a router firmware update, or after you installed a new network driver. It can also pop up for no obvious reason — I've seen it on both Windows 10 and 11 machines, especially after a Windows update that messed with network settings.

What's actually going on

Your computer sends a DHCP request to the router asking for an IP address. The router is supposed to hand one out. But something in the chain is broken: the router's DHCP service might be stuck, your network adapter got confused, or Windows has a stale IP lease cached. In rare cases, a corrupted Winsock catalog or a misconfigured static IP can cause this.

Fix it in 6 steps

Try these in order — the first fix works for most people. If it doesn't, move to the next.

Step 1: Release and renew your IP from Command Prompt

Open Command Prompt as administrator (right-click Start > Windows Terminal (Admin) or Command Prompt (Admin)). Then run these commands one at a time:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

Wait a few seconds after each. If ipconfig /renew hangs or times out, that's a sign the router's DHCP is not responding. Move to step 2.

Step 2: Reset Winsock and the IP stack

Still in the same admin Command Prompt, run:

netsh winsock reset
netsh int ip reset
netsh int tcp set global autotuninglevel=normal

Restart your PC after this. The Winsock reset clears corrupted socket entries, and the IP reset rebuilds the TCP/IP stack from scratch. This fixed it for me on a Dell Latitude 5410 that wouldn't connect after a driver update.

Step 3: Disable IPv6 temporarily

IPv6 can cause conflicts with some home routers. Open Network Connections (press Win+R, type ncpa.cpl, hit Enter). Right-click your Ethernet adapter, go to Properties. Uncheck Internet Protocol Version 6 (TCP/IPv6). Click OK. If this works, leave it off — but only if you don't need IPv6 (most home users don't).

Step 4: Power cycle your router and modem

This sounds basic, but a router's internal DHCP server can get stuck. Unplug the power from both the router and the modem (if separate). Wait 60 seconds — not 10, not 30, a full minute. Plug the modem back in first, wait until all lights stabilize (about 2 minutes), then plug in the router. Wait another 2 minutes, then restart your PC. I've seen this fix the error on a TP-Link Archer AX73 that hadn't been rebooted in months.

Step 5: Update or reinstall the network adapter driver

Open Device Manager (right-click Start > Device Manager). Expand Network adapters. Find your Ethernet card (look for Realtek, Intel, or Killer). Right-click it, choose Update driver > Search automatically. If Windows finds nothing, go to the manufacturer's website and grab the latest driver. If the error started right after a driver update, roll back the driver instead (right-click > Properties > Driver > Roll Back Driver).

Step 6: Set a static IP manually

If nothing else works, assign a static IP outside your router's DHCP range. In Network Connections, right-click your Ethernet adapter > Properties > Double-click IPv4. Select Use the following IP address. For most home routers (like 192.168.1.x), use:

Make sure the IP you choose (like .50) isn't already used by another device. You can check your router's DHCP range in its admin panel — usually it starts at .2 and goes up to .254, so pick something in the middle that's likely free.

If it still fails

After all this, the error persists? Then you're looking at a hardware issue. Check the Ethernet cable — swap it with a known good one. Try a different port on the router. If your motherboard has two Ethernet ports (some high-end boards do), switch to the other one. I've also seen a faulty Network Interface Controller (NIC) cause this — in that case, a cheap USB-to-Ethernet adapter ($15 on Amazon) bypasses the problem completely. If you're on a Dell or HP laptop, run their built-in hardware diagnostic (press F12 at boot, choose diagnostics) to test the NIC.

One more thing: if your computer has both Wi-Fi and Ethernet enabled, Windows sometimes gets confused and tries to use the Wi-Fi adapter for the Ethernet connection. Disable Wi-Fi in Settings > Network & Internet > Wi-Fi > Off, then try a cold reboot (shut down completely, not restart, wait 10 seconds, power on). That alone saved me an hour of debugging once.