Advertisement

MediaTek WiFi adapter shows connected without internet

If your MediaTek Wi‑Fi adapter says connected but Windows shows no internet, the problem may be the router path, DHCP, DNS, or a driver/power setting. This article walks you through the quickest checks first, then the safest Windows and adapter fixes.

Windows 9 min read

A MediaTek Wi‑Fi adapter that shows connected but Windows says there’s no internet usually means the Wi‑Fi link is up, but Windows can’t reach the internet beyond the router. Start with the modem/router path, then check DHCP, IP, gateway, and DNS on Windows. After that, work through safe adapter and network-stack resets. If the problem began after a driver or sleep/wake event, suspect the MediaTek driver or power settings.

What "connected without internet" actually means

On Windows, this status means the PC joined the Wi‑Fi network, but Windows did not confirm a working path to the internet. The cause can be the router, the modem or ISP, Windows networking, or the MediaTek adapter itself.

The signal can look fine while the real failure is elsewhere. The default gateway may not answer. DHCP may not hand out a usable address. DNS may fail even when the Wi‑Fi icon says connected.

If the adapter works on one network but not another, that usually points more toward router compatibility or settings than a dead adapter.

Before you start

Use these quick checks before you change anything on the PC:

  • Test another phone, tablet, or laptop on the same Wi‑Fi.
  • Check the router and modem lights for an obvious internet or WAN fault.
  • If the modem and router are separate, restart the modem first, then the router.
  • Make sure Airplane mode is off and Wi‑Fi is turned on in Windows.
  • If you can, test the Windows PC on a phone hotspot or another known-good network.

If other devices also lose internet on the same network, stop and focus on the router, modem, or ISP path first. If the PC works on another network, the Windows install and adapter are probably fine, and the home router is the more likely blocker.

Check whether the problem is DHCP, gateway, DNS, IPv4, or IPv6

A connected adapter can still be useless if Windows did not get a usable IP address, gateway, or DNS server. The fastest way to check is ipconfig /all, because it shows the address Windows got and whether the router handed out the rest of the network details.

Command Prompt
ipconfig /all

Look for these signs:

  • The adapter has an IPv4 address in your normal home network range, not a self-assigned address like 169.254.x.x.
  • A default gateway is listed.
  • DNS servers are listed.
  • The adapter is shown as connected, not disconnected.

Use the pattern to narrow the fault:

  • No valid IPv4 address or no gateway usually points to DHCP trouble or a router that did not answer correctly.
  • IPv4 looks normal but websites do not open often points to DNS.
  • IPv6 is present but IPv4 is broken can leave some apps and sites failing, even when the Wi‑Fi status looks normal.
  • If both IPv4 and IPv6 look wrong, focus on the router, the adapter driver, or the Windows network stack instead of chasing random settings.

If you want a layer-by-layer check, ping the default gateway first, then a public IP, then a domain name. If the gateway responds but a public IP does not, the break is beyond the router. If the public IP works but a domain name does not, DNS is the likely fault.

Fix the MediaTek adapter and Windows network stack

Work through these in order and stop as soon as the connection comes back. There’s no reason to stack more changes once you’ve found the broken layer.

  1. Disable and re-enable the adapter. Open Device Manager, find the MediaTek Wi‑Fi adapter, disable it, wait a few seconds, then enable it again. This clears a stuck radio state without changing your saved Wi‑Fi profile.
  1. Renew the IP address.

    Command Prompt
    ipconfig /release
    ipconfig /renew

    If Windows gets a fresh lease and the internet returns, the problem was likely DHCP or a stale lease. If renewal fails, the router may not be handing out addresses properly, or the adapter may not be reaching the router cleanly.

  1. Flush DNS.

    Command Prompt
    ipconfig /flushdns

    This helps when the connection exists but name lookups are stale or broken. If IP addresses work but websites do not, this is a low-risk step.

  1. Check the driver version, then update or roll back. Open the MediaTek adapter properties in Device Manager and check the driver tab. If the issue began right after a driver change or Windows update, roll back first if that option is available. If not, install the current driver from the PC maker or the current official source for your exact model and Windows version. Before you install anything, verify the release notes against the official source.
  1. Change the adapter power settings. In Device Manager, open the adapter’s power management settings and turn off the option that lets Windows power it down to save energy. MediaTek adapters can show this exact symptom after sleep, standby, or aggressive power saving, so this is one of the first settings I’d check.
  1. Run Windows Network reset if the stack still looks broken. Windows 10 and Windows 11 both include a Network reset feature that reinstalls network components and clears some saved configuration. It can fix a stuck stack, but it will remove and recreate network adapters, and you may need to reconnect to Wi‑Fi afterward.
