If one PC on a Wi‑Fi 7 router stays connected to the network name but never gets an IP address, the problem is usually DHCP, a router rule tied to that device, or a Windows-side setting on that PC. The quickest fixes are on the PC first: renew the lease, forget and rejoin the network, and check for a static IP, VPN adapter, or broken network stack. If that does not help, check MAC filtering, access control, reservations, and lease conflicts on the router.
What you’ll usually see
The router works for other devices, but one PC is stuck with no valid address, a self-assigned address, or repeated connect-and-fail behavior. Often the Wi‑Fi link is close enough for the PC to see the SSID and associate, but DHCP fails when it tries to hand out an IP.
That difference matters. If the PC never truly joins the Wi‑Fi, you’re dealing with a different problem, usually security mode, driver compatibility, or signal quality. If it joins but cannot get an IP, focus on the PC, the router’s device rules, or a lease conflict instead of Wi‑Fi 7 as a label.
Before you start
Work from the safest checks first and keep router changes for later. You do not need to change every setting at once, and that usually makes it harder to see what fixed it.
- Have access to the problem PC and the router’s admin page.
- If the PC has a known-good Wi‑Fi profile from before the problem started, remove and recreate it rather than stacking new fixes on top of it.
- If you use a VPN client or network filter on that PC, be ready to disable it briefly while you test.
- If the router has a current firmware update or vendor note about DHCP or compatibility, check the official support page for your exact model before changing advanced settings. Firmware details change, so don’t rely on an old version number.
Stop and back out of changes one at a time. If you change several things at once, you can’t tell whether the fix came from the PC, the router, or a lease refresh.
Fix the PC first
Start with the problem PC, because those changes are reversible and they often clear the issue without touching the router.
- Check whether the adapter is set to use a manual address. If it is, switch the PC back to automatic IP and automatic DNS. A static address can sit outside the router’s DHCP pool or collide with an existing lease.
- Turn off any VPN adapter or network filter for the test. Some VPN clients create virtual adapters that interfere with normal address assignment or route selection on Windows.
- Renew the lease.
ipconfig /release
ipconfig /renewIf the PC gets a fresh IP after that, the DHCP path is working again. If the command fails or the PC gets the same broken state right away, keep going.
- Forget the Wi‑Fi network and join it again. This clears a bad saved profile, including old security details, stale credentials, or a saved MAC identity that no longer matches what the router expects.
- Check whether randomized MAC is enabled for that Wi‑Fi network. If the router has a rule tied to the old hardware address, a randomized MAC can make the PC look like a different device every time it connects. Turn it off for that SSID and test again if you suspect a mismatch.
- Update or roll back the Wi‑Fi adapter driver if the problem began after a driver change. A driver issue can show up as a PC that sees the network but never completes DHCP.
If the PC starts getting an address after one of these steps, stop there. If it still connects but won’t get an IP, move to the router and lease checks.
Check router rules and DHCP behavior
A router can look healthy because every other device renews normally while one PC is being blocked by a setting aimed at that device. The usual culprits are MAC filtering, access control, a reservation that no longer matches, or a DHCP pool that is too tight.
- Check MAC filtering and access control. Make sure the problem PC is not blocked by its MAC address. This matters even more if the PC uses a randomized MAC, because the router may still be matching the old address while the PC presents a new one.
- Review DHCP reservations. A reservation ties a specific MAC address to a specific IP. If the reservation points to the wrong MAC, or the PC’s MAC changed, the router may hand out the wrong address or fail to match the device. ASUS notes that a manually assigned IP needs to be inside the DHCP pool and that the rule should appear in the manual assign list after you apply it. On many routers, the same rule applies: the reserved address has to fit the pool and match the right device.
- Check whether the DHCP pool is full or cluttered with stale leases. If the pool is exhausted, the router may still serve existing devices but fail when this one PC asks for a new lease. A stale lease can also keep the router from giving the same PC a clean address until the old entry ages out or is cleared.
- Look for signs of an IP conflict. If the PC seems to get an address but then drops off the network, another device may already be using that IP. Microsoft Q&A describes a case where devices appeared to compete for the same address, which is the kind of pattern you want to look for here.
If you recently changed filtering, reservations, or access rules, undo one change at a time. That gives you a clean rollback path if the PC starts working again.
When the PC still won’t get an IP
If the PC still fails after the easy client checks and the router-side checks, reset the Windows network stack, then test the adapter and security mode.
- Reset the Windows stack.
netsh winsock reset
netsh int ip resetRestart the PC after you run those commands. If the PC starts getting an IP again after the restart, the stack was the problem.
- Disable and re-enable the network adapter, or reset it from Windows Settings if that’s easier on your version of Windows. This clears a stuck driver state without changing router policy.
- Try the same PC on another band or with a simpler security setting if your router supports it. If the PC only fails on one band steering setup or on a WPA3-only setting, that points to a compatibility issue between the adapter, the driver, and the router configuration rather than a Wi‑Fi 7 defect itself.
- Check the router’s current firmware notes on the official support page for your exact model. If the manufacturer has a DHCP or compatibility fix, use that guidance before changing deeper settings. The exact release you should use can change, so verify it against the current official source.
If the PC works on a different network but not on this router, the issue is more likely a device-specific compatibility or security mismatch. If it fails on every network, the problem is local to Windows or the adapter.
How to verify the fix
After each change, confirm that the PC gets a normal IP address, gateway, and DNS settings and can stay connected after a reboot. If the address returns after a renew, forget-and-rejoin, or adapter reset, you’ve confirmed that the fault was in the client side or in the lease path.
If the PC only works after you disable randomized MAC or change the security mode, keep the setting that works and document it for that network. If it only works after you remove a reservation or access-control rule, rebuild that rule carefully with the current MAC address before you call it done.
Conclusion
If the PC still won’t take an IP after those checks, compare that adapter against a different PC or another Wi‑Fi network before you replace hardware. That tells you whether you’re dealing with a bad lease path, a router rule, or a PC-side compatibility problem.
Frequently Asked Questions
How do I know whether the PC is failing to join Wi‑Fi or only failing at DHCP?
If the PC can see the SSID and connect to it but shows no valid IP address or can’t reach the network, the association step worked and DHCP failed. If it never joins the SSID, focus on security mode, signal quality, or the Wi‑Fi driver first.
Should I use a static IP to fix this?
Only as a test, not as the first fix. A static IP can work around DHCP, but it can also create conflicts if you pick an address inside the router’s active pool. In most cases, it’s better to return the PC to automatic addressing and fix the cause.
Why would randomized MAC break one PC and not the others?
Because the router may have a reservation or access-control rule tied to the older MAC address. If the PC presents a different randomized MAC on that SSID, the router can treat it as a different device or block it under policy. Turning off randomized MAC for that network often clears the mismatch.