This usually means Windows joined the Wi‑Fi network, but DHCP did not hand your Realtek adapter a usable IPv4 address. The quickest safe fix is to check for a fallback 169.254.x.x address, renew the lease, and then move on to adapter or router changes. If that still fails, the cause is usually a Windows network setting, the Realtek driver, or the router’s DHCP service.
What this error usually means
The Wi‑Fi link is up, but address assignment failed. Windows asks the router’s DHCP server for an IP lease. If that step breaks, it may self-assign a 169.254.x.x address through APIPA instead of getting a normal private address.
The first thing to check is not the signal bars. Open the adapter status or ipconfig output and look for a 169.254.x.x address, no default gateway, or a lease that looks stuck or expired. If you see 169.254.x.x, that strongly points to DHCP failure rather than a simple Wi‑Fi signal problem.
Before you start
- Make sure you’re checking the IPv4 address, not just the Wi‑Fi connection icon.
- Have access to the router only if you may need to reboot it or check DHCP settings.
- If this is a work, school, or shared network, stop before changing router settings you don’t control.
- If the laptop has ever worked on the same network, that helps separate a device problem from a network problem.
- If the adapter shows a static IP instead of automatic addressing, note that before changing anything so you can undo it later.
If the machine fails on both Wi‑Fi and Ethernet, or it fails on one adapter and also on a USB Wi‑Fi adapter, the issue is less likely to be one bad radio and more likely to be Windows networking or DHCP itself.
Is the problem on this laptop or the router?
Split the problem before you change much. If other devices get online on the same Wi‑Fi, the router is probably handing out addresses and the fault is more likely this laptop or its Realtek setup. If this laptop fails on one network but works on another, the adapter is usually fine and the issue sits with that router or its DHCP settings.
A common case is a laptop that fails on home Wi‑Fi but works on a phone hotspot. That points away from the adapter hardware and toward the router, its DHCP pool, or a bad reservation. If the same laptop also fails on Ethernet or another wireless adapter, the issue is more likely Windows network settings or a broken network stack, not just the Realtek card.
The safest fixes to try first
Start with the smallest reversible actions. Don’t jump straight to driver reinstalls or a reset unless the simple lease checks fail, because those can blur the cause you are trying to find.
- Disconnect from the Wi‑Fi network, then connect again. If the lease was just stale, this is sometimes enough.
Renew the IP lease.
Command Prompt ipconfig /release ipconfig /renewIf the adapter gets a valid private address after this, the problem was a stuck lease or a slow DHCP handoff.
Restart the wireless adapter. You can do that in Network Connections, Device Manager, or with PowerShell. A disable/enable cycle can clear a stale state without changing your router or profile. Microsoft’s guidance for this kind of failure also includes disabling and re-enabling the wireless adapter.
PowerShell (run as Administrator) Get-NetAdapter -Name "Wi-Fi" | Disable-NetAdapter -Confirm:$false Start-Sleep -Seconds 3 Get-NetAdapter -Name "Wi-Fi" | Enable-NetAdapterReplace
Wi‑Fiwith your adapter name if it is different.
- Reboot the router only if the lease still fails. Do this after you have checked the laptop side, not before. A router reboot can help if DHCP is slow, the pool is stuck, or the router needs a clean restart, but it also wipes useful clues about what was failing.
If the adapter still comes back with 169.254.x.x after ipconfig /renew, stop treating it like a simple Wi‑Fi glitch. That usually means DHCP is still failing, so the next place to look is the router’s DHCP service, a bad reservation, or a full address pool.
Realtek and Windows settings that can block an IP lease
If the easy lease steps do not work, the next suspects are local settings that interfere with DHCP. Start with the Realtek driver itself. A corrupted or mismatched driver can make Windows look connected while the adapter never completes address negotiation.
Power saving is another frequent culprit. Some Realtek adapters and Windows power plans can put the card into a state where it wakes poorly after sleep or after a router reboot. If the failure appears after waking the laptop, that timing is a strong clue.
Also check for static IP mistakes. If someone manually set IPv4 values on the adapter, a bad address, subnet mask, gateway, or DNS entry can make DHCP look broken when the adapter is really fixed to the wrong settings. In adapter properties, make sure IPv4 is set to obtain an address automatically unless your network admin told you otherwise.
If the error persists on more than one network adapter, Windows networking itself may be stuck. Cases like this are where ipconfig /release, ipconfig /renew, and broader stack repair steps are often used, because the failure can come from corrupted IP configuration rather than the Wi‑Fi radio alone. When a machine fails on both wireless and Ethernet, that is a stronger sign of a system-wide network issue than a single Realtek card problem.
On the router side, check the DHCP service itself. The common failure points are DHCP being turned off, a bad reservation for this laptop’s MAC address, or the address pool being full. If the router is set to hand out addresses only in a narrow range, one extra device can be enough to push it over the edge. If you don’t manage that router, hand this part to the person who does.
How to confirm it’s fixed and when to escalate
The fix is real only if the adapter gets a normal private IP address again. You should see an address in your home or office range, plus a default gateway and DNS servers, and you should be able to reach the internet without the fallback 169.254.x.x address.
A quick check is enough: if the address is valid, the gateway is present, and DNS servers are listed, try a website or another known host. If the address looks right but name lookups still fail, the IP problem may be gone and you are dealing with a separate DNS issue.
Stop and escalate if any of these are true:
- The laptop only fails on one network and you do not control the router.
- The router’s DHCP settings need admin access.
- The laptop fails on every network, including a hotspot.
- Both Wi‑Fi and Ethernet show the same DHCP failure.
- The adapter keeps returning 169.254.x.x after renew, reconnect, and a router reboot.
At that point, the next step is router admin help, deeper Windows network repair, or hardware testing rather than repeating the same quick fixes.
Frequently Asked Questions
Should I reinstall the Realtek driver first?
No. Reinstalling the driver is usually later in the process, after you’ve checked whether the laptop gets a 169.254.x.x address, tried release and renew, and confirmed the problem follows the laptop rather than the router. That keeps you from changing the one thing that would have shown where the fault really was.
What does a 169.254.x.x address mean?
It means Windows did not get a lease from DHCP and fell back to APIPA, which is a self-assigned address used when normal address assignment fails. If you see that address, focus on DHCP, adapter settings, and router-side address allocation instead of treating it like a signal-strength issue.
Sources
- How to Fix 'WiFi Doesn't Have a Valid IP Configuration' on Windows (oneuptime.com)
- Unable to get valid ip address for wireless or ethernet - Software & Applications - Spiceworks Community (community.spiceworks.com)