How to Fix "WiFi Connected But No Internet" on Windows
Your laptop says it is connected, the WiFi icon shows a yellow triangle, and nothing loads — but other devices on the same network work fine. That pattern points at your PC's network configuration, not the router. This guide walks the fixes in order, from a 30-second IP renew to a full network-stack reset.
- ✓Confirms whether the problem is your PC or the router before you waste time rebooting hardware
- ✓Renews the IP lease, flushes DNS, and resets the TCP/IP + Winsock stack in the correct order
- ✓Clears the leftover proxy and IPv6 settings that silently block traffic after a VPN or update
Best when one Windows PC has "No Internet" while phones and other devices on the same WiFi work normally.
Main Troubleshooting Guide
How to Fix No Internet Connection →Complete symptoms, causes, and step-by-step solutions
Symptoms
You might be experiencing this problem if you notice:
- •WiFi shows "Connected" but the status reads "No Internet" or "No Internet, secured"
- •Yellow warning triangle over the WiFi icon in the system tray
- •Browser shows "This site can't be reached" or "DNS_PROBE_FINISHED" on every site
- •You can reach the router admin page (192.168.x.1) but no external sites
- •Other devices — phones, tablets — work fine on the exact same network
- •It started after waking from sleep, a Windows update, or disconnecting a VPN
- •Pinging 8.8.8.8 works but pinging google.com fails (a DNS problem)
- •Neither ping by IP nor by name works (an IP/gateway or stack problem)
The fastest triage: open Command Prompt and run "ping 8.8.8.8" then "ping google.com". If the IP works but the name fails, it is DNS. If neither works, it is your IP lease or the TCP/IP stack.
What RescuePC checks for "No Internet" on WiFi
RescuePC runs the network-recovery sequence in the right order and verifies each step, so you do not have to memorize a dozen netsh commands or guess which layer is broken.
- →Tests reachability by IP vs. by name to pinpoint whether it is DNS, the IP lease, or the stack
- →Releases and renews the DHCP lease and flushes the DNS resolver cache
- →Resets the TCP/IP stack and Winsock catalog (the usual fix after a VPN or malware removal)
- →Detects and clears a stuck system proxy and conflicting IPv6/DNS settings
- →Re-checks the WiFi adapter driver and power-management setting that drops the link on resume
This is most useful when the connection works on every other device, or when "No Internet" keeps returning after each sleep/wake cycle.
When These Fixes Resolve It
- ✓Other devices work on the same WiFi but one Windows PC shows "No Internet"
- ✓The problem appeared after a VPN, proxy app, malware cleanup, or Windows update
- ✓Your IP shows 169.254.x.x, or sites fail only by name (DNS)
- ✓"No Internet" returns every time the laptop wakes from sleep
These are all PC-side network configuration faults — exactly what the IP renew, stack reset, proxy/DNS cleanup, and adapter re-arm steps repair.
When the Problem Is the Network, Not Windows
If every device loses internet, the fault is upstream of your PC:
- ⚠All devices — phones, tablets, other PCs — also have no internet (router or ISP outage)
- ⚠The router itself cannot reach the internet from its own status page
- ⚠Only specific sites fail for everyone (a remote outage, not your machine)
Common Causes
- ⚠A stale or failed DHCP lease (your PC ended up with a 169.254.x.x self-assigned address)
- ⚠A corrupted TCP/IP stack or Winsock catalog, often after a VPN, proxy app, or malware removal
- ⚠DNS misconfiguration — a dead ISP DNS server or a poisoned resolver cache
- ⚠A leftover system proxy left enabled by a VPN, work app, or adware
- ⚠WiFi adapter power management switching the radio off and not restoring it cleanly
- ⚠An IPv6 vs. IPv4 conflict where Windows prefers a non-working IPv6 route
- ⚠Outdated or corrupted wireless adapter drivers
- ⚠Date/time wrong enough to break HTTPS, making every site fail to load
Solutions
Solution 1: Confirm It Is Your PC, Not the Router
- 1Check that another device (phone) has working internet on the same WiFi — if it does, the problem is this PC
- 2Open Command Prompt and run: ping 8.8.8.8
- 3Then run: ping google.com
- 4If 8.8.8.8 replies but google.com fails, jump to the DNS fix below
- 5If neither replies, continue with the IP and stack fixes
Solution 2: Release, Renew, and Flush
- 1Open Command Prompt as Administrator
- 2Run: ipconfig /release
- 3Run: ipconfig /flushdns
- 4Run: ipconfig /renew
- 5Run: ipconfig /all and confirm you now have a real IP (not 169.254.x.x) and a Default Gateway
- 6Open a browser and test
Solution 3: Reset the TCP/IP Stack and Winsock
- 1Open Command Prompt as Administrator
- 2Run: netsh winsock reset
- 3Run: netsh int ip reset
- 4Run: netsh int tcp reset
- 5Restart your computer (the reset only takes effect after a reboot)
- 6Reconnect to WiFi and test — this resolves most post-VPN and post-malware cases
Solution 4: Clear a Stuck Proxy and Fix DNS
- 1Open Settings > Network & Internet > Proxy and turn OFF "Use a proxy server" (leave "Automatically detect settings" on)
- 2Open Network Connections (ncpa.cpl) > right-click your adapter > Properties
- 3Select Internet Protocol Version 4 (TCP/IPv4) > Properties
- 4Choose "Use the following DNS server addresses" and enter 1.1.1.1 and 8.8.8.8
- 5Click OK, then run: ipconfig /flushdns and test
Solution 5: Power-Cycle and Re-arm the WiFi Adapter
- 1Open Device Manager > Network adapters > right-click your WiFi adapter > Properties
- 2On the Power Management tab, uncheck "Allow the computer to turn off this device to save power"
- 3On the Driver tab, click Update driver > Search automatically; if it broke after an update, use Roll Back Driver
- 4Open Network Connections (ncpa.cpl), disable the adapter, wait 10 seconds, re-enable it
- 5Reconnect and test, especially after a sleep/wake cycle
Fix "connected, no internet" — the exact commands
Connected-but-no-internet means the Wi-Fi link works but IP, DNS, or routing is broken. These commands isolate which layer failed — run them in order.
ping 1.1.1.1Tests raw connectivity to the internet by IP. If this WORKS but websites fail, the problem is DNS, not the connection.
nslookup example.comTests DNS resolution directly. A timeout here + successful ping = DNS is the broken layer.
ipconfig /release && ipconfig /renewRequests a fresh IP lease — fixes a stale or self-assigned (169.254.x.x) address.
ipconfig /flushdnsClears the DNS cache, removing poisoned or stale entries.
netsh winsock reset && netsh int ip resetRebuilds the socket catalog and TCP/IP stack (reboot required) — the deep fix when the above fail.
The ping/nslookup pair is the diagnosis: ping fails = routing/adapter; ping works + nslookup fails = DNS. RescuePC runs exactly this decision tree in its network repair.
Which "No Internet" Pattern Do You Have?
ping 8.8.8.8 works, ping google.com fails
Likely cause: DNS resolution is broken — wrong/overloaded DNS server or a poisoned cache
Neither IP nor name pings; IP shows 169.254.x.x
Likely cause: DHCP failed to assign an address (APIPA) — stale lease or DHCP client issue
Broke right after disconnecting a VPN or removing malware
Likely cause: A leftover proxy entry or a corrupted Winsock catalog
Only happens after the laptop wakes from sleep
Likely cause: Adapter power management is turning the WiFi radio off to save power
Fix WiFi Connected But No Internet Automatically
RescuePC Toolkit includes 109+ automated repairs that fix this problem with one click. No command line knowledge required.
Download Now - Free TrialNo credit card required • Works on Windows 10 & 11
Fix the Layer That Is Actually Broken
"No Internet" is a stack of possible faults — IP, DNS, Winsock, proxy — and the right test tells you which one in seconds.
- →Another device works = the fault is this PC, not the router
- →IP works, name fails = DNS; nothing works = IP lease or stack
- →Broke after a VPN/malware = Winsock + proxy cleanup
- →RescuePC runs the sequence and verifies each layer so you fix it once