Settings path
Settings > Network & Internet > Advanced network settings > Network reset
  1. Use the Windows Network Troubleshooter if the adapter still looks missing or unstable. Microsoft support replies on this MediaTek family point to restarting the computer or running the Network Troubleshooter, including the network adapter troubleshooter, when the chip stops connecting after standby or Windows says no network adapters were found. That isn’t a universal fix, but it can confirm whether Windows still sees the adapter.

If the adapter starts working again after a driver change or power setting change, keep that setup stable for a while. Avoid making more changes unless the symptom returns.

When the problem is probably router-side or hardware

If the PC connects to one Wi‑Fi network but not another, suspect the router first. Common causes include band steering, MAC filtering, access control lists, guest-network restrictions, and security settings that do not play nicely with a specific adapter or driver version.

A router reboot that only fixes the issue briefly often points to DHCP or router firmware behavior rather than a bad adapter. If the same MediaTek card works on a phone hotspot but not your home router, the adapter is usually not the main problem.

Look for these router-side clues:

  • Only one device fails while others stay online.
  • The PC connects to Wi‑Fi but cannot get a valid gateway or DNS server.
  • The failure returns after router restarts or after the router has been up for a while.
  • The problem follows one band, such as 2.4 GHz or 5 GHz, but not the other.

Hardware failure becomes more likely when the adapter disappears from Device Manager, shows a warning icon, or stops reconnecting after reboot and driver repair. User reports on the MediaTek MT7921 family also describe disconnects after sleep and cases where Windows did not present usable Wi‑Fi adapters after wake or reinstall attempts. If you see that pattern, the next step is usually a known-good driver from the PC maker, then hardware diagnosis if the adapter still drops out.

How to verify the fix

After each fix, check the same things you used to diagnose the problem:

  • Open a website on the affected PC.
  • Run ipconfig /all again and confirm the adapter has a valid IPv4 address, default gateway, and DNS server.
  • If you changed the driver or power settings, restart the PC and make sure the adapter still connects after sleep or a reboot.
  • If the problem only happened on one network, reconnect to that same router and see whether the symptom returns.

If the PC reaches websites again and keeps the connection after a restart, the fix held. If it only works briefly or only on some networks, the router setting, driver version, or power behavior still needs attention.

Conclusion

If the adapter says connected but Windows still has no internet, start with the modem/router path and then work down to DHCP, DNS, driver, and power settings. If you still can’t get a valid gateway or the adapter keeps dropping after sleep, the next move is usually a clean driver from the PC maker or a hardware check.

Frequently Asked Questions

How do I know if the problem is my router or the MediaTek adapter?

If other devices on the same Wi‑Fi also lose internet, start with the router, modem, and ISP path. If only your Windows PC fails, test it on another network or hotspot. If it works there, the router settings are more likely than the adapter itself.

Should I reset Windows network settings first?

No. Start with the reversible checks first: another device, router lights, adapter disable/enable, IP renewal, and DNS flush. Use Network reset only after those fail, because it changes more settings and can force you to reconnect afterward.

Can a driver update cause this even if Wi‑Fi still says connected?

Yes. A MediaTek driver update can break DHCP, roaming, sleep/wake recovery, or power management while the Wi‑Fi icon still looks normal. If the problem began right after an update, rollback or reinstall with the correct current driver for your exact PC model is a sensible next move.

Sources