Windows 11 Wi-Fi Connected but No Internet? Complete Troubleshooting Guide
Diagnose Windows 11 Wi-Fi connected but no internet with safe steps for DHCP, DNS, proxy, VPN, drivers, network commands and reset.
Contents
- Windows 11 says connected, but the internet does not work: diagnose the cause before resetting anything
- The five-minute diagnostic: what works and what fails?
- Understand the “No internet, secured” label
- Step 1: use the Windows 11 network troubleshooter
- Step 2: forget and reconnect to the exact Wi-Fi network
- Step 3: inspect the actual IP address, gateway and DNS servers
- Step 4: test the gateway, external reachability and DNS separately
- How to read the diagnostic results
- Step 5: check proxy, VPN and captive portal interference
- Step 6: repair DHCP assignment and clear the DNS cache
- Step 7: correct DNS configuration without creating a new problem
- Step 8: update, roll back or reinstall the Wi-Fi adapter driver
- Step 9: use Winsock and TCP/IP resets only when indicated
- Step 10: network reset is the last resort
- Special case: connected to Wi-Fi, but only after waking from sleep
- Special case: Wi-Fi works on a phone but not Windows 11
- Special case: connected, but browsers say DNS_PROBE_FINISHED_NO_INTERNET
- Special case: public Wi-Fi, school or office network
- Common mistakes that make a simple outage worse
- When to contact your ISP, router vendor or computer manufacturer
- A practical repair order you can follow
- Official sources and further reading

