If your Intel AX201 shows as connected to Wi‑Fi but websites won’t load, the link to the router is usually up. The failure is usually somewhere else: DNS, IP assignment, the default gateway, proxy or VPN settings, captive portal handling, or the AX201 driver and power settings. Start by checking which layer fails, then fix the simplest one first instead of reinstalling everything at once. If the problem follows sleep, a driver update, or a router change, that narrows the next step quickly.
What this symptom usually means
If Wi‑Fi says connected but no pages open, your PC joined the access point, but traffic is getting stuck after that. The AX201 may be associated with the router while name resolution, routing, or a Windows setting blocks web access.
A quick way to separate the causes is to compare an IP address with a website name. If an IP works but a name does not, the problem is usually DNS. If neither works, look at IP assignment, gateway access, proxy, VPN, or the adapter and driver path. If the browser is the only thing failing, the issue may be a browser proxy setting or security software rather than the Wi‑Fi link itself.
| What you can still reach | What it usually points to |
|---|---|
| Public IP works, website name fails | DNS |
| Neither IP nor name works | IP assignment, gateway, proxy, VPN, driver, or security software |
| Command-line network tests work, browser does not | Proxy, VPN, browser settings, or security software |
| The same SSID fails on every device | Router, captive portal, modem, or ISP |
If the adapter says connected but the browser never finishes loading any site, people often call that “Wi‑Fi works but the internet doesn’t.” The connection is real. The usable path to the web is what’s broken.
Before you start
- Check one other device on the same Wi‑Fi. If it also fails, stop focusing on the AX201 first and check the router, modem, captive portal, or ISP.
- If this is a work or school PC, proxy, VPN, and security settings may be managed by policy. Changing them without approval can make access worse.
- If the problem started only after sleep or resume, a driver update, or a router firmware change, keep that in mind while you test. That pattern often matters more than the adapter model name.
- If you are on a captive network such as a hotel, guest, office, or public Wi‑Fi, complete the sign-in page before assuming the connection is broken.
A captive portal can look like a normal Wi‑Fi connection until the first web request is intercepted. In that case, normal browsing will fail until the sign-in page opens or you manually trigger it with a browser on the Windows PC.
Fix it in the right order
- Test whether IP access works.
Open Command Prompt and try a public IP, then a name.
ping 1.1.1.1
ping www.microsoft.comIf the IP ping works but the name ping fails, the problem is likely DNS. If both fail, the issue is lower down, such as IP assignment, gateway access, proxy, VPN, driver, or security software. If both work but browsers still fail, move to proxy, VPN, and browser settings.
- Check whether the PC got a valid address, gateway, and DNS server.
Run ipconfig /all and look at the active wireless adapter.
ipconfig /allIf you see an address such as 169.254.x.x, Windows did not get a proper address from DHCP, so this is not just a DNS issue. If the default gateway is missing, wrong, or blank, the PC cannot reach the router correctly. If the DNS servers are blank or clearly wrong, fix DNS before changing anything else.
- Fix DNS only if names fail but IPs work.
Change the DNS server in Windows or in the router if that is how your network is managed. If this is a managed network, match the DNS policy the network expects instead of guessing. After the change, retry the same ping tests and then load a few websites.
- Check proxy and VPN settings.
Proxy leftovers are a common reason a PC can connect to Wi‑Fi but not browse. A manual proxy can block normal web traffic while leaving the wireless link untouched.
Settings > Network & internet > ProxyTurn off any manual proxy you did not set on purpose, then disconnect any VPN completely and test again. A browser extension is not the same thing as a full VPN client, so check both if you use one. If command-line network tests work but the browser still fails, proxy or browser routing is a strong suspect.
- Check the Intel AX201 driver and adapter settings.
Open Device Manager and inspect the Intel AX201 entry for warning symbols, recent driver changes, or anything that suggests the adapter is not loading cleanly.
Device Manager > Network adapters > Intel(R) Wi-Fi 6 AX201 160MHzOpen the adapter’s Properties and look at Power Management and Advanced settings. On some systems, aggressive power saving can leave the link up while traffic becomes unstable after sleep or resume. If the problem started after a driver or firmware change, compare the installed driver against the current official Intel or PC maker support page for your exact model before you replace anything.
If reinstalling is already on your mind, do not assume uninstalling in Device Manager will always complete cleanly. Intel notes that on some HP systems, a background process called HotKeyServiceUWP.exe can block actual removal or ejection of the adapter at the kernel level, and the normal uninstall can appear to succeed while the driver remains locked in memory. Intel also notes that the Windows 11 removal wording can differ from Windows 10 during that process. If the adapter is disappearing together with Code 10 or Code 43, you may be looking at a different problem than simple no-web browsing.
- Reset the Windows network stack if the basic checks do not fix it.
A network stack reset is the next reversible step when Windows networking seems stuck. It can clear bad Winsock state, reset parts of TCP/IP, and flush DNS so Windows rebuilds the path the browser uses.
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsRestart the PC after running those commands. If browsing works only after the restart, the issue was in Windows networking state rather than the Wi‑Fi radio. If nothing changes, do not keep repeating resets; move back to router, proxy, VPN, security software, firmware, or compatibility checks.
- Check security software, firmware, and router compatibility.
Third-party security suites can filter web traffic even when Wi‑Fi looks healthy. If you use one, test carefully and only if you know how to restore it safely. Router firmware and AX201 compatibility can also matter, especially if the issue appears only after sleep, only on one band, or only on one router.
If the AX201 works on another network but not your usual router, the router side becomes more likely. If the adapter keeps dropping, disappears, or reports a device error after driver changes, that points away from a simple DNS problem and toward the driver, power settings, firmware, or compatibility. If a driver reinstall fails in a way that still leaves the adapter locked in memory, the cause may be software interference rather than bad hardware.
How to confirm the fix worked
You have the right fix when three things line up: the PC gets a normal IP address, ping works to both an IP and a name, and multiple websites load in a browser.
If only this PC was affected and the checks now pass, stop changing Wi‑Fi settings. If every device on the SSID was failing and now all of them work, the router, captive portal, modem, or ISP was the real problem. If command-line tests work but the browser still does not, keep looking at proxy, VPN, browser, or security software settings.
If the failure comes back after sleep or after a driver update, treat that as a strong clue that you are dealing with driver, power management, or router compatibility rather than a dead Wi‑Fi radio.
Conclusion
If the AX201 still connects but pages won’t load after these checks, compare the installed driver and adapter behavior against the current official Intel or PC maker support information for your exact model. Then test the same PC on a different network before you decide it is hardware.
Frequently Asked Questions
If ping works but websites still do not load, what does that mean?
That usually means the network link and basic routing are alive, but name resolution, proxy settings, or browser traffic handling is broken. In practice, that points first to DNS or a proxy/VPN problem, not to the Intel AX201 radio itself.
Should I reinstall the Intel AX201 driver right away?
No. Start with DNS, proxy, VPN, and the network stack first, because those are safer and often faster to fix. Reinstall the driver only if the failure follows sleep, updates, adapter warnings, or you have ruled out the Windows network settings.
Sources
- Intel(R) Wi-Fi 6 AX201 160MHz driver repeatedly failing - Intel Community (community.intel.com)