Device Manager, Network adapters, your WiFi card — yellow triangle, Properties, Device status: ‘This device cannot start. (Code 10).’ Your wireless is dead, and the error message tells you almost nothing useful. Here’s what Code 10 actually means: Windows found the hardware and loaded a driver, but the driver couldn’t initialize the card. In plain terms, it’s a driver-hardware handshake failure — and handshakes fail for fixable reasons. The forum threads on this error are enormous, and the pattern in the solved ones is remarkably consistent: bad driver from Windows Update, fixed by a proper clean reinstall of the right driver. This guide follows that proven sequence, with the deeper cuts (BIOS, power drain, registry) for stubborn cases. If your adapter vanished entirely instead of showing Code 10, see our WiFi disappeared guide — that’s a different problem. Note your card’s brand before starting (Intel, MediaTek, Realtek, Qualcomm) — it determines where the correct driver comes from. Intel AX201 owners should also read our AX201-specific fixes ; that card’s CNVio2 design makes it the Code 10 champion.

Why this happens

  • Mismatched driver from Windows Update. The number-one cause — a generic driver that doesn’t match the card’s firmware revision.
  • Corrupted driver files. Partial updates or disk errors damage the driver store copy.
  • Conflicting driver remnants. Old driver files from a previous card linger and conflict with the new installation.
  • Fast Startup preserving bad state. Hybrid shutdown carries a wedged initialization state across boots.
  • Outdated BIOS/chipset firmware. The card’s firmware interface and the driver disagree, especially on CNVio2 Intel cards.
  • Power management interrupting init. The adapter gets powered down mid-initialization on some power plans.
  • Registry corruption in the driver key. Rare, but damaged UpperFilters/LowerFilters entries block startup.
  • Failing card hardware. The last resort diagnosis — usually accompanied by intermittent disappearance, not stable Code 10.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Clean-reinstall the correct WiFi driver

The fix that resolves most Code 10 cases: remove every trace of the wrong driver and install the right one from the proper source.

  1. Identify your exact card: Device Manager → adapter → Properties → Details tab → Hardware Ids (note VEN/DEV codes).
  2. Download the driver: Intel cards → Intel’s site or the Intel Driver & Support Assistant ; others → your laptop maker’s support page for your exact model.
  3. In Device Manager, right-click the adapter → Uninstall device → check ‘Attempt to remove the driver for this device.’
  4. Restart, then install the downloaded driver package — don’t let Windows Update install one first.
  5. Verify in Device Manager: no yellow icon, and the Driver tab shows the version you installed.

Fix 2: Disable Fast Startup

Code 10 that survives driver reinstalls is often Fast Startup resurrecting a wedged initialization state on every boot.

  1. Control Panel → Power Options → ‘Choose what the power buttons do.’
  2. ‘Change settings that are currently unavailable’ → uncheck ‘Turn on fast startup.’
  3. Full Shutdown, wait 10 seconds, power on.
  4. Check Device Manager — if Code 10 cleared, Fast Startup was preserving the bad state.
  5. Leave it off if your WiFi card is sensitive to it; the boot-time cost is a few seconds.

Fix 3: Power-drain the hardware

A full power drain resets the card’s firmware state below anything Windows can reach — the hardware equivalent of ’turn it off and on again,’ done properly.

  1. Shut down completely and unplug the charger and all peripherals.
  2. Hold the power button for 30 seconds (internal battery) or remove the battery if removable.
  3. Wait a full minute, reconnect only the charger, and boot.
  4. Check whether Code 10 cleared in Device Manager.
  5. This is especially effective for cards that throw Code 10 after sleep/resume cycles.

Fix 4: Update BIOS and chipset drivers

For CNVio2 Intel cards especially, the BIOS participates in card initialization — old BIOS plus new driver equals Code 10.

  1. Check your laptop maker’s support page for BIOS updates mentioning WiFi, wireless, or CNVio2.
  2. Flash the BIOS on AC power with a charged battery; never interrupt it.
  3. Install the latest chipset driver package for your model afterward.
  4. Reboot and check Device Manager for the adapter status.
  5. If the BIOS changelog doesn’t mention wireless, update anyway when the system is significantly behind — initialization fixes hide in generic entries.

