Advertisement

MediaTek WiFi adapter connects but websites won’t load

If your MediaTek Wi‑Fi adapter says connected but websites still won’t open, the problem may be DNS, the default gateway, a proxy or VPN, a captive portal, or the driver. This walkthrough helps you test each one in the right order.

Networking 9 min read

If your MediaTek Wi‑Fi adapter says connected but no websites load, the Wi‑Fi link is up. The fault is usually higher up: DNS, the gateway or DHCP, proxy or VPN settings, a captive portal, the router, or the adapter driver. The fastest way to find it is to test a name, an IP address, and another device on the network. Once you know which one fails, the fix usually becomes clear.

What this symptom usually means

A connected Wi‑Fi icon only tells you the radio link is active. It does not prove your PC has a working default gateway, usable DNS servers, or a clean path through Windows.

In practice, this usually falls into four buckets: DNS failure, a bad or missing gateway, a blocked browser path from proxy or VPN settings, or a MediaTek driver problem that keeps traffic from moving cleanly. If every browser fails on every site, think broad path or adapter trouble. If only some sites fail, DNS or filtering is more likely.

Before you start

  • Use a Windows PC where you can open Command Prompt and Settings.
  • Know whether this is your own network or a work or school network, because proxy and VPN settings may be managed there.
  • If you can, have another device ready for comparison.
  • If the network uses a captive portal, be ready to sign in before normal browsing will work.

The fastest three checks

Start with the checks that separate a local PC problem from a router or ISP problem. They are quick, reversible, and each one rules out a whole class of causes.

  1. Check another device on the network. If your phone or another laptop can browse through the same router, the network is probably alive and the fault is more likely on this Windows PC or this adapter. If nothing can browse, look at the router, modem, or ISP first.
  1. Open a site by IP address instead of by name. If an IP address loads but example.com does not, the link is up and DNS is the likely weak point. If the IP address also fails, the problem is farther down the path, such as routing, gateway, proxy, or filtering.
  1. Check Windows’ network status for a real gateway and internet access. In Settings > Network & internet > Wi‑Fi, the connection should show a valid network name and internet access, not just connected to Wi‑Fi. If Windows says connected but no internet, that lines up with a broken route or captive portal rather than a simple signal problem.

If step 1 shows only this PC is failing, keep working on Windows and the MediaTek adapter. If step 1 shows the whole network is down, stop chasing the adapter until the router or ISP is stable.

If IP addresses work but names do not

If an IP address loads but website names do not, DNS is the first place I’d look. DNS turns google.com into an IP address, and when it fails, the browser looks broken even though the Wi‑Fi link is alive.

Start with a DNS flush, then renew the IP lease if the system seems stuck. The flush clears old name lookups from Windows, and a renew can pick up a fresh lease and gateway from the router.

  1. Open Command Prompt as a normal user first. If that does not help or the adapter seems stuck on an old lease, use an elevated prompt.
  1. Run the DNS flush.
Command Prompt
ipconfig /flushdns
  1. Renew the IP lease.
Command Prompt
ipconfig /release
ipconfig /renew

If browsing starts working after the flush, the fault was likely stale DNS rather than the adapter itself. If renewal fails, or Windows gets an address but no usable gateway, the issue is more likely router-side, DHCP-side, or in the adapter’s link to the network stack.

If IP addresses still do not load, DNS is not the main problem. Move on to Windows settings and the adapter path instead of repeating DNS fixes.

Windows and MediaTek settings to inspect

A healthy Wi‑Fi link can still be blocked by Windows settings. The common blockers are a proxy, a VPN, a captive portal that has not been completed, and power-saving behavior that makes the adapter look connected while traffic stalls.

Start with proxy and VPN. A broken proxy can send every browser request to nowhere, and a VPN can fail in a way that leaves Wi‑Fi looking fine in the tray while pages never load. Turn off any VPN first, then check Settings > Network & internet > Proxy and make sure no unexpected manual proxy is enabled.

Next, watch for a captive portal. Some public or guest Wi‑Fi networks need a sign-in page before normal browsing works. If the network is new, open a plain HTTP page or trigger the network sign-in prompt. If a portal is waiting, normal HTTPS sites may appear dead until you log in.

Then inspect the adapter itself. In Device Manager, open the MediaTek Wi‑Fi adapter properties and look for power management settings that let Windows turn off the device to save power. If the adapter keeps disconnecting, reconnecting, or only works briefly after being toggled off and on, that pattern often points to a driver issue rather than a router fault. Reports around MediaTek RZ717 and MT7921 adapters have included intermittent connections and temporary improvement after disabling and reenabling the adapter or reinstalling a driver.

If changing one setting immediately improves browsing, keep that change and test again. If nothing changes, do not stack random tweaks; move to a cleaner network reset or a different network test.

How to prove whether it’s the adapter, the router, or the network

The cleanest way to sort this out is to change one thing at a time and watch which fault moves with it. If the problem follows the adapter across networks, the driver or hardware is the likely cause. If it stays on the same router and only this PC fails, the router or its filters are more likely.

  1. Test the PC on another network, such as a phone hotspot or a different home network. If websites load normally there, the MediaTek adapter is probably not dead. The original router, DNS, or filtering setup is the stronger suspect.
  1. If the problem stays with the PC, update the MediaTek driver first from the laptop maker or the adapter vendor’s current support source. In 2026, check the current official package for your exact model before installing anything. Driver behavior can change by build, and the newest package is not always the best fit for every machine.
  1. If a new driver makes the problem worse, roll it back. That is the fastest reversible test for a driver fault. If rollback is not available or the driver is clearly broken, reinstall the adapter and let Windows load it again, then test before changing anything else.
  1. If another network works and this one still fails, look at the router or access point. Device-specific router filtering, MAC filtering, bad DHCP behavior, or a captive portal that never completed can all make one Windows PC look broken while other devices work.
  1. If the adapter fails on every network, shows repeated reconnects, or only comes back briefly after being disabled and enabled, hardware becomes the likely answer. At that point, replacement is reasonable after you have confirmed the issue is not a bad driver or a bad router path.

If you want the shortest decision path, use this order: another device on the network, an IP address test, DNS flush and IP renew, proxy and VPN checks, then driver update or rollback. That sequence tells you where the break really is instead of guessing at the adapter first.

Verify the fix

After the change, confirm two things: a site loads by name, and another site loads after you close and reopen the browser. If both work, the path is healthy again.

If browsing returns only after a driver change, keep that driver and watch it for a while on the same network and on one other network if you can. If browsing returns only after DNS or proxy changes, the adapter was probably not the root cause.

If the problem comes back after a reboot or after the adapter sleeps, that points back toward driver behavior, power management, or the router path rather than a one-time browser issue.

Conclusion

If you still cannot narrow it down after the IP test and the other-network test, the next best move is to compare the current MediaTek driver against the laptop maker’s official support package and test the adapter on one other network before replacing hardware.

Frequently Asked Questions

Should I reset the Windows network stack if flush DNS and renew IP do not help?

Yes, if the IP address test still fails and proxy or VPN settings are not the cause, a Windows network reset can clear a stuck stack. Use it after the simpler checks, because it will remove saved network state and you will need to reconnect to Wi‑Fi afterward.

How do I know if it is the MediaTek driver and not my router?

It is more likely a driver issue if the problem follows the same PC to another network, if the adapter briefly improves after disable and enable, or if only this adapter fails while other devices on the router work. If several devices fail on the same router, look there first.

Sources