“Wi-Fi connected but no internet” is one of the most common network complaints — and one of the most misdiagnosed. The Wi-Fi icon shows connected, but nothing loads. Before spending an hour in Windows settings, take one minute to check whether the problem is actually with your machine. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Check the router and other devices first. Can your phone access the internet on the same Wi-Fi? Can another laptop connect? If nothing can reach the internet, the issue is your router or ISP — not Windows. Restart the router (unplug 60 seconds, plug back in, wait 2 minutes) and test. If the phone works and your PC doesn’t, it’s a Windows-side problem and the fixes below apply.
Understanding the Specific Failure
“Connected but no internet” means the Wi-Fi adapter successfully associated with the router and got an IP address — but traffic isn’t reaching the internet beyond the router. This differs from “limited connectivity” (no IP address from DHCP) and from “no network at all” (adapter can’t connect to the router).
To confirm the exact failure point: open Command Prompt and run:
ping 192.168.1.1If this gets replies, the router is reachable and the problem is beyond the router (DNS, upstream, or routing). If this fails, the problem is between the PC and the router.
Fix 1: DNS Is the Most Likely Culprit
When the router is reachable but internet pages won’t load, DNS failure is the most common cause. The connection works, but the domain name translation (turning “google.com” into an IP address) is failing.
Test it: in Command Prompt, run ping 8.8.8.8. If this gets replies, internet connectivity works but DNS is broken. If pages don’t load but this IP ping works, DNS is confirmed as the issue.
Fix: Settings → Network and internet → Wi-Fi → your connection → DNS server assignment → Edit → Manual → enter:
- Preferred DNS: 1.1.1.1
- Alternate DNS: 8.8.8.8
Save and test. Switching from the ISP’s DNS to Cloudflare or Google resolves the issue immediately when the ISP’s DNS server is the problem. Also run ipconfig /flushdns from administrator Command Prompt to clear any cached bad DNS entries.
Fix 2: Network Stack Reset
Corrupted TCP/IP or Winsock configuration blocks internet traffic even when the Wi-Fi association is fine. This is the most effective fix when DNS is working but pages still don’t load, or after VPN software changes network settings unexpectedly:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renewRun from an administrator Command Prompt, then restart the PC. This resolves a substantial proportion of “connected but no internet” cases by clearing the accumulated network stack configuration that prevents proper routing.
Fix 3: Proxy Settings
A proxy server configured in Windows settings intercepts all web traffic and routes it through the proxy. When the proxy is unreachable (corporate proxy accessed from home, a VPN proxy left over after disconnecting), all web traffic fails while the Wi-Fi connection itself shows as connected.
Check: Settings → Network and internet → Proxy. If “Use a proxy server” is On, turn it off. Also check Settings → Network and internet → VPN — if a VPN is showing as connected but you don’t actively need it, disconnect it. Stale proxy and VPN configurations are a common cause of sudden “connected but no internet” that appears without any obvious trigger.
Fix 4: Update or Roll Back Network Adapter Driver
A driver update that introduced a routing bug, or a Windows update that replaced the manufacturer’s Wi-Fi driver with a generic version, can cause “connected but no internet” where the association works correctly but traffic forwarding is broken.
If the problem appeared after a recent update: Device Manager → Network Adapters → right-click Wi-Fi adapter → Properties → Driver → Roll Back Driver.
If the driver is outdated: download the current Wi-Fi driver from the laptop manufacturer’s support page — manufacturer drivers for Intel, Qualcomm, and Realtek adapters handle routing correctly where generic Windows drivers sometimes don’t.
Fix 5: IPv6 Issues
Windows prefers IPv6 when available. On networks where IPv6 is partially configured but not fully functional, Windows attempts IPv6 routing, fails, and falls back to IPv4 — but this fallback doesn’t always happen quickly, creating “connected but no internet” delays or failures.
Test by disabling IPv6: Settings → Network and internet → Advanced network settings → More network adapter options → right-click Wi-Fi adapter → Properties → uncheck “Internet Protocol Version 6 (TCP/IPv6)” → OK. If internet access restores immediately, IPv6 misconfiguration was the cause. Leave IPv6 disabled as a workaround until the router’s IPv6 configuration is corrected.
Fix 6: Router-Specific Fixes
When only one device on the network can’t reach the internet while others can, the router may have a per-device block, a MAC address filter, or the device’s DHCP entry may be in a broken state. Restart the router to clear its client table. If that doesn’t help:
- Log into the router admin panel → check whether MAC filtering is enabled and whether the PC’s MAC address is blocked
- Check the DHCP client table for the PC — if it shows an IP address in an error state, remove the entry and force the PC to request a new lease (
ipconfig /releasethenipconfig /renew)
The Captive Portal Exception
Hotel Wi-Fi, coffee shop networks, and corporate guest Wi-Fi often require logging in through a captive portal web page before granting internet access. Windows shows “Connected” once it associates with the network, but the network blocks all traffic until you log in.
Open any browser and navigate to a non-HTTPS page like http://neverssl.com — this forces the browser to an unencrypted connection that the captive portal can intercept and redirect to the login page. HTTPS pages often fail to redirect correctly. After completing the captive portal login, regular internet access opens.
Our guide on DNS server not responding covers DNS failures in more depth — the resolver configuration and DNS client service issues that cause DNS-specific connectivity failures. For the Wi-Fi adapter driver and power management fixes, our Wi-Fi keeps disconnecting guide covers those fixes in the context of recurring disconnections that share the same root causes. Microsoft’s network connectivity documentation covers the Network Diagnostics Framework that Windows runs automatically when you click the network icon and troubleshoot, including the specific checks Windows performs to classify connectivity as “connected,” “limited,” or “no internet.”
Windows Network Connectivity Test and the NCA Probe
Windows checks internet connectivity by sending a request to a Microsoft server (msftconnecttest.com). When this test fails but the internet actually works for other purposes — because the Microsoft server is temporarily unreachable, or because a firewall blocks that specific test request — Windows shows “No internet access” even though Chrome, Firefox, and other applications can browse normally.
Confirm: open a browser and navigate directly to a known page (google.com, bbc.com). If it loads, the internet is working and Windows’ connectivity indicator is incorrect — not a genuine connectivity problem. This “false alarm” from Windows’ test is more common than people expect, particularly on networks where the Microsoft connectivity test endpoint is filtered by a firewall or security appliance. No fix is needed when the browser works but the Windows indicator says no internet.
Antivirus and Firewall Blocking Traffic
Security software — particularly full security suites with built-in firewalls — occasionally blocks all internet traffic after an update, after a false-positive detection, or after a policy change in the product. The Wi-Fi connection shows as active, but the firewall is silently dropping all outbound traffic.
Test: temporarily disable the security suite’s firewall component (not the full antivirus, specifically the firewall) and test internet access. If pages load with the firewall disabled, the firewall has a misconfigured rule blocking all traffic. Check the firewall’s blocked list and event log for entries — most security suite firewalls log what they block, and the log shows whether a broad “block all” rule was applied or whether a specific application is being blocked. Re-enable the firewall after identifying and correcting the problematic rule.
Date and Time Affecting HTTPS Connections
All HTTPS connections (which is essentially all modern web traffic) validate the server’s certificate against the current time. When the system clock is significantly wrong — more than a few minutes off — HTTPS certificate validation fails and all secure web traffic appears broken while the connection is technically established. Pages show certificate errors rather than the “no internet” indicator, but the root cause is the same: the Wi-Fi is connected but HTTPS traffic won’t work.
Check the clock: right-click the taskbar clock → Adjust date and time → confirm correct date and time → Sync now. After syncing, HTTPS traffic immediately works. This is especially common after a CMOS battery failure (which causes the clock to reset to a default date on every startup) or after a machine was turned off for an extended period.
MTU Mismatch and Partial Connectivity
Maximum Transmission Unit (MTU) settings affect how large each network packet can be. When the MTU is set incorrectly — often left at a non-standard value by VPN software installation — large packets get fragmented or dropped, causing some web pages to load while others don’t. Small pages (404 error pages, simple text pages) may load while complex pages with large resources fail. This is an intermittent “connected but no internet” that’s highly inconsistent and confusing to diagnose.
Check MTU: Command Prompt → netsh interface ipv4 show subinterfaces. The MTU should be 1500 for standard Wi-Fi. If it shows a different value: netsh interface ipv4 set subinterface "Wi-Fi" mtu=1500 store=persistent. After resetting the MTU, the packet size mismatch is resolved and pages that were failing to load because of large packet drops should load correctly.
VPN Split Tunneling Configuration
When a VPN is connected with split tunneling configured, some traffic routes through the VPN and some routes directly. When the split tunneling rules are misconfigured or the VPN client is in an inconsistent state, all traffic may end up being dropped — because traffic that should go directly gets routed to the VPN, and the VPN rejects it because it doesn’t match the VPN’s expected traffic pattern.
Disconnecting the VPN and testing internet access without it is the quickest diagnostic. If internet works without the VPN, reconnect the VPN and check whether split tunneling is configured correctly. Setting split tunneling to “Full tunnel” (all traffic through VPN) or “No tunnel” (disconnect the VPN) are both reliable states — it’s the intermediate split tunneling configurations that produce the inconsistent partial connectivity that looks like “connected but no internet.”
Network Bridge Misconfiguration
Windows allows creating network bridges between adapters — useful for sharing internet connections between adapters. When a network bridge is configured incorrectly or accidentally, it can intercept Wi-Fi traffic and fail to route it correctly, producing “connected but no internet” on the Wi-Fi adapter.
Check: Settings → Network and internet → Advanced network settings → More network adapter options. If a “Network Bridge” adapter appears in addition to the Wi-Fi adapter: right-click → Delete (if not intentionally configured). After removing the inadvertent bridge, the Wi-Fi adapter routes traffic directly through the router without the bridge intercept, restoring internet access. Network bridges in home environments are almost never needed — they were primarily useful in early router-free networking setups that are essentially obsolete.
Check Routing Table
For persistent “connected but no internet” where all other fixes haven’t resolved it: the Windows routing table may have a corrupted or incorrect entry that redirects all traffic incorrectly.
Check: administrator Command Prompt → route print. Look at the IPv4 Route Table section. The “Default Gateway” entry (destination 0.0.0.0) should show your router’s IP address (typically 192.168.1.1) with an appropriate metric. If it shows a different IP, or if multiple default gateway entries conflict, the routing table has a problem. Running the Winsock and IP reset commands from Fix 2 clears these routing table issues and allows Windows to rebuild a correct routing table. After the reset and restart, route print should show a single clean default gateway entry pointing to the router.
A practical observation worth sharing: “Wi-Fi connected but no internet” is the Windows connectivity issue with the highest rate of spontaneous resolution. Wait 5–10 minutes and try again — network glitches at the ISP or router level that cause this symptom often clear themselves. If internet access returns without any changes, the issue was upstream and transient. This doesn’t mean ignoring it if it keeps happening, but a single occurrence that resolves itself isn’t worth a full troubleshooting session. Track whether it recurs (and how often) before investing time in the deeper fixes — recurrence once a day or more is worth systematic investigation, while once a month is usually not. Related: VPN Slowing Internet Speed.