Fix 5: Try the driver from the other source

When the maker’s driver fails and Intel’s works (or vice versa), the ‘correct’ source is whichever one initializes your specific card.

  1. If you installed the laptop maker’s driver, try the chip maker’s generic instead (Intel/Realtek/MediaTek direct).
  2. If you installed the chip maker’s driver, try the laptop maker’s customized package — some models need OEM tuning.
  3. Between attempts, always fully uninstall with ‘delete the driver software’ checked.
  4. Note which version works and from where — then block Windows Update from replacing it (see Fix 7).
  5. Keep the working installer archived; you’ll want it after the next feature update.

Fix 6: Check for filter-driver and registry issues

Rare but real: third-party filter drivers (VPNs, firewalls) attach to the network stack and block adapter initialization.

  1. Temporarily uninstall VPN clients and third-party firewalls, then reboot and check the adapter.
  2. In Device Manager → View → ‘Show hidden devices,’ look for grayed-out ghost adapters from old VPNs and uninstall them.
  3. If comfortable with regedit, check the adapter’s class key for stray UpperFilters entries — back up the key first.
  4. Run sfc /scannow in an elevated Command Prompt to repair corrupted system files affecting driver loading.
  5. Reinstall the WiFi driver once more after cleaning filters — the combination often succeeds where either alone failed.

Fix 7: Block driver updates and verify long-term

Code 10 has a nasty habit of returning via Windows Update. Lock in your working driver.

  1. Confirm the adapter works through sleep/wake cycles and reboots over a day or two.
  2. Use Microsoft’s ‘Show or hide updates’ troubleshooter to hide the problematic driver update.
  3. Or enable ‘Do not include drivers with Windows Updates’ via Group Policy / registry.
  4. Write down the working driver version and its source for future reference.
  5. If Code 10 ever returns after these steps on a card that also intermittently vanishes, suspect hardware — our 5GHz connection guide covers the deeper wireless diagnostics, and Microsoft’s Windows support hub documents hardware diagnostics.

Closing

Code 10 looks cryptic but it’s almost always a driver mismatch wearing a scary error code. Clean out the wrong driver, install the right one from the right source, disable Fast Startup, and block the bad update — that sequence ends the vast majority of Code 10 sagas.

Frequently asked questions

What does Code 10 mean on a WiFi adapter?
Code 10 means ’this device cannot start’ — Windows loaded the driver but the hardware failed to initialize. For WiFi adapters, it’s almost always a driver problem: corrupted installation, a Windows Update driver that doesn’t match the card’s firmware, or conflicting driver remnants. Hardware failure is possible but much less common; software fixes resolve the large majority of Code 10 cases.
How do I fix Code 10 on my wireless network adapter?
The reliable sequence is: uninstall the adapter in Device Manager (checking ‘delete the driver software’), restart, then install the correct driver from your laptop maker’s support site or the chip maker (Intel, MediaTek, Realtek). If that fails, try a System Restore to before the error appeared, disable Fast Startup, and check for BIOS updates — in that order.
Can Windows Update cause a Code 10 WiFi error?
Yes, frequently. Windows Update installs generic or mismatched wireless drivers that don’t align with the card’s firmware, particularly for Intel AX201 (CNVio2) and MediaTek cards. The pattern is unmistakable: WiFi worked, an update installed overnight, and Code 10 appeared. Reinstalling the proper driver and then blocking driver updates prevents the cycle from repeating.
Does Code 10 mean my WiFi card is dead?
Not usually. A truly dead card typically vanishes from Device Manager entirely rather than appearing with Code 10 — the error itself proves Windows can still see and talk to the hardware at some level. Suspect hardware only after clean driver reinstalls, BIOS updates, and power drains all fail, or if the card also disappears intermittently.