Windows 11 says connected, but the internet does not work: diagnose the cause before resetting anything
Your Windows 11 laptop shows Connected, no internet or No internet, secured, yet the Wi-Fi signal looks strong. This does not necessarily mean your wireless hardware has failed. A successful connection to a router is different from having a working route to websites. DNS resolution, DHCP address assignment, a VPN, a proxy, a captive portal, the router’s upstream link, or the Windows network stack can all break independently.
This Windows 11-specific guide prioritizes reversible tests, explains how to interpret actual command output, and reserves destructive resets for last. If your main problem is that Wi-Fi works on one device but not another, see our related cross-device Wi-Fi troubleshooting guide. For the operating-system-specific procedure, continue below.
Official starting point: Microsoft: Fix Wi-Fi connection issues in Windows. Interface labels can vary by Windows 11 build, PC vendor, and whether the device is managed by an employer or school.
The five-minute diagnostic: what works and what fails?
- Test two unrelated websites in a browser, then try an app. A single unavailable website does not prove an internet outage.
- Connect a phone to the same Wi-Fi network and turn off its cellular data for the test. If the phone also fails, suspect the router, captive portal, or provider.
- If permitted, connect the laptop to a different network, such as your own phone hotspot. If it works there, focus on the original network and its settings.
- Restart the affected laptop once. For a home router you control, check its internet/WAN status before restarting it; do not restart shared workplace equipment.
- Record whether the failure started after an update, VPN installation, new router, sleep/wake event, or a change to security software.
| All devices fail on same Wi-Fi | Router, modem, ISP or captive portal | Check router WAN/service status |
|---|---|---|
| Only Windows 11 laptop fails | Laptop profile, DNS, driver, proxy or VPN | Run ipconfig /all and test another network |
| Websites by name fail, but IP connectivity seems possible | DNS resolver or filtering | Run nslookup example.com |
| IP address starts 169.254 | DHCP assignment failed | Check adapter and router DHCP |
| Only one app or website fails | Application, filtering or service issue | Test other destinations; avoid global resets |
| Failure begins after waking from sleep | Driver, power state or roaming | Check driver updates and sleep pattern |
Understand the “No internet, secured” label
The word secured means the Wi-Fi connection is using a security mechanism; it is not a guarantee that internet access works. Windows uses connectivity checks to assess internet availability. Occasionally a corporate firewall, captive portal, or filtering policy can affect those checks even when selected sites work. Verify actual browsing and application access rather than trusting the icon alone. If browsing works normally, do not run aggressive resets just to change an icon.
Step 1: use the Windows 11 network troubleshooter
- Open Start → Settings → Network & internet.
- Look for the recommended network troubleshooter or open Get Help and search for network or Wi-Fi connectivity troubleshooting.
- Follow the on-screen diagnostic and record any identified problem.
- Test the connection before changing another setting.
Microsoft has changed how troubleshooters appear across Windows versions. Some Windows 11 builds launch the Get Help experience instead of the older standalone troubleshooter. A managed work device may limit available options.
Step 2: forget and reconnect to the exact Wi-Fi network
- Before starting, confirm you know the Wi-Fi password or have permission to obtain it.
- Open Settings → Network & internet → Wi-Fi → Manage known networks.
- Choose the problematic SSID and select Forget.
- Reconnect from the Wi-Fi list and enter the correct password.
- Retest two sites. If your company uses certificate-based Wi-Fi, contact IT instead of deleting managed profiles.
Forgetting a network removes its stored configuration. It can help after a router replacement, password change, or stale network profile, but it cannot repair a provider outage.
Step 3: inspect the actual IP address, gateway and DNS servers
Open Command Prompt and run ipconfig /all. Find the active wireless adapter, not an inactive Ethernet or virtual VPN adapter. Note the IPv4 address, Default Gateway, DHCP Enabled status, and DNS Servers. Avoid sharing the full output publicly because it can reveal internal network details.
| 169.254.x.x IPv4 address | Windows likely did not obtain an IPv4 address from DHCP | Investigate router DHCP, network profile and adapter |
|---|---|---|
| 192.168.x.x, 10.x.x.x or 172.16–31.x.x | A common private address; not proof of internet access | Check gateway and DNS tests |
| No default gateway on expected network | No obvious upstream route | Check IP configuration and DHCP |
| Unexpected manual DNS or proxy | Possible stale configuration | Return to approved automatic settings if appropriate |
| VPN adapter instead of Wi-Fi adapter | You may be reading the wrong interface | Inspect the active Wi-Fi section |
A valid private IP address means your laptop has an address on the local network, not that the ISP or DNS service is functioning. The 169.254.x.x pattern often indicates that DHCP assignment did not complete. On corporate networks, static addresses and custom DNS may be intentional—do not override them without approval.
Step 4: test the gateway, external reachability and DNS separately
- Run
ipconfigand note the default gateway address for the active Wi-Fi adapter. - Try
ping YOUR_GATEWAY, replacing the placeholder with the actual address. Some routers block ping; a failed response is not conclusive. - Try
nslookup example.comto see whether a DNS server resolves a hostname. - Try opening multiple reputable websites in the browser. A successful DNS lookup does not by itself prove web access.
- Optionally test
ping 1.1.1.1, but remember ICMP may be blocked; do not treat a timeout alone as proof that internet routing is down.
How to read the diagnostic results
| Gateway reachable, nslookup fails | DNS or filtering issue | Review DNS settings and VPN/proxy |
|---|---|---|
| Gateway not reachable and no valid IP | Local Wi-Fi/DHCP issue | Rejoin SSID; inspect router/adapter |
| DNS resolves but all browsers fail | Proxy, VPN, routing or filtering | Check proxy/VPN and router upstream |
| Browser works, one app fails | App-specific problem | Update app; check its firewall permissions |
| Hotspot works, home Wi-Fi fails | Network-specific configuration | Inspect router and ISP status |
Step 5: check proxy, VPN and captive portal interference
Go to Settings → Network & internet → Proxy. A manual proxy can redirect traffic to an unavailable server. If this is your personal PC and you did not configure one, investigate unexpected manual settings. Do not disable a work or school proxy without IT approval. Microsoft explains the different proxy modes in its Windows proxy guidance.
If a personal VPN is active, disconnect it temporarily and test the connection. Some VPN clients use a kill switch that intentionally blocks traffic while disconnected; check the app’s own settings instead of uninstalling blindly. For hotel, airport or guest Wi-Fi, open a browser and look for an authorized sign-in or terms page. If no page appears, ask the network operator for its supported captive-portal procedure. Do not enter credentials into an unexpected imitation login page.
Step 6: repair DHCP assignment and clear the DNS cache
If the active adapter has an incorrect DHCP address or stale DNS behavior, open Command Prompt as administrator and use only the commands relevant to your symptoms. Releasing an address will interrupt active connections. Avoid running these on a remote computer you are controlling over the same network.
- For DHCP problems, run
ipconfig /release, thenipconfig /renew. - For suspected cached DNS problems, run
ipconfig /flushdns. - Run
ipconfig /allagain to verify the new address, gateway and DNS servers. - Test actual websites after each repair. If renewal fails, inspect the router DHCP service or ask the network administrator.
These commands are documented by Microsoft Learn: ipconfig. They cannot fix a wrong wireless password, failed router WAN link, or unsupported Wi-Fi radio band.
Step 7: correct DNS configuration without creating a new problem
Open Settings → Network & internet → Wi-Fi → Hardware properties or the relevant network properties and inspect DNS server assignment. If a manually entered DNS server is outdated or unreachable on your personal home network, restoring Automatic (DHCP) can be a useful test. Some Windows 11 versions expose the setting through the DNS server assignment Edit button. Do not override DNS on a managed computer or a network that requires specific filtering.
Public DNS providers can be used for controlled diagnosis, but changing DNS is not a universal fix. A broken gateway, expired captive-portal session, parental-control policy, or disconnected ISP cannot be repaired merely by choosing a different resolver. Record the original configuration so you can reverse the test.
Step 8: update, roll back or reinstall the Wi-Fi adapter driver
- Open Device Manager → Network adapters and identify the actual Wi-Fi adapter manufacturer and model.
- Check Settings → Windows Update for approved driver updates, or visit your PC manufacturer’s official support page.
- If the failure began immediately after a driver update and Roll Back Driver is available in adapter Properties, consider rolling back and retesting.
- Before uninstalling a driver, download a compatible replacement using another connection or device and save it locally.
- Only then consider uninstalling the adapter in Device Manager and restarting. Windows may reinstall it, but this is not guaranteed on every device.
Avoid third-party “driver updater” tools, especially ones demanding payment or installing bundled software. On company-owned computers, obtain approval before changing drivers. If your laptop repeatedly disconnects after sleep, document the timing and check vendor release notes for the wireless driver and firmware.
Step 9: use Winsock and TCP/IP resets only when indicated
If the laptop has persistent Windows networking stack symptoms after simpler checks, Microsoft documents broader repair commands. In an elevated Command Prompt, run netsh winsock reset and, if necessary, netsh int ip reset, then restart Windows. These can change networking configuration and affect software that depends on custom network settings. They are not a first response to a single unavailable website or a router-wide outage.
Save work, note custom settings, and avoid running resets on remote-only systems where you could lose access. If a corporate VPN or endpoint security suite is installed, coordinate with IT before proceeding.
Step 10: network reset is the last resort
For Windows 11, go to Settings → Network & internet → Advanced network settings → Network reset. Review the warning before selecting Reset now. Microsoft explains that this removes installed network adapters and their settings and reinstalls adapters after restart. You may need to reconnect to Wi-Fi, reconfigure VPN software or virtual switches, and review network profile settings afterward.
If you rely on Hyper-V, a virtual machine, a custom static IP, a VPN client, or workplace networking, back up or document the relevant settings first. If multiple devices fail on the same router, a Windows network reset is unlikely to be the right remedy.
Special case: connected to Wi-Fi, but only after waking from sleep
When the issue happens only after sleep, test a full restart and a fresh connection, then update the wireless driver from the laptop vendor. Some adapters expose a Power Management tab in Device Manager; others do not. If available, test relevant power-saving settings carefully, as they may affect battery life. A sleep-related failure that follows the laptop across different Wi-Fi networks points more toward the device than the home router.
Special case: Wi-Fi works on a phone but not Windows 11
Make sure the phone is actually using the same SSID with cellular data disabled. If the Windows laptop works on your phone hotspot, the problem is more likely a compatibility or configuration issue with the original router, such as band selection, security mode, access rules, or DHCP behavior. Do not downgrade router security or disable its firewall without understanding the risk. See our device-by-device guide for router, Android and iPhone comparisons.
Special case: connected, but browsers say DNS_PROBE_FINISHED_NO_INTERNET
This browser error is a clue, not a diagnosis. Test other browsers and apps, then run nslookup example.com and inspect proxy/VPN configuration. If DNS resolution succeeds but the browser still fails, look at browser extensions, security filtering, captive portals and system time rather than repeating DNS cache flushes indefinitely.
Special case: public Wi-Fi, school or office network
Guest networks may require browser authentication, limit the number of registered devices, or restrict certain services. Workplaces may use 802.1X authentication, certificates, managed DNS, proxies or device compliance policies. If you cannot access the internet only on a managed network, contact its administrator. Avoid random certificate installation, disabling endpoint security, or bypassing network restrictions.
Common mistakes that make a simple outage worse
- Changing router DNS, Windows DNS, firewall, proxy and driver all at once, making it impossible to identify the cause.
- Disabling IPv6 globally as a blanket fix without evidence of an IPv6-specific problem.
- Uninstalling a wireless driver without first obtaining a replacement.
- Using Network reset before checking whether other devices also lost internet.
- Running
ipconfig /releaseduring a remote support session. - Treating a failed ping as definitive proof of an internet outage.
- Assuming the Wi-Fi icon alone proves that every application should work.
When to contact your ISP, router vendor or computer manufacturer
Contact the ISP when multiple devices fail, the modem/router reports an upstream fault, or the service remains unavailable after confirming the account and local equipment status. Contact the router manufacturer when one band, security mode or DHCP service behaves inconsistently across devices. Contact the PC manufacturer if the wireless adapter disappears from Device Manager, repeatedly fails across independent networks, or shows hardware errors after approved driver and firmware checks.
For work or school equipment, give IT the exact error message, affected SSID, time of failure, whether a hotspot works, and any changes that preceded the issue. Avoid sending passwords, private IP configuration screenshots or other sensitive details to public forums.
A practical repair order you can follow
- Confirm whether the failure affects one device or the whole network.
- Check two websites, another app, and a second network.
- Run the Windows network troubleshooter.
- Reconnect to the Wi-Fi network if you have its credentials.
- Read the active adapter’s IP, gateway and DNS using
ipconfig /all. - Test name resolution with
nslookupand check proxy/VPN/captive portal settings. - Renew DHCP or flush DNS only when the results justify it.
- Update or roll back the wireless driver if the issue points to the adapter.
- Use Winsock/TCP/IP repair if the Windows stack appears broken.
- Reserve Network reset for persistent failures after recording custom configuration.
