“Windows connected to Wi-Fi but no internet” means the PC has joined a wireless network, but Windows cannot confirm a working path beyond it; Microsoft describes the No Internet state as local-network access without confirmed internet access.［1］ First find out whether the failure follows this PC, this Wi-Fi network, or one app, then check the captive portal, the active adapter's address and gateway, DNS, and proxy before any reset. The Connected label does not prove that the router has internet access, that a portal sign-in is complete, or that Windows has a usable address, gateway, DNS server, or application path.

Key Takeaways:

First determine whether the failure follows this PC, this Wi-Fi network, or one app.

Read the active adapter's address, gateway, DNS, and proxy state before changing them.

Use network reset only after narrower checks fail and every required setting is saved.

If several devices fail or you are not sure which layer is broken, the Device and App Troubleshooting Guide sets out the wider triage order.

Step 1: Map “Windows connected to Wi-Fi but no internet” before changing anything

Run four quick checks and write down the result:

Comparison	Likely branch
Another device fails on the same Wi-Fi	Router, portal, or ISP; use the router no-internet guide.
This PC works on a trusted hotspot	Original Wi-Fi, portal, DHCP, or router policy.
Websites work but one app fails	Use the Windows app connectivity guide.
This PC fails on every network	Windows adapter, address, proxy, security policy, or driver.

Keep the network name, exact Windows status, time, and last known change. Do not factory-reset the router when other devices work.

Repeat each comparison only once or twice. A result that changes on every attempt may indicate weak signal, roaming between access points, an unstable router, or an upstream outage rather than a fixed Windows configuration error. Note whether the failure began after sleep, travel, an update, a new security tool, or a network change, but do not assume that the latest event caused it.

Before continuing, pause downloads and other traffic that could confuse the test. Keep one known website and one known working device as controls. This makes later results comparable and avoids treating a single unavailable website as proof that the whole internet connection is down.

Step 2: Check the visible Wi-Fi state and captive portal

Select the network icon (in Windows 11, the quick settings area) and confirm Wi-Fi is on, Airplane mode is off, and the intended network says Connected. Microsoft's connection guide shows the normal flow from that icon.［2］ If the signal is weak, move closer or compare another supported band; 2.4 GHz, 5 GHz, and 6 GHz have different range and compatibility tradeoffs.

Open a fresh browser window and visit the network operator’s normal sign-in page if one is supplied. Hotel, airport, school, and guest networks may require a captive-portal agreement. Never enter account credentials into a page whose network or operator you do not recognize.

If the portal does not appear, disconnect and reconnect to that one network after confirming its credentials are available. Close any old portal tab and retry with a normal browser window. A private or managed network may intentionally block unsolicited portal detection, so use only instructions from the network owner rather than guessing an address or installing a certificate.

Also compare signal quality with the PC in a fixed location. A connection that works close to the access point but fails at the desk is a coverage or band-selection problem, not evidence for a Windows network reset. Record that distinction before moving on.

Step 3: Read the address and gateway without changing them

Open Command Prompt and run:

ipconfig /all

ipconfig /all displays the full TCP/IP configuration, including adapter addresses, default gateways, DHCP, and DNS information.［3］ Find the active Wi-Fi adapter, not a disconnected Ethernet, virtual, or Bluetooth adapter.

An address beginning 169.254 usually means Windows did not obtain a normal DHCP address. Reconnect once and check router DHCP or administrator policy.
A missing default gateway means the PC has no normal route off the local link.
A plausible address and gateway shift the investigation toward the portal, upstream service, DNS, proxy, policy, or a specific app.

Do not publish the complete output: it can contain device, network, and organization details.

Check the lease and adapter names as a set. A valid-looking address on a disconnected virtual adapter does not describe the Wi-Fi path, and a stale address from an earlier network is not proof that DHCP is currently working. If a company supplied a static address, preserve the address, prefix, gateway, and DNS values exactly; do not replace them with guessed public values.

If support needs evidence, share only the active adapter's state and redact physical addresses, DNS suffixes, organization names, and unrelated adapters. Capture the output before and after one reversible change so the comparison shows what actually changed.

Step 4: Separate gateway, DNS, proxy, and driver branches

If another device works, compare whether the PC can reach the local gateway recorded by ipconfig. A gateway failure supports a local Wi-Fi, address, or adapter branch. A reachable gateway with no internet points farther upstream. If IP destinations work but hostnames fail, continue with a DNS-specific guide rather than changing every network setting.

