Your Windows laptop connects to Wi-Fi, displays a reassuring little lock icon, and then announces, “No Internet, secured.” In other words, the computer has successfully entered the building but cannot find the door to the internet.
This frustrating Windows 10 and Windows 11 Wi-Fi error usually means your PC has established a secure wireless connection with the router, but something is blocking internet access beyond that local connection. The culprit might be a temporary router failure, an invalid IP address, a broken DNS configuration, a misbehaving network driver, VPN software, or an outage at your internet service provider.
The best approach is not to start wildly clicking every network option in sight. Work through the fixes below in order, beginning with quick checks and saving destructive resets for later. Microsoft and major networking manufacturers similarly recommend separating computer-specific problems from router, modem, and ISP failures before changing advanced settings.
What Does “No Internet, Secured” Mean?
The word secured describes the connection between your computer and the Wi-Fi access point. It generally means the network is protected with a security protocol and Windows has accepted the correct Wi-Fi password.
It does not guarantee that the router itself can reach the internet. Your PC might be connected securely to a router that has lost its modem connection, failed to receive a public WAN address, or cannot communicate with the ISP.
The message can also appear when internet access is technically available but Windows cannot complete its connectivity test. That occasionally happens with captive portals, VPNs, DNS filters, corporate firewalls, security software, and networks that block Microsoft’s connection-checking services.
Common causes include:
- A temporary modem, router, or ISP outage
- A damaged or outdated wireless adapter driver
- An expired or invalid DHCP lease
- Incorrect static IP or DNS settings
- A corrupted Winsock or TCP/IP configuration
- A saved Wi-Fi profile that no longer matches the router
- VPN, proxy, firewall, or web-filtering software
- Wireless adapter power-saving behavior
- A router firmware, security-mode, or channel problem
Diagnose the Problem Before Changing Anything
A minute of testing can save half an hour of resetting things that were innocent all along.
Check another device
Connect a phone, tablet, or another computer to the same Wi-Fi network.
- If every device has no internet, focus on the modem, router, or ISP.
- If only the Windows computer fails, focus on its Wi-Fi profile, settings, software, and driver.
Try a phone hotspot
Temporarily connect the Windows PC to a mobile hotspot. If the hotspot works, the computer’s Wi-Fi hardware is probably functional. The home router, saved network profile, DHCP service, or router security configuration becomes the more likely suspect.
Test Ethernet when possible
Connect the computer to the router with an Ethernet cable.
- If Ethernet works but Wi-Fi does not, investigate the wireless adapter and router radio settings.
- If Ethernet and Wi-Fi both fail, investigate Windows networking, the router’s internet connection, or the ISP.
Open a browser manually
Public Wi-Fi networks at hotels, airports, universities, and coffee shops often require a sign-in page. Open a browser and visit a plain HTTP website or the router’s local address. A captive portal may appear even though Windows initially reports no internet.
1. Turn Wi-Fi Off and Back On
Begin with the least glamorous fix, because it succeeds far more often than its sophistication level suggests.
- Click the network icon on the taskbar.
- Turn Wi-Fi off.
- Wait about 10 seconds.
- Turn Wi-Fi back on and reconnect.
You can also enable Airplane mode briefly and then disable it. This restarts the wireless radio without rebooting the entire computer.
2. Forget the Wi-Fi Network and Reconnect
A saved wireless profile contains the network name, password, security type, and connection preferences. If the router password or security mode changed, the old profile can become the digital equivalent of an expired key card.
Windows 11
- Open Settings.
- Select Network & internet.
- Choose Wi-Fi and then Manage known networks.
- Select the affected network and click Forget.
- Reconnect from the taskbar and enter the Wi-Fi password.
Windows 10
- Open Settings > Network & Internet.
- Select Wi-Fi.
- Click Manage known networks.
- Choose the network and select Forget.
- Reconnect and enter the password again.
3. Restart the Computer, Modem, and Router Properly
Restarting network equipment clears temporary memory, rebuilds ISP and DHCP sessions, and forces devices to negotiate fresh connections. The order matters more than many people realize.
- Shut down the computer.
- Unplug the router and modem. If they are one combined gateway, unplug that device.
- Wait at least 30 seconds.
- Plug in the modem first.
- Wait until its connection lights stabilize.
- Plug in the router and allow it to finish starting.
- Start the computer and reconnect.
If every household device lost internet at once, check the router’s Internet or WAN light. A missing, red, or amber WAN indicator may point to an ISP, modem, cable, or authentication problem rather than a Windows problem. Major PC and router manufacturers recommend testing other devices and restarting the network equipment before performing deeper operating-system repairs.
4. Run the Windows Network Troubleshooter
Windows 11
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run the available Network and Internet troubleshooter.
- You can also open the Get Help app and search for network troubleshooting.
Windows 10
- Open Settings > Update & Security > Troubleshoot.
- Select Additional troubleshooters.
- Run Internet Connections and Network Adapter.
The troubleshooter may repair disabled services, invalid adapter settings, gateway problems, or DHCP configuration errors automatically. Microsoft currently directs Windows 11 users toward the automated Network and Internet troubleshooter in the Get Help app as an early diagnostic step.
5. Disable VPNs, Proxies, and Third-Party Network Filters
VPN clients, proxy servers, antivirus web shields, parental controls, and corporate filtering tools install components that sit between Windows and the internet. When one of those components crashes or points to an unavailable server, Wi-Fi can remain connected while websites stop loading.
- Disconnect any active VPN.
- Open Settings > Network & internet > Proxy.
- Turn off manual proxy settings unless your organization requires them.
- Temporarily pause third-party web filtering or firewall software for testing.
- Reconnect to Wi-Fi and test again.
Do not leave security software disabled. If disabling it restores access, update, repair, or reinstall that application and then turn its protection back on.
6. Make Sure IP and DNS Assignment Are Automatic
Most home networks use DHCP to assign IP addresses, gateways, and DNS servers automatically. An old static configuration from a workplace, school, lab, or previous router can prevent internet access.
- Press Windows + R.
- Enter
ncpa.cpland press Enter. - Right-click Wi-Fi and select Properties.
- Double-click Internet Protocol Version 4 (TCP/IPv4).
- Select Obtain an IP address automatically.
- Select Obtain DNS server address automatically.
- Click OK and reconnect.
Automatic DHCP is the normal choice for home users unless a network administrator has deliberately supplied static values. Windows also provides IP-assignment controls through the Network & internet section of Settings.
7. Reset Winsock, TCP/IP, DHCP, and DNS
Windows networking depends on several software layers. If one becomes corrupted, resetting the stack can restore communication without removing personal files.
- Search for Command Prompt.
- Right-click it and choose Run as administrator.
- Run the following commands one at a time:
Restart the computer after the commands finish. Winsock reset repairs the interface used by network-aware applications, while the TCP/IP reset rebuilds core protocol settings. Releasing and renewing requests a fresh DHCP lease, and ipconfig /flushdns clears cached domain-name records. Microsoft includes this command sequence in its Windows Wi-Fi troubleshooting guidance and documents DNS flushing as a method for discarding stale or negative resolver-cache entries.
If ipconfig /renew reports that the media is disconnected, confirm that Wi-Fi is enabled and connected before running it again.
8. Test a Different DNS Server
If you can reach numeric IP addresses but ordinary website names fail, DNS may be the problem. DNS converts names such as example.com into addresses computers can route.
- Press Windows + R and enter
ncpa.cpl. - Right-click Wi-Fi and select Properties.
- Double-click Internet Protocol Version 4 (TCP/IPv4).
- Select Use the following DNS server addresses.
- For testing, enter one trusted public pair:
- Cloudflare:
1.1.1.1and1.0.0.1 - Google Public DNS:
8.8.8.8and8.8.4.4
Click OK, flush DNS again, and test the connection. If nothing changes, return DNS assignment to automatic rather than collecting experimental settings like souvenirs.
9. Disable and Re-enable the Wi-Fi Adapter
- Press Windows + R.
- Enter
ncpa.cpl. - Right-click the Wi-Fi adapter and select Disable.
- Wait 10 seconds.
- Right-click it again and select Enable.
This restarts the adapter and its Windows binding without requiring a complete reboot.
Check power management
- Open Device Manager.
- Expand Network adapters.
- Open the Wi-Fi adapter’s properties.
- Select the Power Management tab.
- Clear Allow the computer to turn off this device to save power, if available.
This is especially useful when the error appears after sleep, hibernation, or long idle periods.
10. Update, Roll Back, or Reinstall the Wi-Fi Driver
A Windows update can expose an old driver defect, while a newly installed driver can introduce a fresh one. That is why both updating and rolling back are valid fixes, depending on when the problem began.
Update the driver
- Open Device Manager.
- Expand Network adapters.
- Right-click the wireless adapter.
- Select Update driver.
For laptops, the safest first choice is often the driver supplied for the exact computer model by Dell, HP, Lenovo, ASUS, Acer, Microsoft Surface, or another system manufacturer. Those packages may include device-specific power and antenna settings.
Roll back a recent driver
Open the adapter’s Properties > Driver tab and select Roll Back Driver if the button is available. Use this when the problem started immediately after an update.
Reinstall the driver
- Download the correct driver before removing the existing one.
- In Device Manager, right-click the Wi-Fi adapter.
- Select Uninstall device.
- Choose the driver-removal option if appropriate and available.
- Restart Windows.
- Install the downloaded manufacturer driver if Windows does not restore a working version.
Microsoft and Intel both document uninstalling and reinstalling wireless adapter drivers as a repair for persistent Wi-Fi failures. Intel’s clean-installation process also recommends obtaining the replacement package before removing the active driver.
11. Perform a Windows Network Reset
Network reset removes and reinstalls network adapters, then restores many networking components to their defaults. Use it after the targeted fixes above, not as the opening act.
Windows 11
- Open Settings > Network & internet.
- Select Advanced network settings.
- Choose Network reset.
- Click Reset now.
Windows 10
- Open Settings > Network & Internet.
- Select Status.
- Click Network reset.
- Select Reset now.
The computer will restart. You will need to reconnect to Wi-Fi, and Windows may classify the network as public again. VPN clients, virtual switches, Hyper-V components, and other specialized networking software may require reconfiguration afterward. Current Dell and ASUS support guidance uses the same Windows 11 path through Advanced network settings and Network reset.
12. Check the Router and Modem
If multiple devices fail, stop blaming the Windows laptop. It has suffered enough.
- Verify that the modem or gateway shows a normal online status.
- Check whether the router has received a WAN or internet IP address.
- Reseat Ethernet and coaxial or fiber connections.
- Install router firmware only from the manufacturer’s official interface or support page.
- Confirm that DHCP is enabled.
- Check that access control, MAC filtering, and parental controls are not blocking the PC.
- Use WPA2 or WPA3 security rather than obsolete WEP or TKIP modes.
- Test the 2.4 GHz band if 5 GHz or 6 GHz is unstable or out of range.
Do not factory-reset the router unless you know the ISP credentials and can rebuild the Wi-Fi configuration. A factory reset can turn a manageable outage into an evening-long networking escape room.
13. Use IP and Ping Tests to Find the Failure
Open Command Prompt and enter:
Locate the Wi-Fi adapter and examine its IPv4 address and Default Gateway.
- An address beginning with
169.254usually means Windows could not obtain a usable address from a DHCP server. - A normal home-network address commonly begins with
192.168,10, or sometimes172.16through172.31. - A missing default gateway means Windows has no route beyond the local connection.
Microsoft identifies the 169.254.0.0/16 range as Automatic Private IP Addressing, which Windows uses when automatic addressing is enabled but a DHCP server cannot be reached.
Ping the router
Replace the example address with the Default Gateway shown by ipconfig:
If the gateway replies, the PC can communicate with the router. The remaining problem is more likely to involve the modem, ISP, router WAN connection, or DNS. Microsoft uses the default-gateway ping test for this exact distinction.
Test an external IP address
If the external IP replies but websites do not open by name, investigate DNS. If the router replies but the external IP does not, investigate the router’s WAN connection or ISP.
14. Generate a Windows Wireless Network Report
For recurring failures, Windows can create a detailed HTML report containing recent wireless sessions, disconnect reasons, adapter information, driver versions, and network profiles.
- Open Command Prompt as administrator.
- Run:
Windows saves the report as an HTML file and displays its location. Open it in a browser and inspect the session chart for repeated authentication, driver, or connectivity failures. Microsoft describes the report as a tool for analyzing Wi-Fi problems and reviewing stored wireless profiles and recent events.
When Should You Contact the ISP or PC Manufacturer?
Contact your ISP when all devices are offline, the modem cannot achieve an online state, the router receives no WAN address, or the connection repeatedly drops at the same time every day.
Contact the computer manufacturer when the wireless adapter disappears from Device Manager, repeatedly reports an error code, fails on every network, or remains broken after a clean driver installation and network reset.
A USB Wi-Fi adapter can also serve as a useful diagnostic tool. If the USB adapter works normally while the internal card does not, the internal adapter, antenna connection, or its driver is probably responsible.
Experience-Based Lessons From Common “No Internet, Secured” Cases
The most useful troubleshooting experience comes from recognizing patterns rather than memorizing an enormous menu of commands. The following composite scenarios reflect problems that repeatedly appear in home and small-office support. They are representative examples, not claims about one particular computer.
Case 1: The connection fails after the laptop wakes up
A laptop works perfectly in the morning, goes to sleep during lunch, and wakes with “No Internet, secured.” Phones on the same Wi-Fi continue working. Rebooting fixes the laptop, but only until the next sleep cycle.
This pattern usually pushes power management and the adapter driver to the top of the suspect list. Disabling and re-enabling the adapter may restore access immediately. Clearing the option that allows Windows to turn off the device can prevent the recurrence. Updating the laptop manufacturer’s Wi-Fi and chipset drivers is more useful here than repeatedly resetting the router, which was never the guilty party.
Case 2: Every device loses internet at once
A Windows PC shows the error, two phones say “Connected without internet,” and a streaming television stops streaming at the most dramatic moment possible. Because several unrelated devices failed together, changing the Windows DNS settings would be mostly theatrical.
The efficient move is to inspect the modem and router, restart them in sequence, and check for an ISP outage. If the router has no WAN address or the modem’s online indicator never stabilizes, the failure is upstream of the PC. This is why checking another device should happen before opening Device Manager.
Case 3: Numeric addresses work, but websites do not
The computer can ping the router and an outside IP address, yet browsers cannot open ordinary domain names. That combination strongly suggests a DNS-resolution problem. Flushing the DNS cache and temporarily testing a known public resolver can confirm the diagnosis. If the public resolver works, the router or ISP-provided DNS server deserves attention.
The important lesson is that “the internet” is not one single mechanism. Radio connectivity, local routing, internet routing, and name resolution are separate layers. One can fail while the others remain perfectly healthy and deeply confused about why they are being blamed.
Case 4: A mobile hotspot works, but home Wi-Fi does not
A Windows laptop connects successfully to a phone hotspot but displays “No Internet, secured” on the home router. This result confirms that the wireless hardware can associate with a network and pass internet traffic. The likely causes narrow to the saved home Wi-Fi profile, router security compatibility, DHCP configuration, access controls, or a problem limited to one router band.
Forgetting and recreating the Wi-Fi profile is a sensible first move. Testing 2.4 GHz instead of 5 GHz can reveal a range or compatibility problem. Router logs may also show that the computer is being rejected, blocked, or assigned a conflicting address.
Case 5: The problem begins immediately after an update
When connectivity fails directly after Windows or a driver update, timing is evidence. It does not prove the update is responsible, but it makes driver rollback and clean reinstallation reasonable early steps.
A common mistake is uninstalling the adapter before downloading the replacement package. That can leave the user with no connection and no convenient way to retrieve the driver. Download the correct package first, or keep Ethernet, USB tethering, or another computer available.
The practical lessons
Change one thing at a time and test after each change. Record static IP, VPN, proxy, and specialized adapter settings before resetting them. Do not factory-reset a router merely because a single laptop is unhappy. Do not disable IPv6 permanently as a generic cure without evidence of an IPv6-specific compatibility problem. Most importantly, use test results to decide the next step.
A phone that works on the same network tells you something. A hotspot that works tells you something else. A successful gateway ping, a failed external ping, or a 169.254 address each narrows the search. Troubleshooting becomes much faster when every test answers a question instead of merely adding another reboot to the afternoon.
Conclusion
The “No Internet, secured” Wi-Fi error usually does not mean the wireless password is wrong. It means Windows reached the local Wi-Fi network but could not complete the path to the internet.
Start by testing other devices, reconnecting to the network, and restarting the modem and router. Then move through DHCP, DNS, TCP/IP commands, adapter settings, driver repairs, and finally a full network reset. When several devices fail together, investigate the router or ISP. When only one PC fails on every network, investigate its driver or hardware.
Note: Before performing a network reset, driver removal, or router reset, save any required static IP addresses, VPN settings, Wi-Fi passwords, and business network configuration. Managed workplace or school computers should be handled according to the organization’s IT policies.
