A USB Wi‑Fi adapter can show as connected while websites still fail. That usually means the wireless link is up, but something else is broken: DNS, the default gateway, a proxy, a captive portal, the router, or the adapter/USB port itself. Start with the fastest split test: check whether the PC has a valid IP address, default gateway, and DNS server, then test whether the gateway responds before you touch drivers. In most cases, that tells you whether you should fix the PC, the router, or the adapter.
What this symptom usually means
Connected but no websites load usually means the adapter joined the Wi‑Fi network, but the computer still can’t reach the internet cleanly. The link can look healthy even when name lookup, routing, or a login page is blocking traffic.
A useful split test is to separate the failure into one of five buckets: DNS, gateway, proxy, captive portal, or adapter/driver trouble. If the adapter shows connected but browser tabs spin forever, don’t assume the radio is bad. First check whether the PC can reach the router, then whether it can resolve names, and only then whether the browser or driver is involved.
If only HTTPS sites fail, or only some sites work, that can point to DNS, filtering, browser settings, or a proxy rather than a dead Wi‑Fi link. One support case described a USB wireless adapter that connected but would not display any HTTPS sites. That’s a good example of why you should diagnose the path step by step instead of reinstalling drivers first.
Before you start
Use the same PC and the same USB adapter for the first checks, so you can tell whether the problem follows the adapter or stays with the computer. Have a way to compare against another network if you can, such as a phone hotspot or a different Wi‑Fi network.
If the adapter disconnects only after sleep or after the PC has been idle, suspect USB power saving early. When the adapter is in a loose front-panel port, a hub, or an extender, move it to a direct port on the computer before you spend time on software changes.
Check IP, gateway, and DNS first
Open a Command Prompt and look at the network details for the USB Wi‑Fi adapter.
ipconfig /allCheck these items on the adapter’s section:
- A usable IPv4 address
- A default gateway
- DNS servers
If the IPv4 address is missing or looks wrong, the PC may not be getting a proper lease from the router. If the default gateway is missing, web traffic has nowhere to go. If the DNS server is missing or unreachable, websites can fail by name even when the network seems connected.
Next, test the gateway itself. Replace 192.168.1.1 with the gateway shown by ipconfig.
ping 192.168.1.1If the gateway does not respond, the problem is closer to the adapter, USB port, or router than to DNS. If the gateway responds but website names still do not load, DNS or a browser/proxy problem moves higher on the list. A Windows diagnostic in one support case reported that the DNS server was not responding and the default gateway was not available. That’s exactly the kind of result this split test is trying to surface.
Rule out proxy, captive portal, and browser-only problems
If one browser fails but another works, or one browser profile fails while a private window works, the Wi‑Fi connection is probably not the real problem. That usually points to browser settings, an extension, or a proxy that is only affecting part of the system.
Check Windows proxy settings and turn off any proxy you did not set on purpose. A bad proxy can make the connection look alive while every page times out.
A captive portal can also look like “connected but no internet,” especially on hotels, airports, apartment networks, and some public hotspots. If a sign-in page, terms page, or network page keeps appearing, complete that login first. Until you do, the adapter may be connected to Wi‑Fi but still blocked from normal web traffic.
If you are on a network that should not have a portal, test both a plain HTTP site and a normal HTTPS site. If only some sites fail, the issue may be filtering, DNS, or browser handling rather than the Wi‑Fi link itself.
Look for adapter, USB, or driver issues
If the gateway and DNS problem appears only on this USB adapter, or the connection keeps dropping and reconnecting without fully disconnecting, the adapter or USB path may be the cause. USB power saving can also put the adapter into a bad state after sleep, idle time, or a restart.
Start with the least disruptive fixes:
- Unplug the adapter and move it to a different USB port on the same computer.
- Use a direct port on the PC instead of a front-panel port, hub, or extender.
- Watch for the adapter’s activity light, if it has one, to see whether it changes when websites stop loading.
- Open Device Manager, find the adapter, and check its power management settings.
- If Windows is allowed to turn the device off to save power, turn that off and reconnect the adapter.
If changing ports fixes the problem, the original port was probably flaky, underpowered, or a poor match for the adapter. If disabling USB power saving helps, the adapter was likely getting stuck in a bad low-power state. If none of that changes anything, then a driver refresh is reasonable, but only after you’ve saved the current driver details so you can roll back if needed.
If you still have the same symptom after moving ports and disabling power saving, the next reversible step is to reinstall or update the adapter driver from the current official source for that model. Check the adapter maker’s current support page or Windows Update for the latest driver package before you assume an older copy is still the right one.
When the router or network is the real problem
If other devices on the same Wi‑Fi network also cannot load websites, stop blaming the USB adapter. That pattern points to the router, DNS service, parental controls, security filtering, or the internet connection itself.
The cleanest split test is to try the PC on a different network, such as a phone hotspot, or to test another device on the same router. If this USB Wi‑Fi adapter works on a different network, the adapter is probably fine and the router or ISP is the real problem. If every device on the router fails the same way, focus on the router’s DNS settings, filtering, or WAN connection before touching the PC again.
If only this one PC fails while other devices work, the issue is usually local: browser settings, proxy, DNS on the PC, or the adapter driver. If you have already confirmed a valid IP, a reachable gateway, and working DNS, and the problem still stays with this machine, move to a network reset or driver refresh. If a clean test network behaves the same way, stop and compare logs, settings, or another adapter before you buy new hardware.
Verify the fix
Reload a few different websites after each change, not just the one that failed first. You want to see normal browsing again, not just a single page that happened to come back.
Then confirm these points:
ipconfig /allstill shows a valid IPv4 address, default gateway, and DNS server for the USB adapter- The gateway responds to
ping - The browser opens more than one site
- The problem does not return after a reboot or after sleep
If the router responds but names still do not resolve, the fix is not complete yet. If the browser works only in one profile or one browser, the adapter may be fine and the remaining issue is local to that app.
Conclusion
If the adapter is connected but websites still do not load, work the path in order: IP, gateway, DNS, proxy or portal, then USB power and drivers. If that still doesn’t settle it, compare the same adapter on another network before you replace hardware.
Frequently Asked Questions
Why does Wi‑Fi say connected when websites won’t load?
Because the adapter can join the wireless network while the computer still lacks a working path to the internet. The break is often DNS, the default gateway, a proxy, or a captive portal, not the Wi‑Fi link itself.
Should I reinstall the driver first?
No, not first. Check IP, gateway, DNS, browser settings, and USB port behavior before you reinstall anything, because those tests tell you whether the problem is the PC, the router, or the adapter.
How do I tell if it’s DNS or the gateway?
If you can ping the gateway but website names still fail, DNS is a likely suspect. If you cannot reach the gateway at all, the problem is earlier in the chain, usually the adapter, USB path, or router.