Use the scope matrix to choose only one branch. A failed local gateway test does not justify changing DNS, and a hostname-only failure does not justify reinstalling the Wi-Fi adapter. If the network works in a different Windows user account, compare per-user proxy and application settings before changing machine-wide configuration.

Review Settings > Network & internet > Proxy. On a managed device, an automatic script or manual proxy may be required; record it and ask the administrator rather than turning it off permanently. If only one app fails while browsers work, remain on the app branch.

In Device Manager, confirm that the wireless adapter exists and has no reported error. Prefer Windows Update or the PC/adapter manufacturer’s official driver. Do not begin by uninstalling the driver: Microsoft recommends having a backup driver available before that later-stage action. Do not globally disable the firewall to test internet access.

When an error code is present, copy it exactly and check the official support path for the PC or adapter model. Avoid generic driver-download sites: a similarly named adapter can use different hardware revisions, and the wrong package can remove the only working recovery path.

Step 5: Use network reset only as a last step

Restart Windows after saving work and apply normal supported updates. If the fault still follows this PC across networks, preserve Wi-Fi credentials, static addresses, proxy details, virtual switches, and organization instructions before considering Network reset. Microsoft calls network reset a last step and notes that it removes adapters and their settings, may require network software to be set up again, and can change network profiles.

Do not combine a network reset with router factory reset, driver removal, and firewall changes. One change at a time preserves evidence and a recovery path.

After a reset, reconnect only to the intended trusted network and restore documented settings one category at a time. Recheck the same control website and comparison device used at the start. If the result is unchanged, stop repeating destructive actions and escalate with the saved before-and-after evidence; the remaining cause may be hardware, policy, router compatibility, or an upstream service.

Summary

First prove whether the failure follows the PC, the network, or one app. Confirm the Wi-Fi state and captive portal, then read the active adapter’s address and gateway. Route the evidence to DHCP, gateway/upstream, DNS, proxy, policy, driver, or app support. Reserve network reset for a confirmed device-side problem after saving every setting needed to reconnect.

FAQ

Why does Windows say Connected when there is no internet?

The PC can be associated with the Wi-Fi access point while the router, portal, address, gateway, DNS, or upstream connection still fails.

What does a 169.254 address mean?

It usually means Windows self-assigned a link-local address because it did not receive a normal DHCP lease. Check the active adapter and network owner before entering a manual address.

Should I forget the Wi-Fi network first?

Only after confirming the password and any enterprise setup are available. Forgetting one network is narrower than resetting every network setting.

Should I restart or factory-reset the router?

A normal restart may be reasonable when several devices fail. A factory reset erases configuration and is not a first response, especially when other devices work.

Can I uninstall the Windows Wi-Fi driver immediately?

No. First confirm the adapter state and obtain the official backup driver. Driver removal can leave the PC without a working way to reconnect.

Does a reachable gateway prove internet access?

No. It proves a local path to the router. The router, portal, ISP, DNS, or destination service can still fail.

Will network reset erase saved settings?

It removes and reinstalls network adapters and resets their settings; related network software may need setup again. Save recovery details first.

What should I send to support when Windows shows Wi-Fi but no internet?

Send the exact status, time, Windows and adapter versions, whether other devices/networks work, and sanitized ipconfig /all findings. Do not send passwords or full private configuration.

When can you reconnect a VPN after a captive portal?

On a hotel or airport Wi-Fi network, joining the access point and completing its sign-in are separate steps. If you were using a VPN when the portal stopped appearing, first preserve any managed connection requirements and, where policy allows, disconnect it while completing the network owner's browser sign-in. Then confirm that an ordinary website works on the same Wi-Fi. A missing DHCP lease or gateway must still be fixed before a VPN has a usable internet path.

Once that baseline works, connect AethoVPN's Windows client to a low-load location and test the same website with the VPN connected. If only that second test fails, record the connection state and return to the working baseline to separate the VPN branch from the original Wi-Fi fault. A VPN does not grant portal authorization, repair the router's upstream service, or make an unfamiliar sign-in page trustworthy. If the client is not on this PC yet, download the Windows client and use the 3-day free trial for that second test.

Disclaimer: Menu names and network ownership vary by Windows release and organization policy. Preserve credentials and managed settings before making changes.

Sources:

Microsoft Support — Fix Wi-Fi connection issues in Windows — https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c
Microsoft Support — Connect to a Wi-Fi network in Windows — https://support.microsoft.com/en-us/windows/experience/connectivity-networking/connect-to-a-wi-fi-network-in-windows
Microsoft Learn — ipconfig — https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig

Sources checked 4 October 2026.

Related Articles:

Windows Connected to Wi-Fi but No Internet: What to Check