Fix Ethernet Doesn't Have Valid IP Configuration Error

This Windows error means your Ethernet adapter can't get an IP address from the router. Try the IP release/renew first, then check cables and drivers.

Quick answer for advanced users

Run ipconfig /release, then ipconfig /renew in an elevated Command Prompt. If that doesn't work, reboot your router and PC, then check your cable. For stubborn cases, reset Winsock and the TCP/IP stack.

Why this happens

This error shows up when your Windows machine can't get a valid IP address from your router's DHCP server. The network adapter is there, the cable might be plugged in, but for some reason the IP negotiation fails. You'll see the yellow triangle in the system tray, and the Network Diagnostics tool will tell you the exact problem.

It can happen after a power outage, a router firmware update, or just randomly when you boot up. Sometimes it's a loose cable, sometimes it's a corrupt network stack, and sometimes the router just needs a kick. The easiest way to think about it: your computer is asking for an address, and the router isn't answering.

Step-by-step fixes

Step 1: Release and renew your IP address

This is the most common fix and works about 60% of the time. Press Windows Key + R, type cmd, right-click on Command Prompt and choose Run as administrator. Then type these two commands one at a time:

ipconfig /release
ipconfig /renew

After the first command, you'll see your network adapters lose their IPs – that's normal. After the second, wait a few seconds for Windows to grab a new address. If you see an IP like 192.168.1.5 or 10.0.0.7, you're good. If you see 169.254.x.x, that means the renew failed.

Step 2: Reboot your router and PC

If the renew fails, unplug your router's power cord for 30 seconds, then plug it back in. Wait until the lights stabilize (usually about a minute). While you wait, shut down your PC completely. Once the router is up, turn the PC back on. This clears the ARP table on the router and gives your PC a fresh DHCP request.

Step 3: Check the Ethernet cable and ports

This might seem obvious, but a half-seated cable causes this exact error. Unplug the cable from both the PC and the router, then plug it back in until you hear the click. If you have another cable, swap it in – cheap cables break internally and show no visible damage. Also, try a different port on the router. Ports die.

Step 4: Restart the network adapter

Open Device Manager by right-clicking the Start button and selecting it. Expand Network adapters, find your Ethernet adapter (it'll have something like Realtek, Intel, or Killer in the name), right-click it and choose Disable device. Wait 10 seconds, then right-click again and Enable device.

Step 5: Reset Winsock and TCP/IP stack

If the above didn't work, the network stack might be corrupt. In the same elevated Command Prompt, run these commands one by one:

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

You'll need to restart the PC after. This resets the Windows network configuration to a clean state. Don't skip the restart – it doesn't apply until you reboot.

Alternative fixes if nothing above worked

Set a static IP address

Sometimes the router's DHCP is broken, and a static IP is the workaround. Find your router's IP address – usually 192.168.1.1, 192.168.0.1, or 10.0.0.1 – and your subnet mask (usually 255.255.255.0). In the same area, you'll need a free IP in your router's range, but not one that's taken. A safe bet: use an IP like 192.168.1.50 if your router is 192.168.1.1.

Go to Control Panel > Network and Sharing Center > Change adapter settings, right-click your Ethernet adapter, select Properties, double-click Internet Protocol Version 4 (TCP/IPv4), and select Use the following IP address. Fill in the IP, subnet mask, and default gateway (your router's IP). For DNS, use 8.8.8.8 and 8.8.4.4 (Google's) or 1.1.1.1 and 1.0.0.1 (Cloudflare's). Make sure that IP you pick isn't already assigned by your router, or you'll get a conflict.

Update or reinstall the Ethernet driver

Occasionally, a Windows update breaks the driver. Go to Device Manager, find your Ethernet adapter, right-click and select Update driver, then Search automatically. If no update is found, download the latest driver from your motherboard or laptop manufacturer's website – not from the generic Intel or Realtek site. A mismatched driver causes exactly this issue. If the problem started after a recent Windows update, use Roll Back Driver to undo that.

Prevention tips for the future

Most of the time, this error is a temporary glitch that rebooting fixes. To reduce the odds, make sure your router's firmware is up to date – check the manufacturer's support page for instructions. And avoid turning off your computer at the wall before Windows shuts down completely; that sometimes leaves the network adapter in a weird state. If it happens often, consider setting a static IP or replacing the router – a failing router causes these errors repeatedly.