How To • Networking • IP/DHCP Issues

How to Fix APIPA 169 Address Issues on Windows

This guide will help you diagnose and resolve the problem where your Windows computer assigns itself a 169.254.x.x IP address, preventing internet access. You will learn how to force your device to obtain a valid IP from your router or network.

Note: Steps may vary by device and router model. This guide focuses on safe, general methods.

Quick Answer

Restart your computer and your router.
Run the Windows Network Troubleshooter (search in Start Menu).
Disable and re-enable your network adapter in Windows Settings.
Open Command Prompt as Administrator and run: ipconfig /release then ipconfig /renew.
Verify your router's DHCP server is turned on.

If this doesn't work, follow the diagnostic flow below to pinpoint the exact cause.

What you need

Before you start

A Windows PC with administrator access.
Physical access to your router/modem (to restart it).
Knowledge of how to log into your router's admin page (check the label on the router).
Another device (like a phone) that can access the internet, to check if the problem is isolated.
Optional: An Ethernet cable to test a wired connection.

Good to know

APIPA (169.254.x.x) means your PC failed to contact a DHCP server.
DHCP is the service on your router that hands out IP addresses.
This is usually a local network issue, not a problem with your Internet Service Provider.
Windows automatically tries to get a new IP address every so often.
Static IP misconfiguration can also cause this.

Diagnose the issue in 2 minutes

Is it only one device or all devices?
- All devices: Problem is likely with your router or ISP connection. Restart your router first.
- One Windows PC: Problem is likely with that PC's connection or settings. Proceed below.
On the affected Windows PC:
- Open Command Prompt, type ipconfig. Does it show an IPv4 address starting with 169.254?
  - Yes: DHCP failure is confirmed. Is Wi-Fi or Ethernet connected?
    - Wi-Fi: Try forgetting the network and reconnecting.
    - Ethernet: Try a different cable or port on the router.
- Can you ping your router's default gateway (e.g., 192.168.1.1)?
  - Command: ping 192.168.1.1
  - No reply: Physical connection or router issue.
  - Reply received: Router is reachable, but DHCP service may be off.

Quick Checks:

Check: Is Airplane Mode or a VPN turned on? (Turn them off temporarily).
Check: Does the network icon show "No Internet" or "Unidentified Network"?
Check: Have you recently installed new security software? (It may have a firewall blocking DHCP).

Step-by-step guide

Step 1 — Restart everything

Power cycling clears temporary glitches in devices and connections.

Restart your Windows computer.
Unplug your router and modem from power for 60 seconds, then plug them back in. Wait for all lights to stabilize.

What you should see: After restarting, check ipconfig again. The IP should now start with 192.168.x.x, 10.x.x.x, or 172.16.x.x.

Step 2 — Use Windows Network Troubleshooter

Let Windows automatically detect and attempt to fix common problems.

Click the Start button and type "Network Troubleshooter".
Select "Identify and repair network problems".
Follow the on-screen prompts and apply any recommended fixes.

Step 3 — Renew the IP address via Command Prompt

This forces your PC to request a new IP address from the router.

Search for "Command Prompt", right-click it, and select "Run as administrator".
Type ipconfig /release and press Enter. Your connection will drop.
Type ipconfig /renew and press Enter. Wait for the command to complete.
Type ipconfig to verify you have a non-169.254 address.

What you should see: "DHCP request successful" or a similar message. A new, valid IP address appears.

Step 4 — Disable and re-enable the network adapter

This resets the adapter's software state, similar to rebooting just the network hardware.

Press Windows Key + X and select "Network Connections".
Right-click your active Wi-Fi or Ethernet adapter and select "Disable". Wait 10 seconds.
Right-click it again and select "Enable". Wait for it to reconnect.

Windows: You can also do this via Settings > Network & Internet > Change adapter options.

Step 5 — Check for static IP or incorrect settings

Ensure your PC is set to obtain an IP address automatically, not using a manual (static) IP.

