Fix Ethernet Doesn't Have a Valid IP Configuration

You're connected via Ethernet, but Windows throws up that error: 'Ethernet doesn't have a valid IP configuration'. You've probably tried unplugging the cable and restarting the router. It didn't help. This usually happens after a Windows update, a power outage, or if you've been messing with network settings. I've seen it on Windows 10 22H2 and Windows 11 23H2 the most.

Why This Happens

Your network adapter is stuck trying to get an IP address from the router via DHCP, but something's blocking the handshake. Could be a corrupt Winsock catalog, a misconfigured IP stack, or the DHCP client service crapped out. The culprit is almost always a stale network cache or a driver that got hosed by an update. Don't bother with third-party 'network optimizers' – they rarely fix this and often make it worse.

The Fix – Do These Steps in Order

Step 1: Run the Network Troubleshooter (Quick Check)

Right-click the network icon in the system tray and select Troubleshoot problems.
Windows will try to auto-fix it. It might reset your network adapter. If it says 'Fixed', check if the error is gone. If not, move on.

This step rarely works, but it's fast. Don't rely on it.

Step 2: Release and Renew Your IP (The First Real Fix)

Open Command Prompt as Administrator (search for 'cmd', right-click, run as admin).
Type: ipconfig /release and press Enter.
Then type: ipconfig /renew and press Enter. Wait for it to finish (could take 30 seconds).
Type: ipconfig /flushdns and press Enter.

If it hangs for more than a minute, skip to Step 4. This step fails when the DHCP client itself is broken.

Step 3: Reset Winsock and the IP Stack (This Usually Does It)

In the same Command Prompt (admin), run these one at a time:
```
netsh winsock reset
```
```
netsh int ip reset
```
Restart your PC.

Winsock reset clears the socket catalog. The IP reset flushes the TCP/IP settings. On a clean Windows install, these two commands fix the issue 80% of the time.

Step 4: Reinstall the Network Adapter Driver

Press Win + X and select Device Manager.
Expand Network adapters. Look for something like 'Realtek PCIe GbE Family Controller' or 'Intel Ethernet Connection'.
Right-click your Ethernet adapter and select Uninstall device. Check the box that says 'Delete the driver software for this device' if it appears.
Restart your PC. Windows will auto-reinstall the driver.

If that doesn't work, go to your motherboard or laptop manufacturer's website, download the latest Ethernet driver manually, and install it. Don't use Windows Update drivers – they're often out of date or buggy.

Step 5: Restart the DHCP Client Service

Press Win + R, type services.msc, hit Enter.
Find DHCP Client in the list. Right-click and select Restart.
Set its startup type to Automatic (it usually is, but check).

This service should never be set to anything other than Automatic. If it's disabled, Windows can't get an IP at all.

Step 6: Manually Set a Static IP (Last Resort Workaround)

Open Control Panel > Network and Sharing Center > Change adapter settings.
Right-click your Ethernet adapter, select Properties.
Double-click Internet Protocol Version 4 (TCP/IPv4).
Select Use the following IP address and enter:
- IP address: 192.168.1.50 (or whatever your router's subnet is – check another device)
- Subnet mask: 255.255.255.0
- Default gateway: 192.168.1.1 (your router's IP)
- DNS servers: 8.8.8.8 and 8.8.4.4
Click OK on both windows.

This bypasses DHCP entirely. If the internet works, DHCP is the problem. But don't leave it static – switch back to automatic once you figure out why DHCP is broken.

If It Still Fails

Check the physical connection. Try a different Ethernet cable (Cat5e or Cat6, not a broken one). Plug into a different port on the router. If you're using a powerline adapter, bypass it – those things are flaky. Also, check if your router's DHCP pool is full. Log into your router (usually 192.168.1.1 or 192.168.0.1) and look at the DHCP settings. Make sure it's enabled and not set to some crazy small range like 192.168.1.2–192.168.1.10. Finally, if you're on a corporate network, talk to your network team – they might have MAC filtering or some other policy blocking you.