If your USB Wi‑Fi adapter shows connected but does not get a usable IP address, the problem is usually DHCP, the saved Wi‑Fi profile, or the adapter state, not the radio link itself. Start by confirming the adapter is joined to the right Wi‑Fi network. Then renew the IP address or reconnect the network profile before you change drivers or reset the whole stack.
How to tell what failed
If the adapter is connected but the IP address still looks wrong, use this quick decision table first. It helps you separate a DHCP problem from a profile, driver, or router issue before you move on.
| What you see | Likely cause | Next check |
|---|---|---|
Connected, but 169.254.x.x or self-assigned address | DHCP did not hand out a lease | Renew DHCP, then rejoin the network |
| Other devices work, only this adapter fails | Adapter, driver, or saved profile | Test on a hotspot |
| No devices get an address | Router or DHCP service | Check router settings |
| It works after forget and rejoin | Stale saved profile | Keep the new profile and retest |
| It works on one network but not another | Router-side rule or DHCP issue | Check the affected router |
That is the decision tree I use in practice. Confirm the adapter is really joined. Try the least risky reversible fix first. Only then move to drivers or deeper resets.
Conclusion
If the adapter still does not get a usable IP after a renew, reconnect, and a hotspot test, stop treating it like a routine Wi‑Fi glitch. Check the driver, USB port, or adapter hardware next.
Frequently Asked Questions
Should I forget the Wi‑Fi network or reset the adapter first?
Forget the Wi‑Fi network first if the adapter can see Wi‑Fi but keeps failing to receive a lease. That clears stale profile data without changing drivers. Reset the adapter or the network stack only if the simple reconnect does not restore a normal private IP address.
What does a 169.254 address mean here?
A `169.254.x.x` address usually means the device did not receive a DHCP lease from the router, so it self-assigned an address instead. That points to a DHCP or profile problem more than a radio failure.
Sources
- Unable to get valid ip address for wireless or ethernet - Software & Applications - Spiceworks Community (community.spiceworks.com)