In Network Connections, right-click your adapter and select "Properties".
Select "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties".
Ensure "Obtain an IP address automatically" and "Obtain DNS server address automatically" are selected.
Click OK and close all windows.

Step 6 — Update or reinstall network drivers

Outdated or corrupted drivers can cause communication failures with your network hardware.

Press Windows Key + X and select "Device Manager".
Expand "Network adapters". Right-click your Wi-Fi or Ethernet adapter.
Select "Update driver" and choose "Search automatically for updated driver software".
If that doesn't work, select "Uninstall device". Do not delete driver software if prompted. Then restart your PC; Windows will reinstall the driver.

Common fixes by symptom

Connected but no internet (APIPA address)

Likely causes: Router DHCP server disabled; Firewall blocking DHCP requests; Maximum DHCP leases reached on router.

Safe fixes: Log into router admin page and ensure DHCP is enabled. Temporarily disable third-party firewalls/antivirus. Restart router to clear DHCP lease table.

When to stop: If you cannot access the router admin page (often 192.168.1.1) from any device.

Wi-Fi has APIPA, but Ethernet works

Likely causes: Incorrect Wi-Fi security protocol; Router's wireless radio failing; Driver issue specific to Wi-Fi adapter.

Safe fixes: Forget the Wi-Fi network on your PC and reconnect. Update Wi-Fi drivers. In router settings, try a different Wi-Fi band (2.4GHz vs 5GHz).

When to stop: If only one specific device has this Wi-Fi problem, it's likely the device, not the router.

IP conflict (duplicate address on network)

Likely causes: Another device using a static IP that's in the DHCP range; Router assigning same IP to two devices (rare).

Safe fixes: The ipconfig /release and /renew commands often resolve this. Restarting all devices can clear the conflict.

When to stop: If conflicts keep happening, check all devices for manual IP settings.

VPN turns on and local network breaks

Likely causes: VPN client taking over the network adapter and disrupting local DHCP.

Safe fixes: Disconnect the VPN. Check VPN app settings for options like "Allow local network access". Temporarily uninstall the VPN software to test.

When to stop: If the problem is 100% reproducible with a specific VPN app, contact their support.

Quick reference

What the metric means

Metric	Relevance to APIPA
Latency (Ping)	If you can't ping your router, the physical/connection layer is broken.
Packet Loss	High loss between PC and router can disrupt DHCP request/response packets.
Signal Strength	Weak Wi-Fi signal can cause intermittent DHCP failures.
DHCP Lease Time	How long your device keeps an IP. Expired lease with renewal failure causes APIPA.

Safe baseline router settings

Setting	Recommended
DHCP Server	Enabled. Start IP: 192.168.1.100, End IP: 192.168.1.200.
Wi-Fi Security	WPA2/WPA3 Personal (AES). Avoid WEP or TKIP-only.
Router Admin Password	Changed from default to a strong, unique password.
Firmware Updates	Check for updates every 6-12 months.

Mind map summary

APIPA 169.254.x.x Address (Windows)
|
|--- Root Cause: DHCP Failure
     |
     |--- Device-Side (One PC)
     |    |--- Software
     |    |    |--- Network Adapter Glitch (Disable/Re-enable)
     |    |    |--- Incorrect IP Settings (Set to Automatic)
     |    |    |--- Outdated Driver (Update/Reinstall)
     |    |    |--- Firewall/VPN Blocking (Disable Temporarily)
     |    |
     |    |--- Physical/Connection
     |         |--- Bad Wi-Fi Signal (Move closer/Forget network)
     |         |--- Faulty Ethernet Cable (Swap cable/port)
     |
     |--- Network-Side (All Devices)
          |--- Router DHCP Off (Enable in admin settings)
          |--- Router Overloaded (Restart router)
          |--- DHCP Scope Exhausted (Restart router to clear leases)
          |--- ISP Modem in Bad State (Restart modem & router)
     |
