Fix DHCP Not Enabled for WiFi on Windows

Network & Connectivity Beginner 👁 0 views 📅 May 25, 2026

When DHCP is disabled on a Windows WiFi adapter, the device cannot obtain an IP address automatically, causing no internet access. This guide covers enabling DHCP via network settings and command line.

Symptoms

When DHCP is not enabled on your Windows WiFi adapter, you may experience the following:

  • WiFi shows connected but no internet access
  • IP address shows as 169.254.x.x (APIPA) in network details
  • Error message: "DHCP is not enabled for WiFi" in network troubleshooting
  • Unable to browse websites or use online services
  • Network icon shows yellow exclamation mark

Root Causes

DHCP (Dynamic Host Configuration Protocol) is responsible for automatically assigning an IP address, subnet mask, default gateway, and DNS servers to your device. When disabled, the adapter tries to use a static IP configuration that may be incorrect or missing. Common causes include:

  • Manual IP settings were previously configured and not reverted
  • Third-party VPN or network management software changed adapter settings
  • Corrupted network adapter drivers
  • Windows updates or registry changes
  • Malware or system tweaks

Step-by-Step Fix: Enable DHCP via Network Settings

Method 1: Using GUI (Graphical User Interface)

  1. Press Windows + R, type ncpa.cpl and press Enter to open Network Connections.
  2. Right-click on your WiFi adapter (usually named "Wi-Fi" or "Wireless Network Connection") and select Properties.
  3. In the list, double-click Internet Protocol Version 4 (TCP/IPv4).
  4. Select Obtain an IP address automatically and Obtain DNS server address automatically.
  5. Click OK and close all windows.
  6. Restart your WiFi adapter: Right-click the adapter and select Disable, then right-click again and select Enable.
  7. Check if internet works. Open Command Prompt and type ipconfig /renew to force a new DHCP lease.

Method 2: Using Command Prompt (Admin)

  1. Press Windows + X and select Command Prompt (Admin) or Windows PowerShell (Admin).
  2. Type the following commands one by one, pressing Enter after each:
    netsh interface ip set address name="Wi-Fi" source=dhcp
    netsh interface ip set dns name="Wi-Fi" source=dhcp
  3. Replace "Wi-Fi" with your adapter's exact name if different (use netsh interface show interface to list names).
  4. After running the commands, type ipconfig /renew and press Enter.
  5. Close the command prompt and test your connection.

Alternative Fixes

Reset Network Adapter

  1. Open Settings (Windows + I) > Network & Internet > Advanced network settings.
  2. Click Network reset > Reset now.
  3. Your PC will restart. After reboot, reconnect to WiFi.

Reinstall WiFi Driver

  1. Press Windows + X and select Device Manager.
  2. Expand Network adapters, right-click your WiFi adapter, and select Uninstall device (check "Delete the driver software for this device" if available).
  3. Restart your PC. Windows will automatically reinstall the driver.

Check DHCP Client Service

  1. Press Windows + R, type services.msc, press Enter.
  2. Find DHCP Client in the list. Ensure its status is Running and startup type is Automatic.
  3. If not, right-click and select Properties, set startup type to Automatic, click Apply, then Start.

Prevention

  • Always leave IP settings on "Obtain automatically" unless you have a specific static IP requirement from your network administrator.
  • Avoid using third-party network tools that modify adapter settings without your knowledge.
  • Keep your network drivers updated via Windows Update or manufacturer website.
  • Regularly run network troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Network Adapter.
  • Create a system restore point before making network changes.

Additional Tips

CommandPurpose
ipconfig /releaseReleases current IP configuration
ipconfig /renewObtains new IP from DHCP server
ipconfig /allShows full network configuration

If the problem persists after all steps, consider resetting your router or contacting your ISP, as the DHCP server might be malfunctioning.

Was this solution helpful?