Last updated: September 2026
Most “connected, no internet” cases on Windows 11 are DNS, Winsock, or router DHCP problems — not a dead Wi‑Fi chip. I’ve chased this on my own laptop more times than I care to count: the Wi‑Fi icon looks fine, the network name shows as Connected, and yet Chrome just spins. Random restarts sometimes help for an hour. A staged checklist helps for good.
I’m Rohit Srivastav. I write consumer tech how‑tos for Hiektec.in after years of fixing the same Windows, Android, and Wi‑Fi messes people hit at home. This guide walks through the exact order I use when Windows 11 says you’re online and the web says otherwise.
—
What “connected but no internet” usually means
Windows can associate with your access point (SSID, password, radio link) and still fail higher up the stack. You get a connection to the router. You do not get a working path to DNS or the wider internet.
Common symptoms:
Wi‑Fi status: Connected, no internet (or the globe icon with a warning)
Browser pages fail; some apps that cache data still open
Ping to 8.8.8.8 might work while website names do not (classic DNS)
Or nothing responds at all (IP/DHCP/gateway)
When to stop and call hardware help: if the Wi‑Fi adapter vanishes from Device Manager after every reboot, if the NIC gets burning hot, or if every other device on the same router is fine while this PC never gets an IP — that’s adapter or motherboard territory, not another software tweak.
—
Quick triage (2 minutes)
Do these before you touch DNS or reset anything.
1. Confirm it’s only this PC
Open the same website on your phone (on the same Wi‑Fi, not mobile data). If the phone fails too, skip PC‑only steps and jump to Router and ISP checks. If the phone works, stay on the PC path.
2. Note the exact status text
Go to Settings → Network & internet → Wi‑Fi. Click your network. Read Properties: IPv4 address, DNS, Gateway. Screenshot or write them down. You’ll need them if support asks later.
3. Toggle airplane mode once
Settings → Network & internet → Airplane mode — turn it on, wait 10 seconds, turn it off. Reconnect to Wi‑Fi. Cheap, sometimes enough after sleep/hibernate glitches.
If you’re still stuck, work top to bottom below. Don’t skip ahead to “reset network” until DNS and IP checks fail — resets wipe saved Wi‑Fi passwords and VPN profiles.
—
Fix 1: Flush DNS and renew the IP (easiest real fix)
Windows caches DNS answers. A bad cache entry makes “Connected” look true while every hostname fails.
Right‑click Start → Terminal (Admin) or Windows Terminal (Admin).
Run these one at a time:
“`text
ipconfig /flushdns
ipconfig /release
ipconfig /renew
“`
Then:
“`text
nslookup google.com
“`
You want a real answer with an IP, not a timeout. If nslookup fails but you still have an IPv4 address under Wi‑Fi properties, you’re looking at DNS. Jump to Fix 2.
If /renew fails with “unable to contact DHCP server,” the PC never got a lease. Jump to Fix 4 and the router section.
Why this comes first: I’ve fixed more “no internet” evenings with flush + renew than with driver reinstalls. It’s fast and reversible.
—
Fix 2: Set DNS to known public resolvers (temporary test)
Automatic DNS from the router sometimes points at a dead ISP resolver or a misconfigured local address.
Settings → Network & internet → Wi‑Fi → your network name → DNS server assignment → Edit.
Set to Manual.
Turn IPv4 on.
Preferred DNS: 1.1.1.1
Alternate DNS: 1.0.0.1
(Cloudflare. Google’s 8.8.8.8 / 8.8.4.4 also work for a test.)
Save. Open a new browser tab to a site you don’t have cached.
Leave this as a temporary test. If websites load, you proved DNS was the bottleneck. You can keep public DNS or fix the router’s DNS later. If nothing changes, set DNS back to Automatic before you continue so you don’t stack weird configs.
IPv6 note: if IPv6 DNS is enabled and flaky on your ISP, try turning IPv6 DNS off in the same Edit screen for the test, or disable IPv6 on the adapter briefly (see Fix 6). Don’t leave IPv6 disabled forever unless you know your network doesn’t need it.
—
Fix 3: Run Windows’ network troubleshooter — then ignore half of it
Yes, the built‑in tool. Use it for the log and the one‑click Winsock/adapter resets it sometimes applies; don’t treat the English summary as gospel.
Settings → System → Troubleshoot → Other troubleshooters.
Run Network Adapter and Internet Connections.
Apply recommended fixes if it offers a reset of the adapter or Winsock.
After it finishes, reboot once if it changed anything. Retest. If you’re still down, keep going — the troubleshooter often reports “gateway not available” without fixing DHCP upstream.
—
Fix 4: Check IP, DHCP, and the default gateway
Open Settings → Network & internet → Wi‑Fi → your network → Properties.
Healthy home setup usually looks like:
IPv4 address in a private range (192.168.x.x, 10.x.x.x, or 172.16–31.x.x)
IPv4 DNS servers populated
Default gateway matching your router (often .1 on the same subnet)
IPv4 connectivity: Internet (when things work)
Red flags:
| What you see | Likely cause |
| — | — |
| 169.254.x.x address | No DHCP lease (APIPA). Router/DHCP or wireless association issue |
| No gateway | Bad DHCP options or static IP misconfigured |
| Valid IP, no internet | DNS, firewall, proxy, or ISP outage |
| Metered / limited | Policy or mobile hotspot limits — less common on home Wi‑Fi |
Clear a bad static IP
Settings → Network & internet → Wi‑Fi → your network → IP assignment → Edit.
Choose Automatic (DHCP) unless you *intentionally* use static settings.
Save, disconnect, reconnect.
If someone set a static IP for an old office network, Windows will happily “connect” to Wi‑Fi and go nowhere useful.
Ping the gateway
In an elevated Terminal:
“`text
ipconfig
“`
Note the Default Gateway. Then:
“`text
ping GATEWAY_IP_HERE
“`
No replies: you’re not talking to the router (wireless, AP isolation, or router LAN issue). Replies but no websites: DNS or upstream WAN.
—
Fix 5: Reset Winsock and the TCP/IP stack
Corrupt Winsock catalogs show up after VPN clients, “optimizer” tools, and half‑removed security suites. The Wi‑Fi radio is fine; sockets are not.
In Terminal (Admin):
“`text
netsh winsock reset
netsh int ip reset
“`
Restart Windows when prompted. Rejoin Wi‑Fi. You’ll need the Wi‑Fi password again only if you also reset the network stack more aggressively later — Winsock reset alone usually keeps profiles.
I use this after DNS and DHCP look correct but browsers still fail while ping 8.8.8.8 works (or vice versa). It’s heavier than flushdns; do it before full network reset.
—
Fix 6: Proxy, VPN, and “smart” security layers
Proxy
Settings → Network & internet → Proxy.
Under Automatic proxy setup, turn Automatically detect settings on unless your workplace requires a PAC file.
Under Manual proxy setup, ensure Use a proxy server is Off for home use.
A leftover manual proxy from college or office VPN software will give you Connected + silence.
VPN
Disconnect any VPN. Quit the app from the system tray, not just the “disconnect” toggle. Retest. If internet returns, update or reinstall the VPN — don’t keep stacking reconnects. Some VPN kill‑switches block all traffic when the tunnel drops; that’s intentional, but it looks identical to “no internet.”
Third‑party firewall / suite
If you installed a full antivirus suite with its own firewall, temporarily disable *network protection* (not the whole PC forever) and retest. If that restores access, add an exception for your browser or repair the suite. Windows Firewall alone rarely causes this on a stock install.
—
Fix 7: Forget the network and reconnect
Stale credentials or a bad profile after a router change (new password, WPA3 transition) cause long hangs that still show Connected.
Settings → Network & internet → Wi‑Fi → Manage known networks.
Select the network → Forget.
Reboot the PC (optional but helps stubborn drivers).
Rejoin; enter the current Wi‑Fi password.
Also forget guest networks you joined “just once.” Windows sometimes prefers a weak remembered SSID.
—
Fix 8: Update or reinstall the Wi‑Fi driver (carefully)
Drivers matter when sleep/resume breaks Wi‑Fi or after a big Windows feature update. They are not the first place to start for a sudden DNS failure on an otherwise healthy adapter.
Right‑click Start → Device Manager.
Expand Network adapters.
Right‑click your Wi‑Fi adapter (Intel, Realtek, MediaTek, etc.) → Update driver → Search automatically.
If that finds nothing useful, open the PC or motherboard maker’s support site (or Intel Driver & Support Assistant for Intel Wi‑Fi) and install the matching Windows 11 package.
Clean reinstall
Device Manager → Wi‑Fi adapter → Uninstall device.
If shown, check Attempt to remove the driver only if you already have the installer downloaded.
Restart. Windows often reinstalls a basic driver; then install the vendor package.
When to stop: if the adapter disappears, shows a yellow bang that returns after every clean install, or Wi‑Fi vanishes from Settings entirely, get local hardware service. Don’t keep flashing random drivers from unofficial sites — AdSense‑safe tip and life tip: stick to OEM/vendor packages.
Power management gotcha: Device Manager → Wi‑Fi adapter → Properties → Power Management → uncheck Allow the computer to turn off this device to save power. Laptop users hit this after lid‑close cycles.
—
Fix 9: Network reset (last Windows‑side nuclear option)
This removes all network adapters’ software config and returns networking to defaults. You’ll re‑enter Wi‑Fi passwords and reconfigure VPN.
Settings → Network & internet → Advanced network settings → Network reset.
Reset now. Confirm.
PC restarts after a short countdown.
Sign in, reconnect Wi‑Fi, retest.
Do this after Winsock reset and driver work, not before. I’ve seen people network‑reset on day one, lose every saved network, and still have a dead router WAN port.
—
Router and ISP checks
If the phone failed on the same Wi‑Fi, or the PC never gets a DHCP lease, work here.
Power‑cycle the right way
Unplug the modem/ONT and the router (or the combo box).
Wait a full 60 seconds — not 5.
Power the modem first; wait until sync lights settle.
Power the router; wait 2 minutes.
Retest phone, then PC.
Router admin quick look
Log into the router (often 192.168.0.1 or 192.168.1.1 — check the sticker). Confirm:
WAN status is up
DHCP server is enabled on LAN
You’re not at the DHCP pool limit (dozens of IoT devices can exhaust a tiny pool)
MAC filtering / access control isn’t blocking the PC
Parental controls or “pause internet” schedules aren’t active for your device
Band / isolation issues
Try the other band (2.4 GHz vs 5 GHz) if your router uses separate SSIDs. Guest networks often isolate clients from LAN and sometimes break oddly with certain Windows builds — use the main SSID for the PC while testing.
ISP outage
Check your provider’s status page or app from mobile data. If the neighborhood is down, no amount of Winsock poetry helps. Document the outage time if you need a support ticket later.
—
Optional: Command‑line health snapshot
When you’re comparing before/after or sending details to a tech‑savvy friend, capture:
“`text
ipconfig /all
netsh wlan show interfaces
ping 1.1.1.1
ping google.com
nslookup google.com
“`
Interpretation in plain language:
Ping IP works, ping name fails → DNS
Both fail, gateway ping fails → local link / router
Gateway works, public IP ping fails → ISP / WAN
All pings work, browser fails → proxy, HTTPS inspection, or browser extension (try InPrivate / another browser)
I don’t paste full ipconfig dumps onto public forums with my public IP visible — redact if you share screenshots.
—
What I don’t recommend for this problem
Downloading “PC repair” one‑click suites from random ads
Registry cleaners sold as internet fixes
Third‑party DNS “boosters” that hijack your resolver
Cracked VPN or “free premium Wi‑Fi” tools (unsafe and off‑limits for this site)
Stick to Settings paths, official drivers, and router firmware from the manufacturer.
—
A practical order you can print
Phone test on same Wi‑Fi
Airplane mode toggle
ipconfig /flushdns + release/renew
Manual DNS test (1.1.1.1)
Troubleshooter
Confirm DHCP IP (not 169.254.x.x) and gateway ping
Proxy/VPN off
Winsock + netsh int ip reset, reboot
Forget network, reconnect
Driver update / power management unchecked
Network reset
Router power‑cycle + DHCP/WAN check
ISP status / hardware service if adapter is unstable
Most home cases die at steps 3–8. Hardware is the exception, not the default story.
—
FAQ
Why does Windows say Connected if there’s no internet?
Because “Connected” often means associated with the access point. Internet access is a separate check (DNS + routing + WAN). Windows shows a warning globe when that second check fails.
Does restarting the PC fix Wi‑Fi connected but no internet?
Sometimes, briefly — it clears transient driver and DHCP state. If the problem returns daily, fix DNS/DHCP/Winsock or the router instead of living on reboots.
Is this a Windows 11 bug?
Feature updates occasionally break specific Wi‑Fi drivers. If internet died the morning after an update, check Device Manager and OEM drivers first. Many “bugs” are still local DNS or ISP events that only feel like an OS issue.
Should I change my DNS permanently?
If public DNS fixed you and your ISP’s resolver is unreliable, keeping 1.1.1.1 / 1.0.0.1 or 8.8.8.8 / 8.8.4.4 is fine for most home users. Prefer setting it on the router so every device benefits, unless you have a reason to keep ISP DNS (captive portals, some ISP TV boxes).
Can a VPN cause connected but no internet?
Yes. Kill‑switches and broken tunnels block traffic on purpose when the VPN drops. Disconnect fully and retest before deeper Windows resets.
When should I replace the Wi‑Fi adapter?
When the device disappears, errors persist after clean OEM drivers, or wired Ethernet works while Wi‑Fi never obtains a lease across multiple routers. USB Wi‑Fi adapters are a cheap diagnostic step before motherboard service.
Will Network Reset delete my files?
No. It resets network configuration, not your documents. You will lose saved Wi‑Fi passwords and some VPN/adapter customizations.
I get an IP but only some sites load. Is that the same issue?
Partially. Start with DNS flush and public DNS. Also try another browser and disable extensions. Intermittent site failures can be MTU/VPN related; still start with the checklist above.
—
Final take
Treat “Wi‑Fi connected but no internet” on Windows 11 as a stack problem: radio link first, then IP, then DNS, then OS socket layer, then router WAN. The staged checklist beats random restarts because each step proves or eliminates a layer. If you reach hardware territory — vanishing adapters, heat, zero lease on every network — stop tweaking and get the NIC checked.
I keep this guide updated as Windows 11 Settings labels shift. Last updated: September 2026. If a menu path moved on your build, search Settings for the control name (DNS, Proxy, Network reset) — Microsoft still indexes those terms even when the sidebar layout changes.
—
*Written by Rohit Srivastav for Hiektec.in — clear fixes for Windows, Android, apps & Wi‑Fi.*
Approximate word count: ~2,650