|--- Diagnostic Commands
     |--- ipconfig (See IP)
     |--- ipconfig /release & /renew (Force new IP)
     |--- ping 192.168.1.1 (Test router reachability)

Troubleshooting checklist

Device (Your Windows PC)

Run Network Troubleshooter
Release/Renew IP in Command Prompt
Disable/Enable Network Adapter
Verify "Obtain IP automatically" is on
Update Network Drivers
Temporarily disable firewall/antivirus

Router

Power cycle (unplug 60 seconds)
Login and ensure DHCP is ON
Check for firmware updates
Try connecting via Ethernet cable
Reset to factory defaults (last resort)

ISP & Environment

Is the problem on all devices?
Check modem lights for connectivity
Test with another Wi-Fi network if possible
Note any recent changes to network

When to escalate

Contacting ISP

If all devices on your network have no internet (or APIPA addresses) and a full router/modem restart didn't help. Also, if your modem's status lights indicate a downstream problem.

What to collect:

Modem model and light status.
Time the problem started.
Any outage messages from the ISP website/app.

Replacing Router

If the router's DHCP fails consistently, Wi-Fi randomly drops, or a factory reset doesn't restore functionality. Especially if the router is over 5 years old.

Asking IT Support

If you are on a workplace or university network. Do not change settings like static IPs without their guidance, as it may violate policy.

FAQ

What exactly is an APIPA address?

APIPA stands for Automatic Private IP Addressing. It's a Windows feature where the computer assigns itself an IP address in the range 169.254.0.1 to 169.254.255.254 when it cannot contact a DHCP server. This allows limited communication with other devices on the same local subnet but provides no internet access.

Is a 169.254.x.x address a security risk?

Not inherently. It simply means your computer is isolated from the main network and the internet. However, it could connect to other devices also using APIPA addresses on the same local link, which is generally not a concern in a home environment.

Can I use a static IP to fix this?

Yes, but it's a workaround, not a fix. You can manually assign an IP address in your router's range (e.g., 192.168.1.50), along with the correct subnet mask, gateway, and DNS. This bypasses the broken DHCP process. However, you must ensure the IP isn't already in use by another device.

Why does restarting the router often fix it?

Restarting clears the router's memory, terminates all existing connections, and restarts its internal DHCP service. This can resolve software glitches, clear a full DHCP lease table, and re-establish a clean state for handing out IP addresses.

Does this happen on macOS, Linux, or phones?

Similar concepts exist. macOS and Linux use a protocol called IPv4 Link-Local Addressing (zeroconf), which also assigns a 169.254.x.x address. Mobile phones (iOS/Android) typically show "No Internet" or "Saved" instead of displaying the APIPA address, but the underlying cause is the same: failure to get an IP from the network.

What does "DHCP server not found" mean?

This error means your computer broadcast a request for an IP address but received no offer from a DHCP server. This confirms the problem is between your PC and the router's DHCP function—either the service is off, a firewall is blocking the request, or the physical connection is broken.

Will a Windows reset fix this?

A full Windows reset (Network Reset option in Settings) will remove all network adapters and reset all networking components to default. It can fix deep-seated software corruption but is a last resort as you will need to re-enter Wi-Fi passwords and reconfigure VPNs.

Can antivirus software cause this?

Yes, some security suites include network protection features that can mistakenly block DHCP traffic. To test, temporarily disable your antivirus/firewall completely and try renewing your IP address. Remember to re-enable it afterward.

Sources and references

Microsoft Windows documentation on TCP/IP fundamentals and APIPA.
IEEE 802 standards overview for local area networking.
General DHCP protocol specification (RFC 2131).
Router vendor administration guides (TP-Link, Netgear, Asus, etc.) for DHCP configuration.
Windows networking command line reference (ipconfig, ping, netsh).
PC hardware and driver troubleshooting basics.
Home network security best practices from cybersecurity organizations.

Menu

How to fix APIPA 169 address issues on Windows

AI Assistant

Was this tool helpful?