“Connected, no internet” is one of the more annoying Windows 11 messages because it’s half good news. The Wi-Fi part works — your PC is talking to the router fine — but nothing gets past that to the actual internet. Pages won’t load, apps can’t sync, and the network icon shows that little warning triangle.
The break is somewhere between your router and the wider internet, and there’s a short list of usual suspects: a bad IP lease, a DNS cache gone stale, a corrupted network stack, a flaky driver, or a problem at the router itself. This guide works through them in a sensible order — quick checks first, then the commands that fix most cases, then the deeper resets. Start at the top and stop when you’re back online.
First: is it the PC or the router?
Before touching any settings, answer one question — does anything else on the same Wi-Fi have internet? Grab your phone and check.
Narrow it down in 10 seconds
| Other devices are also offline | Problem is the router or ISP — restart the router first |
|---|---|
| Only this Windows 11 PC is offline | Problem is on the PC — work through the steps below |
| It just started after a VPN or update | Suspect that change first — VPN client or new driver |
This one check saves a lot of wasted effort. There’s no point resetting Windows networking if your whole household is offline — that’s a router or ISP issue, and the fix is restarting the router (pull power, wait 30 seconds, plug back in) or calling your provider.
The rest of this guide assumes only the Windows 11 PC is affected.
Quick wins: toggle the radio and reconnect
Sometimes the connection is just in a bad state. Two fast things before the command line:
- Turn Airplane mode on for a few seconds, then off. Click the network icon in the taskbar (or
Win + Afor Quick Settings). - Toggle Wi-Fi off and back on from the same panel.
- Forget the network and reconnect: Settings → Network & internet → Wi-Fi → Manage known networks → Forget, then rejoin with the password.
Step 1: Renew your IP address
A bad or expired DHCP lease leaves you connected to the router with an address that doesn’t route anywhere. Releasing and renewing it gets a fresh one.
Open Command Prompt or Windows Terminal as administrator and run:
ipconfig /release
ipconfig /renewThe screen will go quiet for a second on /release (you’ve dropped the address) and then list a new one on /renew. If you get a 169.254.x.x address back, that’s an APIPA address — the PC couldn’t reach a DHCP server, which points back at the router or the adapter rather than the wider internet.
Step 2: Flush the DNS cache
If the connection is fine but sites won’t resolve, stale DNS entries are a prime suspect. Windows caches lookups, and a bad cache makes good sites unreachable. Clear it:
ipconfig /flushdnsThen try a site again. A useful test here is to ping a raw IP versus a name — if ping 1.1.1.1 works but ping google.com fails, that’s DNS specifically, and Step 4 (changing your DNS server) is likely your real fix.
ping 1.1.1.1
ping google.comStep 3: Reset Winsock and the IP stack
If renewing and flushing didn’t do it, the network stack itself may be corrupted — often after a bad software uninstall, malware cleanup, or a VPN that left junk behind. Resetting Winsock and the TCP/IP stack returns them to a clean default.
Run these in an administrator terminal:
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsnetsh int tcp resetThese commands are targeted: they fix the network configuration without forgetting your saved Wi-Fi networks. That’s different from the full Network reset in Settings, which is heavier and covered at the end.
Step 4: Change your DNS server
If pinging an IP works but names don’t resolve even after a flush, your DNS server (usually your ISP’s) may be slow or broken. Switching to a public resolver is a clean test and often a permanent fix.
- Settings → Network & internet → Wi-Fi → Hardware properties.
- Next to DNS server assignment, click Edit.
- Switch to Manual, turn on IPv4, and enter a public DNS:
Common public DNS servers
| Cloudflare | 1.1.1.1 / 1.0.0.1 |
|---|---|
| 8.8.8.8 / 8.8.4.4 | |
| Quad9 | 9.9.9.9 / 149.112.112.112 |
You can also do it from the command line for the active adapter:
# Replace "Wi-Fi" with your adapter name if different
netsh interface ip set dns name="Wi-Fi" static 1.1.1.1
netsh interface ip add dns name="Wi-Fi" 1.0.0.1 index=2
ipconfig /flushdnsIf sites load after this, DNS was the culprit. You can leave the public resolver in place — it’s a reasonable default.
Step 5: Check the network driver
A wireless driver that’s outdated, buggy, or got mangled by a stuck Windows update can produce exactly this symptom. Two directions to try:
- Update it: Device Manager → Network adapters → right-click your Wi-Fi adapter → Update driver. Better yet, grab the latest from the laptop or adapter maker’s site rather than relying on the generic one.
- Roll it back: if the trouble started right after an update, open the adapter’s Properties → Driver tab → Roll Back Driver to return to the version that worked.
Win + X → Device Manager → Network adaptersStep 6: Restart the router and check the basics
Even when only one PC seems affected, a quick router restart rules out a confused DHCP table or a stale lease on the router side. Power it off, wait 30 seconds, power it back on, and let it fully come up before testing.
While you’re there, run through the easy-to-miss items:
Don't overlook these
- VPN client still running or half-disconnected — close it fully and retest
- Airplane mode fully off, physical wireless switch/Fn key in the right position
- Date and time correct (a wrong clock breaks secure connections)
- Proxy settings off if you didn't set them: Settings → Network & internet → Proxy
- Antivirus/firewall not blocking — test by briefly disabling third-party firewall
- Router firmware not mid-update or the router not overheating
The VPN one catches people out regularly. A client that dropped badly can leave a virtual adapter or leftover settings that block normal traffic — disconnect, close it completely, and test before assuming Windows is at fault.
Last resort: full Network reset
If nothing above works, Windows 11 has a nuclear option that reinstalls every network adapter and returns all networking to defaults. If you suspect deeper system file corruption rather than just networking, repairing Windows with DISM and SFC is worth a pass first.
- Settings → Network & internet → Advanced network settings → Network reset.
- Click Reset now and let the PC restart.
Settings → Network & internet → Advanced network settings → Network resetWrapping up
“Connected, no internet” almost always comes down to a handful of causes, so work the order: confirm it’s the PC and not the router, renew your IP, flush DNS, then reset Winsock and the IP stack and reboot. If names won’t resolve but raw IPs ping fine, switch to a public DNS server. If the trouble tracks to a recent update, look at the wireless driver, and don’t forget the simple culprits — a stuck Airplane mode or a VPN that didn’t let go cleanly.
Save the full Network reset for last, since it forgets your saved Wi-Fi. Most of the time you’ll be back online well before then, and the fix will be one of the first few steps rather than the dramatic one.
