Photo by Ed Hardie on Unsplash

You're sitting there, WiFi icon shows full bars, it says "Connected" right there in the taskbar, and yet absolutely nothing loads. Chrome times out. Ping fails. You disconnect and reconnect and nothing changes. The little yellow triangle appears and Windows cheerfully informs you: No Internet, Secured. Secured. Great. Super helpful, Windows.

I've seen this happen after a Windows Update, after waking from sleep, after absolutely nothing — just the machine deciding today is the day it forgets how the internet works. The thing is, your router is fine. Your phone is on the same WiFi and streaming video without a problem. This is purely Windows being confused about its own network state, and honestly it happens more than Microsoft would probably like to admit.

What the Error Looks Like

In the system tray, the WiFi icon has a yellow exclamation mark. If you click it, you'll see something like this:

No Internet, Secured
Connected to [Your Network Name]
No internet access

And if you run a quick ping test in Command Prompt:

ping google.com

Ping request could not find host google.com. Please check the name and try again.

Or sometimes:

Request timed out.
Request timed out.
Request timed out.

The IP address is assigned. The connection shows as active. Windows just... can't get out.

Photo by Dreamlike Street on Unsplash

Why This Actually Happens

There are a few culprits, and they're different enough that one fix won't always work for everyone. The most common ones I've run into personally are DNS resolution breaking completely, the DHCP client service getting into a weird state, or Windows' TCP/IP stack getting corrupted (usually after an update or a hard shutdown).

Windows also does this thing where it runs a connectivity check to www.msftconnecttest.com in the background. If that request fails — even if your actual internet is fine — it flags the connection as no internet. Which is an absolutely maddening design choice, but here we are.

Photo by Ed Hardie on Unsplash

Fix 1: Flush DNS and Reset the Network Stack

This is always where I start. Open Command Prompt as Administrator — right-click the Start button, hit "Terminal (Admin)" or "Command Prompt (Admin)" depending on your Windows version — and run these in order:

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

After that, restart your machine. Don't skip the restart. I know it's annoying. Do it anyway.

What this does is reset the Winsock catalog (basically Windows' socket layer), wipe the IP configuration, clear out any stale DNS cache, and request a fresh IP from your router. Half the time this is all it takes. The DNS flush alone has saved me on machines that were in this broken state for days.

Fix 2: Restart the DHCP Client and DNS Client Services

If the first fix didn't work, this is my next move. Sometimes the services responsible for getting and renewing your IP address just quietly die and Windows doesn't even notice.

Run this in an elevated Command Prompt:

net stop dhcp
net start dhcp
net stop dnscache
net start dnscache

Then try:

ipconfig /release
ipconfig /renew

You can also do this through Services (press Win + R, type services.msc). Find "DHCP Client" and "DNS Client" in the list, right-click each one, and hit Restart. Same result, just more clicking.

I've had situations where the DHCP client service was set to Manual instead of Automatic — usually after a botched update — and it just wasn't starting on boot. Check that while you're in there.

Fix 3: Change Your DNS Servers Manually

Here's the thing — sometimes your ISP's DNS servers are just having a bad day, and Windows can't resolve any hostnames because of it. Your connection is technically working at the IP level, but DNS is dead.

Switch to Google's DNS or Cloudflare's. Go to:

Settings > Network & Internet > WiFi > [Your Network Name] > Hardware Properties > DNS server assignment > Edit

Set it to Manual, enable IPv4, and use:

Preferred DNS: 8.8.8.8
Alternate DNS: 8.8.4.4

Or if you want Cloudflare:

Preferred DNS: 1.1.1.1
Alternate DNS: 1.0.0.1

Save it, disconnect from WiFi, reconnect. If this was a DNS issue, you'll know immediately because everything starts working. I was surprised by how often this is the actual fix on corporate networks especially, where the internal DNS server is flaky.

If None of That Worked

At this point I'd look at your WiFi adapter driver. Seriously. Go to Device Manager (Win + X, then Device Manager), expand "Network Adapters," right-click your WiFi adapter, and hit "Update driver." If Windows finds nothing new, go directly to your laptop manufacturer's site and download the driver manually.

Also worth trying: disable and re-enable the adapter in Device Manager. Right-click it, Disable, wait five seconds, Enable. Dumb fix. Works sometimes. I can't explain it.

And if you're on a laptop and this only happens after sleep or hibernate, go to Device Manager, right-click your WiFi adapter, Properties, Power Management tab, and uncheck "Allow the computer to turn off this device to save power." Windows loves to do this and then fail to properly wake the adapter back up.

You Should Be Back Online Now

Honestly, the netsh reset plus a reboot clears this up probably 70% of the time. The rest is usually DNS or a flaky driver. It's one of those errors that looks scary because Windows gives you zero useful information about what actually broke, but the fix is almost always pretty mundane once you dig in.

If you're still stuck after all of this, run the built-in network troubleshooter — I know, I know, it's usually useless — but specifically look at what it reports, not what it fixes. Sometimes it'll name the exact thing that's broken and that gives you a real search term to go look up. That's about all the troubleshooter is good for in my experience.

Good luck. You'll get there.