How to Fix ‘Ethernet Doesn’t Have a Valid IP Configuration’ in Windows 11

Connecting your Windows 11 PC directly to a router or network switch via a physical Cat6 or Cat5e Ethernet cable typically guarantees maximum speed and rock-solid reliability. However, running the built-in Windows Network Troubleshooter after a sudden loss of connectivity can produce a perplexing diagnosis: “Ethernet doesn’t have a valid IP configuration”, with a prominent red cross indicating no internet access.

This network failure indicates that your Ethernet network interface card (NIC) failed to obtain a functional private IP address from your local router’s Dynamic Host Configuration Protocol (DHCP) server. Instead of receiving a standard gateway address (such as 192.168.1.X or 10.0.0.X), Windows assigns itself an Automatic Private IP Addressing (APIPA) address beginning with 169.254.X.X, which cannot route internet packets. This comprehensive tutorial details how to flush corrupted network stacks, reset DHCP bindings, and restore wired internet connectivity in Windows 11.

Method 1: Release and Renew IP Address via Command Prompt

Releasing and renewing your local IP lease forces Windows to drop its invalid APIPA assignment and broadcast a fresh DHCP request to your router.

1. Press the Windows key, type cmd, and click Run as administrator.
2. In the terminal window, release the current IP binding by typing:

   ipconfig /release

3. Press Enter. Your Ethernet connection will briefly drop completely.
4. Next, flush the local DNS resolver cache:

   ipconfig /flushdns

5. Request a fresh IP address lease from your router’s DHCP server:

   ipconfig /renew

6. Review the output. If the IPv4 Address now displays a valid local subnet address (e.g., 192.168.1.15) with a matching Default Gateway, your wired connection is restored.

Method 2: Reset the TCP/IP Stack and Winsock Catalog

Corrupted network protocol socket entries or third-party packet filters (often left behind by uninstalled VPNs or third-party firewalls) can block the Windows network subsystem from processing DHCP acknowledgments.

1. Open an elevated Command Prompt (Administrator).
2. Reset the Windows Sockets (Winsock) catalogue:

   netsh winsock reset

3. Reset the entire TCP/IP stack back to clean installation defaults:

   netsh int ip reset

4. Clear network ARP resolution tables:

   netsh interface ip delete arpcache

5. Restart your computer immediately to allow Windows kernel drivers to rebind the reset network sockets.

Method 3: Configure Network Adapter to Obtain IP and DNS Automatically

If a previously configured static IP address conflicts with another device on your local network, or points to an obsolete gateway subnet, Windows will report an invalid IP configuration.

1. Press Windows + R, type ncpa.cpl, and press Enter to open Network Connections.
2. Right-click your Ethernet adapter and select Properties.
3. Under the list of networking items, double-click Internet Protocol Version 4 (TCP/IPv4).
4. Ensure that Obtain an IP address automatically is selected.
5. Ensure that Obtain DNS server address automatically is selected.
6. If you prefer custom DNS servers (such as Cloudflare 1.1.1.1 or Google 8.8.8.8), choose Use the following DNS server addresses, but leave the IP address assigned automatically via DHCP.
7. Click OK on both windows to apply changes.

Method 4: Reinstall the Ethernet Network Adapter Driver

Corrupted or outdated network controller drivers (such as Realtek PCIe GbE or Intel I225-V/I219-V controllers) frequently freeze DHCP handshake negotiations following Windows updates.

1. Right-click the Start button and select Device Manager.
2. Expand the Network adapters category.
3. Right-click your physical Ethernet adapter (e.g., Intel(R) Ethernet Controller or Realtek Gaming GbE Family Controller) and select Uninstall device.
4. In the confirmation window, do not check the option to delete driver software. Simply click Uninstall.
5. Click Action in the top menu of Device Manager and select Scan for hardware changes, or restart your computer.
6. Windows will detect the Ethernet hardware and reinstall clean driver bindings automatically.

Ethernet IP Configuration Troubleshooting Reference Table

Use this diagnostic table to isolate the specific network layer failure:

Observed State	Technical Root Cause	Recommended Corrective Step
IPv4 shows 169.254.X.X (APIPA)	Router DHCP server unreached or packet dropped	Power cycle router; execute ipconfig /renew
Static IP entered but no internet routing	Subnet mask or Default Gateway mismatch	Switch adapter to “Obtain IP automatically”
Error appeared immediately after VPN uninstall	Corrupted Winsock LSP or virtual filter driver	Execute netsh winsock reset in elevated CMD
Ethernet light on PC is orange/amber or off	Damaged Ethernet patch cable or faulty switch port	Replace RJ-45 cable; test different router LAN port
Intel I225-V adapter dropping connection	Energy Efficient Ethernet (EEE) driver sleep bug	Disable Energy Efficient Ethernet in Driver Properties

Power Cycling Your Router and Modem

If multiple computers or gaming consoles on your network simultaneously report invalid IP configurations, the fault lies within your router’s DHCP daemon, which may have exhausted its assigned IP pool or suffered a memory leak. Unplug the power cable from your router and modem, wait 60 seconds to completely discharge the onboard capacitors, reconnect the power cables, and allow two minutes for the local DHCP pool to initialise before testing your Windows 11 PC.