Fix Windows 10/11 'Ethernet Doesn't Have a Valid IP Configuration'

You're working from home, coffee in hand, and suddenly the little network icon in the system tray shows a yellow triangle. You open Network Settings, and there it is: "Ethernet doesn't have a valid IP configuration." This happens right after boot, after waking from sleep, or sometimes mid-work for no apparent reason. I've seen it on Windows 10 and 11, on Dell, HP, and Lenovo laptops, and on desktop motherboards with Realtek and Intel NICs.

The root cause is simple: your Ethernet adapter is asking the router (or the DHCP server) for an IP address, and the router isn't answering, or the answer gets lost. Sometimes the adapter's cache is stale, sometimes the TCP/IP stack is corrupted, and sometimes the driver is just in a bad state. The good news? Most of the time you can fix it without reinstalling Windows.

Fix 1: Force a DHCP Renew

This is the first thing I try because it's the fastest and fixes 60% of cases. It clears the old IP and forces your adapter to ask for a new one.

1. Right-click the Start button and choose Command Prompt (Admin) or Windows Terminal (Admin).
2. Type ipconfig /release and press Enter. You'll see your Ethernet adapter lose its IP – the screen will show a bunch of zeros. That's normal.
3. Type ipconfig /renew and press Enter. This asks the DHCP server for a fresh IP. It might take 10-20 seconds.
4. When it finishes, type exit and close the window.

After the renew, check if the yellow triangle is gone. If it's still there, move on to the next fix.

Fix 2: Flush DNS and Reset Winsock

Sometimes the problem is deeper – the DNS cache or Winsock catalog (the thing that maps network services to your apps) gets corrupted. This fix resets both.

1. Open Command Prompt as Admin again (same as above).
2. Type ipconfig /flushdns and press Enter. You should see a message saying the DNS Resolver Cache was successfully flushed.
3. Type netsh winsock reset and press Enter. You'll see a message that the Winsock catalog was reset, and you'll need to restart the computer.
4. Type netsh int ip reset and press Enter. This resets the TCP/IP stack. Again, it will tell you to restart.
5. Restart your PC.

After the restart, check if the error is gone. If not, we're moving to the network adapter itself.

Fix 3: Uninstall and Reinstall the Ethernet Adapter

This sounds scary but it's safe. Windows will reinstall the driver automatically. It's like turning the adapter off and on again, but at a driver level.

1. Right-click the Start button and choose Device Manager.
2. Expand Network adapters. You'll see something like "Realtek PCIe GbE Family Controller" or "Intel(R) Ethernet Connection."
3. Right-click your Ethernet adapter and select Uninstall device.
4. In the popup, check the box that says "Delete the driver software for this device" if it appears (on Windows 10 it does; on 11 it doesn't always).
5. Click Uninstall. The screen might flicker, and your network icon will show a red X. That's fine.
6. Restart your computer. Windows will detect the missing driver and install the default one.

After restart, check if the error is resolved. If not, the next fix uses a static IP – a workaround, but a solid one.

Fix 4: Set a Static IP Address

If DHCP is failing repeatedly, you can bypass it and give your PC a fixed IP. This works perfectly for home networks, but if you're on a corporate network, check with your IT department first.

1. Open Settings (Win + I), go to Network & Internet, then Ethernet.
2. Click Edit next to "IP assignment."
3. Change the dropdown to Manual and turn on IPv4.
4. Enter these values (assuming your router is at 192.168.1.1 – if you're not sure, skip this fix and do Fix 5):

IP address: 192.168.1.100
Subnet prefix length: 24
Gateway: 192.168.1.1
Preferred DNS: 8.8.8.8
Alternate DNS: 1.1.1.1

Here's the catch: if your router uses a different subnet (like 192.168.0.1 or 10.0.0.1), this won't work. You'll need to check your router's IP. The next fix tells you how to see your current settings, which helps you pick the right numbers.

Fix 5: Reset Network Stack (Netsh Commands)

This is the nuclear option for network settings. It resets everything – Winsock, TCP/IP, and the firewall. It's combined with a full network reset in Windows.

1. Open Settings (Win + I), go to Network & Internet, then Advanced network settings.
2. Click Network reset.
3. Click Reset now. Windows will warn you that it will remove and reinstall all network adapters and set everything to default.
4. Confirm and let your PC restart. This takes a few minutes.

After the restart, you'll need to reconnect to your Wi-Fi (if you use one) and possibly re-enter the password. For Ethernet, it should just work.

What to Check If It Still Fails

If you've tried all these and the error persists, the problem might be outside your PC. Here's what I'd do next:

• Test the cable. Swap the Ethernet cable with a known good one. A damaged cable is a common culprit that mimics DHCP failures.
• Try a different port on the router. Ports go bad. Move the cable to another LAN port.
• Check the router's DHCP pool. Log into your router (usually at 192.168.1.1) and see if you've run out of addresses. If you have dozens of devices on at once, that's likely.
• Update the network driver. Go to the manufacturer's website and download the latest driver for your specific adapter. Windows Update isn't always current.

One last thing: if you're on a Windows laptop with both Wi-Fi and Ethernet, disable the Wi-Fi adapter while testing Ethernet. I've seen conflicts where the OS gets confused about which adapter should have the IP.

That's the full playbook. Start with the quick commands, then escalate. Most people get it fixed by step two.