“Ethernet doesn’t have a valid IP configuration” is a specific Windows error that means the adapter connected successfully to the network — the physical link is established — but didn’t get a valid IP address from the router. Without an IP address, nothing can route to the internet, and the error appears in Windows network diagnostics. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The most common cause: the router’s DHCP server didn’t respond in time, or the Windows DHCP client failed to process the response correctly. The fastest fix is forcing the adapter to release its failed address and request a new one:
ipconfig /release
ipconfig /renewRun from an administrator Command Prompt. Wait 30 seconds after /renew, then run ipconfig /all to check the IPv4 Address. If it now shows an address in the 192.168.x.x range (or whatever your router’s range is), the fix worked. If it still shows 169.254.x.x (a self-assigned fallback address), the DHCP request failed again — continue below.
What 169.254.x.x Actually Means
The 169.254.x.x address range is APIPA — Automatic Private IP Addressing. Windows assigns this to itself when it can’t obtain an address from DHCP. It’s a fallback that allows communication on the local link but can’t reach any router or the internet.
Seeing 169.254.x.x in ipconfig confirms that DHCP failed — either because the router’s DHCP server didn’t respond, the DHCP lease table is full, or the Windows DHCP client has a problem. This distinguishes the error from a different class of problems where Windows has a valid IP but can’t reach the internet for other reasons.
Fix 1: Restart Everything
The most reliable and underappreciated fix: restart both the router and the PC in the right order. Router first — unplug it for 60 seconds, then plug it back in and wait 2 full minutes for it to complete initialisation. Then restart the PC (not just the network adapter).
Why this order matters: if the PC restarts before the router is fully initialised, the DHCP request may fail again because the router isn’t ready. Waiting for the router first ensures a ready DHCP server receives the PC’s address request.
Fix 2: Full Network Stack Reset
Corrupted TCP/IP or Winsock configuration causes DHCP to fail even when the router is working. This is a common aftermath of VPN software installations, certain system optimisation tools, and some Windows updates. The reset commands clear this corrupted state:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /flushdns
ipconfig /renewRun all five from an administrator Command Prompt in order, then restart the PC. After the restart, the network stack initialises from a clean state and DHCP typically succeeds immediately.
Fix 3: Network Adapter Driver
An outdated or corrupted Ethernet adapter driver can prevent DHCP from working correctly even when the physical connection is fine. Windows updates occasionally replace manufacturer Ethernet drivers with generic versions that handle DHCP differently.
Device Manager → Network Adapters → right-click the Ethernet adapter → Update driver → Search automatically. If this installs a newer driver, test connectivity. For better results: go to the laptop or motherboard manufacturer’s support page and download the Ethernet driver directly — manufacturer drivers are more current and better tested than what Windows Update provides for Realtek and Intel NICs.
If the error started after a recent Windows update: Properties → Driver → Roll Back Driver to restore the previous working version.
Fix 4: Set a Static IP Address
If DHCP consistently fails despite the router working fine for other devices, manually assigning a static IP bypasses DHCP entirely. This is a workaround rather than a root cause fix, but it immediately restores connectivity while the underlying DHCP issue is investigated.
Settings → Network and internet → Ethernet → click your connection → IP settings → Edit → Manual → enable IPv4:
- IP address: 192.168.1.50 (choose a number above the router’s DHCP range — check the router’s admin panel for the range, often 192.168.1.1–192.168.1.100, and pick something above it like 192.168.1.200)
- Subnet mask: 255.255.255.0
- Gateway: 192.168.1.1 (your router’s IP — confirm in the router admin panel)
- DNS: 1.1.1.1 and 8.8.8.8
After saving: test internet access. If it works, DHCP is confirmed as the problem and a static IP is a viable long-term solution for this device. The risk of choosing a static IP within the DHCP range is address conflicts — choosing above the DHCP range prevents the router from assigning the same address to another device.
Fix 5: DHCP Client Service
The DHCP Client service handles IP address requests. When it stops — due to a crash, a registry change, or a system optimisation tool disabling it — DHCP fails for all adapters, producing the “no valid IP configuration” error.
Win + R → services.msc → find “DHCP Client” → confirm it’s Running and Startup type is “Automatic.” If it’s stopped: right-click → Start. If it shows Disabled: Properties → change Startup type to Automatic → Apply → Start. After starting the service, run ipconfig /renew to request a fresh IP address.
Fix 6: Check the Network Adapter’s Power Management
Windows can power down the Ethernet adapter to save energy. On wake from sleep, the adapter may not reinitialise correctly and DHCP fails to renew, producing the error. Device Manager → Network Adapters → right-click Ethernet adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.”
Also check the adapter’s Advanced tab for “Energy Efficient Ethernet” or “Green Ethernet” settings — disable these, as they reduce adapter power in ways that sometimes interfere with DHCP renewal after sleep.
When Multiple Devices Have the Same Problem
If every device on the network shows DHCP failures simultaneously, the router’s DHCP server is the issue rather than any individual machine. Check the router admin panel (usually 192.168.1.1) → DHCP settings → confirm the lease pool has available addresses. A completely exhausted DHCP pool — all addresses assigned to devices — produces exactly this symptom: new connections fail because no addresses are available to assign.
Increasing the DHCP pool range (changing the ending address from 192.168.1.100 to 192.168.1.200, for example) adds available addresses. A router restart also clears stale leases for devices that disconnected without properly releasing their addresses.
Our guide on Ethernet not working on Windows 11 covers the physical and driver-level Ethernet failures that cause the connection to not establish at all — a different problem from establishing the connection but failing at DHCP. For the Wi-Fi equivalent of this error, our Wi-Fi troubleshooting guide covers the same DHCP failure pattern on wireless connections. Microsoft’s IP configuration troubleshooting documentation covers the Windows IP Diagnostic tool and the more detailed DHCP client event logs in Event Viewer’s System log that capture every DHCP transaction attempt and failure reason.
Winsock Corruption From VPN Software
VPN clients modify the Windows Winsock and network layer configuration when they install. When a VPN is uninstalled without cleanly removing its network components, or when it crashes during a configuration change, it can leave the Winsock and TCP/IP stack in a state that prevents DHCP from functioning. This is a specific cause of the “no valid IP configuration” error that appears after installing or uninstalling VPN software, often the day after with no obvious trigger.
The network stack reset commands in Fix 2 address this directly. For particularly stubborn VPN remnants: Device Manager → Network Adapters → View → Show hidden devices → look for virtual adapters from the VPN software (TAP adapters, tunnel adapters, WireGuard adapters) → right-click → Uninstall device. Removing the virtual adapters the VPN left behind clears the network layer conflicts that were preventing DHCP from working on the physical Ethernet adapter.
DHCP Lease Conflicts
When a PC obtains an IP address from DHCP and then has a power outage or hard shutdown without releasing the lease, the router continues to hold that lease as “in use” even after the machine reconnects. If the lease hasn’t expired yet, the router may not re-issue the same address to the reconnected machine, and the machine may receive a conflict notification or no address at all.
The ipconfig /release command explicitly tells the router to release the current lease before /renew requests a new one — this is why using both commands is more reliable than just renewing. If conflict issues persist: access the router admin panel → DHCP lease table → find the PC’s MAC address → manually release its lease from the router side → then run ipconfig /renew on the PC.
Checking for Conflicting Antivirus Network Components
Some security suites install network drivers that sit between the physical adapter and Windows’ networking stack to monitor traffic. When these drivers malfunction or conflict with Windows updates, DHCP packets may not pass through correctly — the adapter sends DHCP discover requests, but the security driver drops or modifies them before they reach the router, and no IP address is returned.
Test: temporarily disable the network monitoring or firewall component of your antivirus (not the full antivirus, specifically any “network shield,” “firewall,” or “network monitor” component) and attempt ipconfig /renew. If a valid IP is obtained with the network shield disabled, the security software’s network driver is the conflict. Update the security software or check whether a Windows 11 compatibility update is available for it — this class of conflict typically appears after Windows feature updates that change how network drivers interact with the OS.
802.1X Enterprise Authentication
Some corporate networks require 802.1X authentication before DHCP addresses are assigned. The switch port the computer connects to remains in a restricted state (no DHCP, limited connectivity) until the authentication completes. When 802.1X credentials expire, certificates are outdated, or the authentication protocol mismatches, the Ethernet connection shows “no valid IP configuration” even though the physical connection is established.
On corporate machines: check whether the network adapter shows “Authentication” status during connection. Settings → Network and internet → Ethernet → your connection → see if there’s an authentication prompt. Corporate machines typically have the 802.1X settings configured by IT, and expired machine certificates or changed authentication server settings require IT intervention rather than local fixes.
Advanced: Checking DHCP Client Event Log
Windows logs every DHCP transaction in Event Viewer. Event Viewer → Windows Logs → System → filter for Source “DHCP-Client.” Events show exactly what happened during each DHCP attempt: whether the discover was sent, whether an offer was received, and why the handshake failed if it did. Common diagnostic events:
- Event ID 1003: “Your computer was not able to renew its address” — DHCP failed to renew
- Event ID 1007: “IP address conflict detected” — another device has the same IP
- Event ID 10158: “The IP address lease has expired” — lease expired without renewal
Each event describes the specific failure with enough detail to determine whether the problem is on the router side (no offer received), the local adapter (failed to send discover), or a conflict (address in use elsewhere). This ten-minute diagnostic saves working through all possible fixes when the specific failure mode is already logged.
When Ethernet Works After Network Reset But Breaks Again
If the network stack reset (Fix 2) restores connectivity but the “no valid IP configuration” error returns after the next restart or sleep/wake cycle, the fix is temporary because the underlying cause wasn’t addressed. Likely culprits for this pattern: a startup service that reconfigures the network stack at every boot (a VPN service, network monitoring software, or a scheduled task), or the Ethernet adapter’s power management putting it into a state where DHCP renewal fails after sleep.
Check Task Scheduler for any network-modifying tasks: Task Scheduler → Task Scheduler Library → look through tasks that trigger at startup or login. Any task from networking software that modifies adapter settings is a suspect. Also confirm the power management fix (Fix 6) is in place — disabling power management for the Ethernet adapter prevents the sleep/wake DHCP failure that causes the recurring pattern.
One final scenario worth checking: if a machine has multiple Ethernet adapters (a built-in NIC and a USB Ethernet adapter, or two built-in NICs on a desktop motherboard) and both are connected, Windows sometimes gets confused about which adapter should be the primary one with internet access. The DHCP response may arrive on the wrong adapter, or routing conflicts between the two adapters prevent internet access even when both have valid IP addresses. Disabling the adapter you’re not actively using (Device Manager → right-click the unused adapter → Disable device) or disconnecting its cable eliminates the multi-adapter confusion and usually restores the correct routing immediately.
Quick summary of which fix to try first based on when the error appeared: appeared right now with no changes → restart router and run ipconfig /release + /renew (Fixes 1 and 2). Appeared after VPN installation or uninstallation → network stack reset targeting Winsock (Fix 2) and remove VPN virtual adapters. Appeared after a Windows update → driver rollback (Fix 3). Happened before with no permanent fix → static IP assignment (Fix 4) while investigating root cause. Happens after every sleep/wake cycle → power management fix on adapter (Fix 6). This context-aware starting point cuts through to the relevant fix faster than working through the list top-to-bottom. Related: Ethernet Slower Than WiFi.
