A Code 10 error on your WiFi adapter — “This device cannot start” — is Windows telling you the driver loaded but the wireless hardware refused to wake up. The timing is the tell: in the vast majority of cases, the error appears the morning after a Windows update, because the update replaced your working wireless driver with a version that doesn’t match your specific card. The hardware is almost certainly fine; the driver is simply the wrong one.

The best fix is a disciplined driver repair in a specific order: roll back, clean reinstall, manufacturer driver, then block the bad update. Skip the random forum suggestions and follow the sequence.

Code 10 looks scarier than it is, and understanding what the message actually means takes away the fear. “This device cannot start” is Windows reporting that the driver-to-hardware handshake failed during initialization — the driver asked the wireless card to wake up in a language the card didn’t understand, usually because the driver was built for a different revision of the same card family. The hardware is almost always innocent: the card worked yesterday with the old driver, and nothing physical changed overnight. What changed is purely software — the driver package — which is why the entire repair lives in Device Manager and never requires opening the laptop. Keep that framing and the sequence below feels logical rather than ritualistic.

Why this happens

  • Windows Update installed a mismatched driver: The new driver’s device ID table doesn’t include your exact wireless card revision.
  • Corrupted driver installation: An interrupted update leaves partial driver files that fail initialization.
  • Driver store conflict: Multiple wireless driver versions compete, and Windows binds the wrong one.
  • Power-state failure: The adapter fails to resume from sleep, and the error persists until the driver stack resets.
  • BIOS update changed the device ID: New firmware presents a different hardware ID the old driver doesn’t recognize.
  • Registry corruption in the driver binding: Damaged UpperFilters/LowerFilters or service entries block startup.
  • Antivirus or security software blocking: Overzealous security tools can intercept the driver’s hardware access.
  • Actual hardware failure: A dead wireless card produces the identical error — the diagnosis of exclusion.

How to fix it

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

Fix 1: Confirm the Code 10 details

  1. Open Device Manager → Network adapters, double-click the wireless adapter, and read the Device status box on the General tab.
  2. Note the exact message and check the Events tab for the driver version that was loaded when the failure began.
  3. If the failure date matches a Windows update, you have your prime suspect.
  4. Also check whether Bluetooth (often on the same card) still works — working Bluetooth with dead WiFi points at the WiFi driver specifically, not the card.

Fix 2: Roll back the driver

  1. In the adapter’s Properties → Driver tab, click Roll Back Driver if available and pick a reason.
  2. Restart and check Device Manager — the yellow warning should be gone.
  3. This is the fastest fix when an update caused the problem, restoring the exact driver that worked yesterday.
  4. If the button is greyed out, Windows replaced rather than updated the driver — proceed to Fix 3.

Fix 3: Clean-uninstall with driver deletion

  1. Right-click the adapter in Device Manager and choose Uninstall device.
  2. Check Attempt to remove the driver for this device — this deletes the mismatched driver package so Windows can’t reinstall it.
  3. Restart. Windows installs its inbox driver, which is older but broadly compatible.
  4. Check whether Code 10 clears. If it does, the deleted driver was definitively the problem.

Fix 4: Install the manufacturer’s wireless driver

  1. Identify your exact wireless card model from the Device Manager Details → Hardware Ids tab.
  2. Download the driver from your laptop maker’s support site for your exact model — not a generic Intel/Realtek/MediaTek download.
  3. Install it and restart, then verify the driver provider and date in Properties → Driver.
  4. OEM packages include the correct firmware and device-ID mappings for your card revision. Intel-card owners can cross-check with the Intel Driver & Support Assistant .

Fix 5: Block Windows Update from re-breaking it

  1. Download Microsoft’s Show or hide updates troubleshooter and hide the wireless driver update.
  2. Alternatively, in Settings → Windows Update → Advanced options, review Optional updates and uncheck driver offers before installing.
  3. This step is what makes the repair permanent — without it, the Code 10 returns with the next update cycle.
  4. Re-check after each major Windows feature update, which can re-offer hidden drivers.

Fix 6: Reset the network stack

  1. Open Terminal as administrator and run: netsh winsock reset netsh int ip reset
  2. Restart the laptop.
  3. A corrupted network stack can prevent the adapter from completing initialization, producing a Code 10 that looks like a driver problem.
  4. This is a safe, quick step worth trying before suspecting hardware.

Fix 7: Check BIOS and power settings

  1. Enter BIOS/UEFI and confirm the wireless adapter is enabled — some BIOS updates flip it off.
  2. In Device Manager → adapter Properties → Power Management, uncheck Allow the computer to turn off this device to save power.
  3. Disable Fast Startup in Power Options and do a full cold boot.
  4. If Code 10 only appears after sleep/wake cycles, power management is your culprit. For the broader vanished-WiFi symptom, see WiFi disappeared from Windows 11 .

Fix 8: Test the hardware

  1. Boot a Linux live USB — if WiFi works there, the card is alive and Windows is the problem.
  2. As a final Windows test, try the card in a different OS user profile or after a network reset (Settings → Network → Advanced → Network reset).
  3. If Linux also shows no wireless hardware, the card has likely failed — replacement WiFi cards are inexpensive on most models with socketed cards.
  4. Check Microsoft’s Windows support site for Code 10 known issues tied to your update. For MediaTek-specific wireless failures, see our MediaTek WiFi repair guide .

Closing

Code 10 is a driver-identity problem wearing a hardware costume. Roll back, clean out the bad package, install the manufacturer’s exact driver, and block the update that caused it — that sequence clears the error in nearly every case. Reserve the hardware verdict for after Linux says the card is truly gone. And remember the blocking step: the update that caused this Code 10 will try to reinstall itself, so hiding it isn’t optional — it’s what turns a fix into a permanent fix.

Frequently asked questions

What does Code 10 mean on a WiFi adapter?
Code 10 means the device failed to start: Windows loaded the driver, but the wireless hardware refused to initialize. For WiFi adapters this almost always indicates a driver-hardware mismatch, typically after Windows Update installed the wrong driver version for your specific wireless card.
Will a Code 10 error fix itself after a restart?
Rarely. The error reflects a persistent driver-hardware incompatibility, not a transient glitch. A restart only helps if the failure was caused by a one-time power-state problem. Plan on a driver rollback or clean reinstall rather than waiting for it to resolve.
Can a Code 10 error mean the WiFi card is dead?
It can, but hardware death is the least common cause. If the error appeared right after a Windows update and the card worked before, it is a driver problem in the overwhelming majority of cases. Only suspect hardware after clean driver installs from the manufacturer also fail.
Why does the Code 10 error keep coming back?
Windows Update keeps reinstalling the same incompatible driver after you fix it. Blocking that specific driver update with the show-or-hide-updates troubleshooter, or installing the manufacturer’s driver that Windows recognizes as newer, breaks the cycle permanently. Recheck the hidden-updates list after each major feature update, since those can re-offer drivers you previously blocked.