Wi-Fi Connected But No Internet: Real Fix (Windows)

Quick answer

Run ipconfig /all and look at the IPv4 address and DNS servers — if you see a 169.254.x.x address, it's DHCP. If the IP is fine but pings to 8.8.8.8 work and pings to google.com don't, it's DNS. Fix that layer, don't touch the router yet.

Windows shows the "Connected, no internet" or "No internet access" yellow triangle when the Wi-Fi link layer is up but Windows can't reach the internet. That's a big distinction. The radio associated, WPA2/WPA3 handshaked, and you got an IP — otherwise Windows would say "No connection." So the problem is one of three things: bad DNS resolution, a broken DHCP lease, or a captive portal / firewall dropping traffic. Nine times out of ten it's the first two. In 14 years of doing this, I've watched people factory-reset routers and reinstall Windows drivers for what turned out to be a stale DHCP lease from a comcast gateway that hadn't renewed in 3 days.

Here's the order I actually run these in. Don't skip around — the diagnostics in step 1 tell you which path to take.

Fix 1: Diagnose — figure out if it's DNS or DHCP

Open an elevated Command Prompt or PowerShell (right-click, Run as administrator) and run:

ipconfig /all

Find your Wi-Fi adapter in the output. Look at two lines:

IPv4 Address — if it starts with 169.254. that's APIPA. DHCP failed. Go to Fix 2.
DNS Servers — if it's blank or points to a weird IP you don't recognize (looking at you, old OpenDNS configs), go to Fix 3.

Then test connectivity to an IP vs a hostname:

ping 8.8.8.8
ping google.com

If 8.8.8.8 responds but google.com fails with "could not find host," that's DNS. 100%. If both fail, that's DHCP or the router itself. If both succeed and the browser still won't load — that's a proxy setting or a captive portal, jump to the alternative fixes.

Fix 2: DHCP is broken — release, renew, and reset

Run these in order in the elevated prompt:

ipconfig /release
ipconfig /renew
ipconfig /flushdns
ipconfig /registerdns
netsh winsock reset
netsh int ip reset

Reboot after the winsock and int ip reset — those two don't take effect until you do. The winsock reset is the one that fixes weird cases where a VPN client (Cisco AnyConnect, older NordVPN builds) corrupted the LSP stack and now nothing routes properly. This is a real thing and it happens more often than people admit.

If ipconfig /renew hangs for 30+ seconds and then hands you another 169.254 address, the router's DHCP scope is exhausted or its DHCP service is dead. Log into the router (192.168.1.1 or 192.168.0.1 typically), check the DHCP client list, and look at the lease time. Some ISP-provided gateways only hand out 15 leases by default and never clean them up. Yeah, really.

Fix 3: DNS is broken — swap the resolvers

If you confirmed DNS is the issue, the fastest fix is to stop using the router as a DNS relay. Go to Settings > Network & Internet > Wi-Fi > [your network] > DNS server assignment > Edit, or on Windows 10: Control Panel > Network and Sharing Center > Change adapter settings > right-click Wi-Fi > Properties > IPv4 > Properties.

Set these:

Primary: 1.1.1.1 (Cloudflare)
Alternate: 8.8.8.8 (Google)

I default to Cloudflare because it's usually the fastest resolver and it doesn't do the NXDOMAIN redirect garbage that some ISPs inject. Then flush:

ipconfig /flushdns

Reboot the adapter (disable/enable in adapter settings) or just reboot. You should be back online immediately. If Cloudflare itself is down — yes, it happens — swap to 9.9.9.9 (Quad9) which does DoH by default and blocks known malware domains.

Alternative fixes if those didn't work

Captive portal stuck state. Hotel/airport Wi-Fi often keeps you in a half-authenticated state. Open a browser and hit http://neverssl.com — plain HTTP, no HTTPS redirect weirdness. If you see the hotel login page, that's your problem.
Proxy settings hijacked. Go to Settings > Network > Proxy. If "Use a proxy server" is on and you didn't set it, that's malware or a leftover from some VPN tool. Turn it off.
Network Reset. Settings > Network > Advanced network settings > Network reset. This nukes all adapters, VPNs, and Wi-Fi profiles. You'll re-enter your Wi-Fi password. It's a sledgehammer, but it works when nothing else does.
Driver rollback. If this started after a Windows Update, open Device Manager, expand Network adapters, right-click the Wi-Fi NIC, Properties, Driver tab, and roll back. Intel AX200/AX201 cards had a bad driver in late 2023 that broke DNS after sleep.
Test another device. If your phone also has no internet on the same SSID, it's the router or the ISP. Call support, don't waste more time on the laptop.

Prevention

Two things. First, stop using the ISP router as your DNS — set Cloudflare or Quad9 directly on the router's WAN settings so every device on your network gets a fast resolver without you touching each machine. Second, if your router's DHCP lease time is under 24 hours and you have a lot of devices, raise it to 7 days. Short leases plus smart home junk that never releases them = exhausted scope = "connected, no internet" on a random Tuesday. I've seen this in three separate offices this year alone.