Windows 10 laptops with MediaTek wireless cards — the MT7921, MT7961, and older MT7630E — suffer a familiar cycle: WiFi works, then a Windows update or a sleep/wake cycle kills it. Device Manager shows Code 10, or the adapter vanishes, or networks appear but nothing connects. The card hardware is rarely at fault; MediaTek’s Windows drivers are simply version-sensitive, and Windows 10’s habit of installing its own build over the manufacturer’s is the engine of most failures.
This is the Windows 10 edition of the MediaTek fix sequence: correct driver sourcing, the power settings that wedge these cards, and the Code 10 drill.
Why this happens
- Windows Update driver mismatch. Microsoft’s MediaTek build conflicting with the laptop firmware — the top cause.
- Sleep/wake reinitialization failure. The card not coming back after power management cycles it.
- Code 10 from version mismatch. Driver loads, hardware won’t start.
- Fast Startup resuming wedged state. Hybrid boot carrying the card’s bad state across reboots.
- Corrupt driver files. Partial updates mixing old and new driver binaries.
- Outdated BIOS. Platform firmware predating the card’s initialization requirements.
- Failing M.2 module. Actual hardware failure — uncommon, last resort.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Identify the exact failure state
Precise symptoms dictate the fix — spend two minutes here.
- Open Device Manager > Network adapters and find the MediaTek entry (MT7921, MT7961, MT7630E, or similar).
- Classify it: missing (driver not loading), yellow bang (check Properties > General for the code — usually Code 10), or present but broken (no networks, or networks that won’t connect).
- Note the trigger if you can: after Windows Update, after sleep, or random.
- Do a full cold boot — Shift + Shut down, wait 30 seconds, power on — and see if the card returns. Returning after cold boot but dying after sleep = power management issue.
- Check Settings > Network & Internet — a missing WiFi section means Windows sees no adapter at all.
Fix 2: Install the manufacturer’s MediaTek driver
The central fix — the validated driver, cleanly installed.
- Go to your laptop maker’s support site and download the Wireless/MediaTek driver for your exact model and Windows 10 64-bit.
- In Device Manager, right-click the MediaTek adapter > Uninstall device — check Delete the driver software for this device.
- Restart the laptop.
- Install the downloaded driver before reconnecting to WiFi if practical, then restart again.
- Verify in Properties > Driver that the date/version matches the package you installed — not a Windows Update build.
Fix 3: Block Windows Update from replacing the driver
Without this, the fix unravels at the next update.
- After the maker driver is working, download Microsoft’s Show or hide updates troubleshooter package (wushowhide.diagcab).
- Run it, choose Hide updates, and hide any MediaTek or wireless driver update it offers.
- On Windows 10 Pro, you can also set Group Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not include drivers with Windows Updates to Enabled.
- Recheck the driver version a week later — if it changed, something replaced it and you need to re-hide.
- Keep updating the driver yourself from the maker’s site on your own schedule.
Fix 4: Disable the power settings that kill the card
The sleep-death workaround that MediaTek cards specifically need.
- Device Manager > MediaTek adapter > Properties > Power Management — uncheck Allow the computer to turn off this device to save power.
- Control Panel > Power Options > Change plan settings > Change advanced power settings > Wireless Adapter Settings > Power Saving Mode — set Maximum Performance for both battery and plugged in.
- Power Options > Choose what the power buttons do > Change settings that are currently unavailable — uncheck Turn on fast startup.
- Do a full shutdown and cold boot after these changes.
- Test sleep/wake three times — MediaTek sleep failures are intermittent, so one successful wake isn’t proof.
Fix 5: Reset TCP/IP and the wireless profiles
For cards that are present with networks visible but won’t connect.
- Command Prompt as administrator:
netsh winsock resetthennetsh int ip resetthenipconfig /flushdns. - Restart.
- Settings > Network & Internet > WiFi > Manage known networks — Forget the problem network and reconnect fresh.
- If it still won’t connect, Settings > Network & Internet > Status > Network reset — wipes all adapters and profiles back to defaults.
- Re-apply Fix 4’s power settings after a network reset — it restores driver defaults.
Fix 6: Update the BIOS and try alternate driver builds
Firmware-level fixes for stubborn cards.
- Check the maker’s support site for a BIOS update — install on AC power, nothing else running.
- BIOS changelogs mentioning WLAN, MT7921, or connectivity are directly relevant — retest sleep behavior after updating.
- If the maker’s driver still fails, try a newer MediaTek build from the Microsoft Update Catalog — search your card model (e.g., MT7921), download, and install via Device Manager > Update driver > Browse my computer.
- If a catalog build works, hide it from Windows Update too (Fix 3) so a worse build doesn’t replace it.
- Also try the previous maker driver version — occasionally the newest maker build is the broken one.
Fix 7: The Code 10 deep drill and hardware verdict
For Code 10 that survives everything above.
- Confirm it’s truly Code 10 in Properties > General — Code 43 or 45 need different handling (see how to fix unknown device in Device Manager in Windows 11 24H2 for the identification method).
- Full power-cycle drill: uninstall with driver deletion, Shift+Shutdown, unplug AC, hold power 15 seconds, boot, install maker driver offline.
- Boot a Linux live USB — working WiFi there proves the hardware is fine and isolates it to Windows drivers.
- If the card is a removable M.2 module (check the service manual), reseat it — loose M.2 cards cause exactly Code 10. An Intel AX210 replacement (~$20) is the popular permanent upgrade.
- If the card is soldered and Code 10 persists across drivers and BIOS, a USB WiFi adapter is the pragmatic workaround.
For 5GHz-specific failures rather than a dead adapter: how to fix laptop not connecting to WiFi 5GHz on Windows 10 . Microsoft’s wireless reference is on Windows support .
Closing
MediaTek WiFi on Windows 10 fails in a predictable loop — Windows Update installs a mismatched driver, sleep wedges the card, Code 10 appears — and the fix is equally predictable: the maker’s validated driver, installed clean, protected from Windows Update, with the card’s power management tamed. Break the loop once, properly, and it stays broken… in the good way.
