Wi-Fi Connected but No Internet on Windows 11: A Methodical Fix

Goal: “Connected, no Internet” does not describe one single failure. The PC may be associated with the Wi-Fi access point while DHCP, gateway routing, DNS, a captive portal, VPN, proxy, router, or ISP is failing. This guide follows the connection path in order so you can identify the layer that is broken before resetting everything.

Quick steps

Test the same Wi-Fi on a second phone or computer.
Restart the affected PC and, if every device is affected, restart the router/modem according to the provider’s instructions.
Check that Windows received a normal IP address and default gateway.
Test the gateway, then an Internet IP, then DNS resolution.
Temporarily disable a VPN or proxy only for comparison, then restore it if it was required.
Use Windows Network Reset only after targeted tests fail.

Expected result: you know whether the failure is local Wi-Fi, DHCP, gateway, Internet reachability, DNS, VPN/proxy, or the upstream connection.

What you need before you start

Access to the Wi-Fi network and password if you may need to forget and rejoin it.
A second device for comparison.
Any corporate VPN or proxy settings written down before you change them.
Administrator access only if a later repair step specifically requires it.

Real-world illustration — Wi-Fi Connected but No Internet on Windows 11: A Methodical Fix

Step 1: compare with another device

If no device on the same Wi-Fi can reach the Internet, the PC is probably not the main problem. Check the router’s WAN status and the ISP’s service state. If every other device works, focus on the Windows PC. If only one browser fails while other applications work, investigate that browser or proxy configuration before calling it a complete network outage.

Step 2: inspect Windows network state

Run the following in PowerShell without administrator rights. The commands are read-only. Replace ADRESSE_PASSERELLE with the IPv4 default gateway displayed by the first command; the placeholder means “gateway address.”

Get-NetIPConfiguration
Test-NetConnection -ComputerName ADRESSE_PASSERELLE -InformationLevel Detailed

If there is no normal IPv4 address or no gateway, investigate DHCP and the local connection. If the gateway responds but external destinations do not, the problem is farther upstream. If the gateway itself does not respond, focus first on Wi-Fi signal, driver state, and the router.

Step 3: test DNS separately

A DNS failure can make the Internet look completely broken even when IP connectivity works. Run this read-only PowerShell query:

Resolve-DnsName example.com

A successful response with A/AAAA records shows that name resolution is working. If DNS repeatedly fails while IP connectivity works, investigate DNS settings, VPN filtering, security software, or the resolver supplied by the network.

A compact three-layer test

The following preserved block collects the active configuration, tests Internet reachability by IP, then tests DNS. Run it in PowerShell without administrator rights. It changes nothing.

$cfg = Get-NetIPConfiguration | Where-Object IPv4DefaultGateway
$cfg | Select-Object InterfaceAlias,IPv4Address,IPv4DefaultGateway,DNSServer
Test-NetConnection 1.1.1.1 -InformationLevel Detailed
Resolve-DnsName example.com

Interpret the results in order: configuration first, IP connectivity second, DNS third. This prevents you from blaming DNS when the PC does not even have a usable gateway.

Captive portals, VPNs, and proxies

Hotel, airport, school, and guest Wi-Fi may require a browser sign-in page. Open a browser and complete the captive portal before changing DNS. A VPN can also install routes and DNS settings that fail when the VPN service is unavailable. Compare behavior with the VPN disconnected, but if it is a required corporate security control, restore it after the test and contact the administrator rather than bypassing it permanently.

Network Reset is a last-level repair

Windows Network Reset removes and reinstalls network adapters and returns many settings to defaults. It can require VPN clients, virtual switches, or custom network configuration to be set up again. Microsoft presents it as a later troubleshooting step, not the first click. Record important configuration before using it.

Common symptom table

Symptom	Clue	Next action
Captive portal	Public Wi-Fi, browser redirects	Open portal and authenticate
169.254.x.x address	No DHCP lease	Check router/DHCP, forget and rejoin Wi-Fi
VPN-related failure	Problem disappears when VPN is off	Check VPN client, routes, and DNS
Only one Wi-Fi band works	2.4 or 5 GHz differs	Check range, compatibility, and driver
Fails after sleep	Adapter toggle temporarily fixes it	Update Windows and the manufacturer driver

Rollback after DNS or proxy experiments

If you manually changed DNS or proxy settings during troubleshooting, restore Automatic (DHCP) or restore the exact values you recorded. Do not leave several experimental changes in place because you will no longer know which one fixed—or created—the problem.

How to verify that it works

The PC has a valid IP and gateway.
The default gateway is reachable.
An external IP is reachable.
DNS resolution returns records.
The same sites work in more than one application.

Common problems and fixes

Wi-Fi is strong but no Internet: signal strength only proves the radio link; continue with gateway and DNS tests.
Only this PC fails: forget/rejoin the network, inspect VPN/proxy, and check the network driver.
Every device fails: focus on router/ISP instead of reinstalling a PC driver.
DNS change seemed to help: confirm the original resolver was really failing before leaving a manual DNS configuration permanently.

Safety and precautions

Do not disable the firewall or security software permanently to “test the Internet.”
Do not run downloaded network-reset scripts from unknown websites.
Back up corporate VPN/proxy settings before Network Reset.

Frequently asked questions

Why can Windows say “connected” when the Internet is down?

Because Wi-Fi association with the access point is only one part of the path. Routing, DNS, portal authentication, or the ISP can still fail.

Should I change to a public DNS immediately?

No. Test DNS first. Changing several parameters at once hides the real cause.

When should I use Network Reset?

After targeted checks and simpler fixes have failed, and after saving any special network configuration you will need to restore.

Separate Wi-Fi association from Internet access

“Connected, no Internet” means the radio link to the access point may be working while DHCP, gateway, DNS, VPN/proxy, captive portal, or ISP connectivity fails. First test another device on the same Wi-Fi. Then compare the affected PC on another network or mobile hotspot. This quickly tells you whether the fault follows the PC or the network.

Check the assigned IP, default gateway, and DNS servers before resetting anything. If you have an address beginning with 169.254, DHCP likely failed. If the gateway responds but domains do not, focus on DNS. If every device fails, reboot/inspect the router/ISP rather than reinstalling the Windows adapter.

Reset only after evidence

A network reset removes/recreates adapters and forgets some network configuration. Record VPN, static IP, virtual adapters, and enterprise Wi-Fi details first. After reset, test a simple known network before restoring every custom setting.

Final checklist

Second device compared.
IP and gateway present.
Gateway tested.
External IP tested.
DNS tested.
VPN/proxy/captive portal considered.
Network Reset reserved for the end.

Key takeaways

The method: test the path in order—local connection, gateway, Internet IP, then DNS.

The key principle: “connected” describes the Wi-Fi link, not the health of every service between your PC and the Internet.

Official sources and references

Image credits

Voir la vidéo sur YouTube

Rechercher dans ce blog

0bamo0 - Android , Projets , Open Source