Wi-Fi connected but no internet in Windows 11?

“Connected” and “online” are different states

Windows can stay associated with the Wi-Fi router even when traffic cannot get past the local network. The router may have lost its upstream connection. The PC may not have received a usable address or default gateway. DNS may be unable to turn a name into an address. A hotel or café may be waiting for a captive-portal sign-in. Or one app may be blocked while the rest of the connection works.

That is why a full reset is a poor first test. It changes several layers at once and can erase the evidence that would have told you which layer failed.

Start with two comparisons

1. Test another device on the same Wi-Fi. Use a phone or another computer and open more than one trusted site or service. Turn off mobile data on the phone for this test so it cannot hide a failed Wi-Fi internet path.
2. Test the affected PC on another known-safe network. A personal hotspot or trusted second network is enough. Do not use an unknown public network for sensitive work.

These two results split the problem quickly:

• Every device fails on the original Wi-Fi: the router, modem, upstream service, or ISP is the stronger branch.
• Only the Windows PC fails on that Wi-Fi but works elsewhere: compare saved network settings, captive portal, address assignment, VPN, proxy, and network-specific policy.
• The Windows PC fails on more than one network: focus on the PC's adapter, Windows configuration, security software, and application scope.
• Only one app or site fails: the general internet path may be fine; troubleshoot that app, account, service, or destination.

Capture the state before fixing it

Write down the Wi-Fi network name, the time, whether the icon says “No internet,” which apps fail, whether a VPN is connected, and whether Windows recently updated or the laptop recently changed networks. Do not publish an unredacted network report or command output; it may include device, network, domain, or address details.

Open Command Prompt and run:

ipconfig /all

Find the active Wi-Fi adapter. Record its IPv4 address, default gateway, DHCP state, and DNS servers. Ignore disconnected adapters so a VPN, virtual switch, or old Ethernet entry does not send you down the wrong branch.

If the address begins with 169.254

Microsoft says a 169.254.x.x address means Windows did not get the expected address from the router. That is a DHCP or local-network clue, not a DNS clue. Reconnect the Wi-Fi once and compare another device. If the router is yours and other devices are also affected, restart it using the maker's normal instructions. If it is managed, contact whoever runs the network.

If there is no default gateway

The PC does not have the normal route off its local segment. Check whether the active adapter is the one you expected, whether a manual address was left behind, and whether the network requires a managed configuration. Do not invent an address or copy settings from another computer.

If the address and gateway look normal

Test the gateway address shown by ipconfig /all:

ping YOUR_GATEWAY_ADDRESS

A reply supports local reachability. No reply can point toward the local path, but it is not absolute proof because some devices block ping. Pair it with the other-device comparison and the router's status before drawing a conclusion.

Check the captive portal before changing Windows

Hotels, airports, apartments, campuses, and guest networks may let the PC join Wi-Fi but block internet access until you accept terms or sign in. Open the Windows network panel and look for a sign-in prompt. Then open a normal browser window and visit the network operator's documented sign-in page if one is provided.

Do not bypass a portal, certificate warning, paywall, or access policy. If the sign-in page does not appear, forget-and-rejoin can be reasonable on a personal device only after you confirm the password and record any custom network settings.

Separate DNS from the wider connection

DNS translates names such as microsoft.com into addresses. A DNS problem can make browsers report that sites cannot be found even though the local gateway and upstream connection still work.

Run a lookup using the DNS server Windows is currently configured to use:

nslookup microsoft.com

If the lookup times out while the gateway and other direct connectivity evidence look healthy, DNS becomes the stronger branch. Microsoft notes that DNS failures can sit on the client, the DNS server, or a device between them. Do not immediately replace a work, school, parental-control, or security DNS setting with a public resolver.

If name lookup is the only broken layer, clearing the local resolver cache is a narrow reversible test:

ipconfig /flushdns

Repeat the same lookup afterward. A DNS cache clear does not repair a missing gateway, router outage, or failed ISP link.

Check VPN and proxy state without tearing it down

Open Settings > Network & internet and record the VPN and Proxy state. A stale manual proxy, an unresponsive VPN tunnel, or an organization policy can affect some or all traffic. On your own unmanaged PC, disconnect a VPN through its normal app and repeat one comparison. Restore the prior state if nothing changes.

Do not uninstall the VPN, delete certificates, turn off endpoint security, or remove a company profile. Those changes can break access and weaken security without proving the cause.

Use DHCP renewal only for the DHCP branch

If the PC has a 169.254 address or an expired DHCP state while other devices receive normal addresses, save the current output, then use an elevated Command Prompt:

ipconfig /release
ipconfig /renew

This temporarily drops the current IP configuration and asks the DHCP server for a new one. It is not a general internet repair. Do not run it during a remote session, and do not use it on a manually configured or managed adapter without approval.

If only one app or website fails

Confirm that another browser and more than one unrelated trusted site work. Check the affected service's official status page, then its sign-in, extension, certificate, firewall rule, and update state. A one-app failure does not justify resetting every network adapter.

If Wi-Fi itself drops, vanishes, or reconnects repeatedly, use the separate Windows 11 Wi-Fi disconnect guide. That article owns signal, roaming, sleep, adapter, and wireless-report evidence; this one assumes the Wi-Fi association stays up.

Use Windows Network reset last

Microsoft describes Network reset as a last step. In Windows 11, it is under Settings > Network & internet > Advanced network settings > Network reset. It removes installed network adapters and their settings, then reinstalls the adapters after restart. It may also leave known connections on a public network profile.

Before approving it, save:

• Wi-Fi names and passwords you are authorized to keep
• VPN client and profile details
• Hyper-V, WSL, container, or other virtual-switch configuration
• manual IP, DNS, proxy, and route settings
• the before-state tests and the reason reset is the next step

After restart, reconnect once and repeat the same device, network, address, gateway, and DNS checks. “It works now” is useful, but a before-and-after record is what keeps the next failure from becoming another blind reset.

Build a useful support record

• Windows edition and full build
• laptop or adapter model and driver version
• network name, location type, and whether it uses a portal
• another device on the same Wi-Fi and this PC on another network
• redacted IPv4, gateway, DHCP, and DNS state
• gateway ping and DNS lookup results
• VPN, proxy, recent update, and one-app-versus-all-app scope
• each change made and the exact retest result

Leave out public IP addresses, Wi-Fi passwords, certificate details, usernames, and organization-specific data when sharing the record.

Where OmniMend fits

OmniMend for Windows can help keep the affected adapter, network state, recent system changes, and before-and-after results together while you work through the supported checks. It does not repair a router or ISP outage, bypass a captive portal or organization policy, or guarantee that a reset will restore access.

Review what OmniMend can and cannot inspect, use the help center, or browse the evidence-first guide library. For a problem that began during a Windows update, preserve that timeline and use the separate Windows 11 update guide.