# Networking: IPv4 address 169.254.x.x (Autoconfiguration / APIPA) — the PC couldn't get an address from DHCP

**Code:** `169.254.x.x self-assigned IP (DHCP failed)` · **Category:** Networking · **Seen on:** Windows, Networking

With no DHCP answer, the computer gave itself a link-local 169.254.x.x address, which only works on the local segment.

## Meaning

A 169.254 address means the DHCP request got no usable reply. Check cable/Wi-Fi, DHCP server health and scope, VLAN and DHCP relay/helper, then `ipconfig /release` and `/renew`. Power-cycle the router if it is a home network.

## Common causes

- DHCP server down or scope exhausted
- Cable/Wi-Fi problem between client and server
- Wrong VLAN or missing DHCP relay (ip helper-address)
- Firewall or switch DHCP snooping blocking replies
- Router needs a restart

## Quick fix

1. Renew: `ipconfig /release` then `ipconfig /renew`
2. Check the DHCP server and scope
3. Verify the VLAN and DHCP relay configuration

## Detailed fix by platform

### Windows

1. 

```powershell
ipconfig /release
ipconfig /renew
ipconfig /all | findstr /i "autoconfiguration dhcp"
```


## How to diagnose

1. **Address** — 169.254.x.x?
2. **DHCP server** — Reachable, free leases?
3. **VLAN/relay** — Correct?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/networking/dhcp-apipa-169-254-self-assigned)