sodcalculator

10 Tech How-To

Fix Unable to Contact Your DHCP Server Error on Windows 10

Guide 10-22513 · Updated · Step by step

If you see the “Unable to contact your DHCP server” error on Windows 10, your computer cannot get a valid IP address from your router, which usually means the DHCP service is stopped, the network adapter is misconfigured, or the router itself is failing. You can fix it by restarting the DHCP client service, renewing your IP address, or resetting the network stack. Below is a complete troubleshooting guide covering the most common causes and step-by-step fixes.

What Is DHCP and Why Does This Error Happen?

DHCP (Dynamic Host Configuration Protocol) is the system that automatically assigns IP addresses, subnet masks, gateways, and DNS servers to devices on a network. When your Windows 10 PC boots up or reconnects to Wi-Fi, it sends a broadcast request asking for an IP address. A DHCP server—usually your router—responds with a lease that lets you communicate on the network and access the internet.

The error appears when that request-and-response process fails. Instead of getting a valid IP, Windows falls back to an Automatic Private IP Address (APIPA) in the 169.254.x.x range, which only works on the local link and cannot reach the internet. The message often shows up in the Network and Sharing Center, in the output of ipconfig, or as a notification when you try to connect.

Common Causes of the DHCP Error

Several things can break the DHCP handshake. Knowing which one applies to you saves time:

  • DHCP client service stopped – The Windows service that handles DHCP requests may be disabled or not running.
  • Network adapter driver issues – Outdated, corrupted, or incompatible drivers can prevent the adapter from sending or receiving DHCP messages.
  • Router problems – The router’s DHCP server may be turned off, overloaded, or malfunctioning after a power surge or firmware update.
  • Static IP misconfiguration – If your adapter is set to a static IP that conflicts with another device, DHCP will fail.
  • Firewall or antivirus interference – Security software can block DHCP traffic (UDP ports 67 and 68).
  • Corrupted network stack – Winsock or TCP/IP settings can become damaged, especially after malware or improper uninstalls.

Fix 1: Restart the DHCP Client Service

The most direct fix is to ensure the DHCP Client service is running and set to start automatically. Here’s how:

  1. Press Win + R, type services.msc, and press Enter.
  2. Scroll down to DHCP Client. Right-click it and select Restart. If it’s not running, choose Start.
  3. Double-click the service, set Startup type to Automatic, and click OK.
  4. Close the Services window and restart your PC.

If the service fails to start, check the Windows Event Viewer for error codes. A common culprit is a third-party firewall or a corrupted system file. In that case, run sfc /scannow in an elevated Command Prompt to repair system files.

Fix 2: Renew Your IP Address

Sometimes the DHCP lease has expired or the router has forgotten your PC. Renewing forces a fresh request:

  1. Open Command Prompt as administrator (right-click Start and select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”).
  2. Type ipconfig /release and press Enter. This drops your current IP.
  3. Type ipconfig /renew and press Enter. This asks the DHCP server for a new IP.
  4. Wait a few seconds. If you get a 169.254.x.x address again, the DHCP server is still unreachable.

If renew fails, also try ipconfig /flushdns to clear the DNS cache, and netsh int ip reset to reset the IP configuration. Restart your PC afterward.

Fix 3: Reset the Network Stack

Corrupted Winsock or TCP/IP settings are a frequent cause. Resetting them restores default behavior:

  1. Open an elevated Command Prompt.
  2. Run netsh winsock reset and press Enter.
  3. Run netsh int ip reset and press Enter.
  4. Close the prompt and restart your computer.

This clears any misconfigured network filters and resets the IP stack. After reboot, try connecting again. If the error persists, move on to driver and router checks.

Fix 4: Update or Reinstall the Network Adapter Driver

A faulty driver can prevent DHCP from working. To update:

  1. Right-click the Start button and select Device Manager.
  2. Expand Network adapters, find your Wi-Fi or Ethernet adapter.
  3. Right-click it and select Update driver → Search automatically for drivers.
  4. If Windows finds nothing, visit the manufacturer’s website for the latest driver.

If updating doesn’t help, uninstall the driver (right-click → Uninstall device), then restart. Windows will reinstall it automatically. This often fixes hidden corruption.

Fix 5: Check Router and Network Settings

If the above steps fail, the problem may be on the router side. Try these in order:

  • Restart the router – Unplug it for 30 seconds, plug it back in, and wait for it to fully boot.
  • Check DHCP settings – Log into the router’s admin page (usually 192.168.1.1 or 192.168.0.1) and ensure DHCP is enabled. Look for a setting like “DHCP Server” or “Address Assignment.”
  • Disable and re-enable the adapter – In Control Panel → Network and Sharing Center → Change adapter settings, right-click your adapter and select Disable, then Enable.
  • Try a different device – If another device also gets the error, the router is likely the culprit. Reset it to factory defaults as a last resort.

Also check that your network cable is firmly connected (for Ethernet) and that Wi-Fi is enabled on your PC. A physical toggle or function key (like F2) can accidentally turn off Wi-Fi.

Fix 6: Manually Assign a Static IP (Temporary Workaround)

If DHCP is completely broken and you need internet immediately, you can set a static IP that matches your router’s subnet. This is a temporary fix until you resolve the DHCP issue.

  1. Open Control Panel → Network and Sharing Center → Change adapter settings.
  2. Right-click your adapter and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Choose Use the following IP address and enter:
    • IP address: 192.168.1.100 (replace 1 with your router’s subnet if different)
    • Subnet mask: 255.255.255.0
    • Default gateway: your router’s IP (e.g., 192.168.1.1)
  5. Set DNS to 8.8.8.8 and 8.8.4.4 (Google) or your ISP’s DNS.
  6. Click OK and restart the adapter.

This bypasses DHCP, but you must ensure the IP you choose isn’t already in use. After the DHCP server is fixed, switch back to “Obtain an IP address automatically.”

Frequently Asked Questions

Why does my PC get a 169.254.x.x IP address?

That’s an Automatic Private IP Address (APIPA). Windows assigns it when it fails to reach a DHCP server. It means your PC can communicate only with other devices on the same subnet that also have 169.254 addresses, but it cannot access the internet or your router’s admin page.

Can a VPN cause the DHCP error?

Yes, a VPN can interfere with your network adapter by adding virtual adapters or changing routing tables. Disconnect the VPN and disable any virtual adapters in Device Manager to see if the error goes away.

Does restarting the router fix the error?

Often yes. A router that has been running for weeks may have a hung DHCP service. Power-cycling it clears the memory and restarts the DHCP server. Wait at least 30 seconds before turning it back on.

Why does the error only happen on Wi-Fi but not Ethernet?

This usually points to a Wi-Fi adapter driver issue or a weak signal. Try updating the Wi-Fi driver, and also check if the router’s wireless settings are set to a channel or mode your adapter doesn’t support (e.g., 802.11ac vs. 802.11ax).

Is it safe to use a static IP instead of DHCP?

It’s safe if you choose an unused IP and set the correct subnet and gateway. However, it’s not recommended for laptops that move between networks, because a static IP that works at home won’t work at a coffee shop. Use it only as a temporary fix.

What if none of these fixes work?

If you’ve tried all the steps and still get the error, the issue may be with your router’s firmware or a hardware failure. Try connecting your PC directly to the modem with an Ethernet cable. If that works, the router is the problem. If not, contact your ISP or a professional technician.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →