“No Internet, Secured” in Windows 11 — connected to Wi-Fi with the lock icon showing but no actual internet access — is one of those errors that sounds more technical than it is. The “Secured” part means the Wi-Fi authentication worked (password correct, encryption established). The problem is specifically between your router and the internet, or between Windows and the router for IP address assignment. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
The fastest distinguishing test: can you reach your router’s admin page? Open a browser → go to 192.168.1.1 (or whatever your router’s IP is). If the router admin page loads: your device has a valid local connection to the router. The issue is the router’s connection to the internet (ISP problem, router reboot needed). If the admin page doesn’t load: the problem is between Windows and the router — IP assignment failure, network stack issue, or DNS.
Release and renew the IP address
The most common cause: Windows connected to Wi-Fi but didn’t get a valid IP address from the router’s DHCP. The network shows as connected but traffic has nowhere to go because there’s no valid IP.
Administrator Command Prompt:
ipconfig /release
ipconfig /renew
After /renew: run ipconfig /all → the IP address shown for the Wi-Fi adapter should be in your router’s range (typically 192.168.1.x or 10.0.0.x). If it shows 169.254.x.x: DHCP failed and Windows assigned itself a fallback address. If it shows the correct range: IP is fine and the problem is elsewhere (usually DNS or the router’s internet connection).
Restart the router
Unplug it for 60 seconds → plug it back in. This is more effective than most settings changes for this specific error because “No Internet, Secured” often means the router itself has lost its connection to the ISP. The router restart forces it to re-establish the upstream connection. While the router restarts: check whether other devices on the network also show no internet. If they do: it’s definitely the router or ISP, not the Windows machine.
DNS — the quick fix when IP is correct
If ipconfig shows a valid IP but internet still doesn’t work: DNS is likely the problem. Switching from the router’s DNS to a known-reliable server:
Settings → Network and internet → Wi-Fi → your connection → DNS server assignment → Manual → Preferred DNS: 1.1.1.1, Alternate: 8.8.8.8 → Save.
After changing: open a browser and try loading a site. If it works: the router’s DNS or ISP’s DNS was failing. The manual DNS setting bypasses the router’s DNS handling entirely and goes directly to public resolvers.
Network stack reset — the thorough fix
Administrator Command Prompt:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renew
Restart after running all five. This completely resets the Windows networking stack, clears cached DNS entries, and requests fresh IP assignment from the router. The most comprehensive software-side fix for persistent “No Internet, Secured” that survives multiple reconnection attempts.
Network adapter driver
A buggy or outdated Wi-Fi driver can cause Windows to report “No Internet” even when the connection is technically established. Device Manager → Network Adapters → right-click Wi-Fi adapter → Update driver. Also from the laptop manufacturer’s support page for the specific model.
If this error started after a Windows Update: Properties → Driver → Roll Back Driver. Windows Updates frequently replace manufacturer Wi-Fi drivers with generic versions that handle DHCP and DNS differently.
Proxy settings
A proxy that’s configured but unreachable — leftover from a corporate VPN, a manually set proxy from troubleshooting another issue, or a proxy automatically configured via WPAD that’s now wrong — causes “No Internet” even when IP and DNS are working correctly. All traffic goes to the proxy and the proxy doesn’t respond.
Settings → Network and internet → Proxy → confirm both “Automatically detect settings” and “Use a proxy server” are Off for home networks. If “Use a proxy server” is On: clear the address and port → Apply. After removing the proxy: internet access should restore immediately.
When other devices work and Windows doesn’t
If a phone on the same Wi-Fi has internet but the Windows machine shows “No Internet, Secured”: the problem is Windows-specific. Run the network stack reset above. Also check whether the IP is in the expected range (ipconfig /all) and whether DNS resolves correctly (nslookup google.com in Command Prompt — should return IP addresses, not “Server failed”).
A “Server failed” from nslookup with a valid IP address confirms DNS is specifically broken even when IP assignment succeeded. The DNS change to 1.1.1.1 / 8.8.8.8 resolves this directly.
Our guide on Wi-Fi connectivity diagnostics covers the router-level causes that affect all devices on the network, not just Windows machines. For IP address conflicts that cause “No Internet” status, our IP conflict guide covers the DHCP conflict scenarios in detail. Microsoft’s network connectivity troubleshooting covers the Network Diagnostics troubleshooter and the specific registry values for Network Location Awareness (NLA) that determine how Windows classifies network connectivity status — the same component that generates “No Internet, Secured” classifications.
Network Location Awareness service
Windows uses the Network Location Awareness (NLA) service to determine whether a connection has internet access. NLA checks a specific Microsoft endpoint (www.msftconnecttest.com) to verify connectivity. If this endpoint is blocked — by a firewall, antivirus, or content filter — NLA reports “No Internet” even when actual internet access is working correctly for everything else.
Test: try accessing a non-Microsoft site directly in a browser. If it loads normally but Windows shows “No Internet, Secured”: NLA’s connectivity test endpoint is blocked. Add msftconnecttest.com to the firewall/antivirus exclusions. This fix is particularly relevant on corporate networks where content filters block Microsoft’s connectivity check endpoints.
NCSI (Network Connectivity Status Indicator) settings
NCSI is the Windows component that displays the “No Internet” overlay. On rare occasions: NCSI itself has a registry misconfiguration that reports “No Internet” even when connectivity is fine. Registry Editor → HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesNlaSvcParametersInternet:
- EnableActiveProbing → should be 1 (enabled)
- ActiveWebProbeHost → should be www.msftconnecttest.com
- ActiveWebProbePath → should be /connecttest.txt
If these values are incorrect or missing: NCSI can’t perform connectivity tests and defaults to showing “No Internet.” Restoring the correct values allows NCSI to accurately determine and display the connection status.
VPN and “No Internet” status
VPN connections sometimes cause Windows to show “No Internet, Secured” on the underlying Wi-Fi connection even when the VPN itself has internet access. This happens because the VPN takes over routing and the original Wi-Fi connection no longer routes traffic directly — NLA’s test to the Microsoft endpoint goes through the VPN, and if the VPN changes the routing so the test fails: “No Internet” appears on the Wi-Fi despite the VPN working.
This is mostly cosmetic when the VPN is connected and working. To confirm: disconnect the VPN → check if “No Internet” clears on the Wi-Fi icon. If it does: the VPN routing was causing the false negative. While connected to the VPN, the VPN connection’s icon (in Settings → Network → VPN) should show the true connectivity status.
Captive portal detection failure
Hotel, airport, and coffee shop Wi-Fi networks use captive portals — you connect to Wi-Fi but need to open a browser and accept terms or log in before internet access is granted. Windows detects captive portals by checking the NCSI endpoint and prompting to open a browser if it doesn’t respond correctly. Sometimes this detection fails: Windows shows “No Internet, Secured” but opening a browser manually (typing any URL) redirects to the captive portal login page.
Fix: open a browser and type any URL → the captive portal redirect should appear → log in or accept terms → internet works. If the redirect doesn’t appear even after the browser is open: navigate directly to a non-HTTPS site (http://neverssl.com is designed for this — it’s specifically a simple HTTP site that forces captive portal redirects to trigger). After authenticating: Windows updates its connection status to show internet access.
MAC address and corporate network authentication
Some corporate networks authenticate devices by MAC address — only registered MACs get internet access. If the device’s MAC recently changed (random MAC address feature, hardware replacement, or MAC spoofing software), the router grants basic Wi-Fi access but blocks internet until the MAC is approved.
Settings → Network → Wi-Fi → your network → Random hardware addresses → Off. After disabling random MAC: reconnect. The device uses its hardware MAC address, which may already be registered with the corporate network. If it’s a new device: report the hardware MAC address (ipconfig /all → Physical Address for the Wi-Fi adapter) to IT for registration in the network’s MAC allowlist.
IPv6 connectivity issues
Windows 11 shows separate connectivity status for IPv4 and IPv6. “No Internet, Secured” sometimes refers to IPv6 connectivity failure while IPv4 works fine. In Settings → Network, hovering over or clicking the network shows whether IPv4 has internet access. If IPv4 shows internet access but the overall status shows “No Internet”: IPv6 is failing and Windows is reporting the overall status based on IPv6.
Disabling IPv6 on the adapter: Network and Sharing Center → change adapter settings → right-click Wi-Fi adapter → Properties → uncheck “Internet Protocol Version 6” → OK. After disabling: Windows uses only IPv4 and reports the correct internet status. This is a workaround rather than a fix — proper IPv6 requires router-side configuration, but disabling it at the adapter level provides immediate resolution of the false “No Internet” status.
Windows 11 known connectivity detection bugs
Specific Windows 11 builds have had bugs where NCSI reports “No Internet” incorrectly — particularly after resume from sleep or after specific network configuration changes. These appear as widespread reports of “No Internet” on the same Windows version and are typically patched in subsequent cumulative updates. Settings → Windows Update → Check for updates → install any pending updates → restart → test connectivity status.
Physical adapter state — disable and re-enable
Device Manager → Network Adapters → right-click the Wi-Fi adapter → Disable device → wait 10 seconds → right-click → Enable device. This hardware-cycles the adapter rather than just disconnecting from the network — more thorough than toggling Wi-Fi on/off in Settings. After re-enabling: Windows re-initialises the adapter’s connection to the router, which sometimes resolves “No Internet” that persisted through software network resets.
Firewall blocking NCSI probes
Third-party firewalls that block outbound connections by default sometimes block the NCSI probes that Windows uses to verify internet access. Windows Defender Firewall allows these by default; third-party products with “ask before allowing” configurations may have blocked the msftconnecttest.com request when it first appeared, causing permanent “No Internet” status.
Check the third-party firewall’s logs or blocked connections list for msftconnecttest.com → allow it → the NCSI probe works again and Windows accurately shows internet access status. This is a common cause on machines where a new firewall was recently installed and “No Internet” appeared shortly after installation without any network changes.
The most important distinction for this error: is it a real connectivity failure (browser can’t load sites) or a false positive (browser works fine but the taskbar icon shows “No Internet”)? These have completely different fixes. Real failure: IP release/renew, DNS change, network stack reset. False positive: NCSI probe blocked, IPv6 showing failure while IPv4 works, VPN routing changing the test path. Confirm which type before starting any fixes — open a browser and try a site first. If the browser works: the “No Internet” label is a display issue, not a real connectivity problem, and the NLA/NCSI fixes apply rather than the networking fixes.
ISP-level outage during troubleshooting
If the router admin page loads (confirming local connection) but the internet is down on all devices: call the ISP before doing anything else on the Windows machine. An ISP outage in the area causes exactly this symptom — connected to Wi-Fi, router accessible, but no internet on any device. Troubleshooting Windows networking during an ISP outage wastes time that becomes obvious once service is restored. Most ISPs have outage status pages or phone support that confirms regional outages immediately. Check before running any of the network reset commands that require subsequent reconfiguration.
After resolving the immediate “No Internet” issue: if it recurs periodically, the cause is likely a DHCP lease management problem (router issuing short leases that Windows doesn’t renew cleanly) or a driver power management issue. Setting a static IP eliminates DHCP renewal failures permanently. Disabling network adapter power management (Device Manager → Wi-Fi adapter → Power Management) eliminates power-related connectivity drops. These two changes together prevent the most common recurring causes without requiring the same troubleshooting sequence each time the error reappears.
One more practical note: the Windows network troubleshooter (Settings → System → Troubleshoot → Other troubleshooters → Internet connections → Run) is sometimes dismissed as ineffective, but for “No Internet, Secured” specifically it often identifies and fixes the most common causes automatically — DHCP failure, DNS misconfiguration, adapter in bad state — without requiring manual commands. Running it as the first automated step (while the full fixes are already in this article as backup) takes 2 minutes and occasionally resolves the issue without any manual investigation, which is the best possible outcome. Related: No Internet After Windows Update.






