Code 10 — “this device cannot start” — on a Wi-Fi adapter is a symptom, not a diagnosis. It tells you the driver failed to initialize the hardware, but not why. This guide takes the troubleshooting approach: reading the evidence Windows gives you, isolating the failing layer, and applying the fix that matches the evidence. It pairs with our step-by-step Code 10 repair guide — use that for the direct fix sequence, this one for understanding what’s actually wrong.

The mindset shift is simple: before changing anything, gather data. The device’s Events tab, the System event log, and a Safe Mode test each take minutes and each eliminate whole categories of causes. Ten minutes of diagnosis routinely saves an hour of random reinstalls.

Why this happens

  • Driver binary corruption: The installed driver’s files are damaged, so initialization code crashes on load.
  • Driver/hardware mismatch: The driver version doesn’t support this exact adapter revision.
  • Stale device instance state: Leftover registry keys from a previous installation poison the new driver’s startup.
  • Power delivery failure during init: The card doesn’t get stable power during the driver’s initialization window.
  • Filter driver interference: Third-party network filters hook the adapter and break its startup sequence.
  • Firmware on the card is bad: The adapter’s own firmware fails to respond to the driver’s initialization commands.
  • PCIe link instability: The card’s connection to the chipset is marginal, causing init timeouts.
  • Windows driver ranking picking wrong: Windows’ driver ranking selects an older or generic driver over the correct one.

How to fix it

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

Fix 1: Read the device’s event history

Open Device Manager, double-click the Wi-Fi adapter, and go to the Events tab. You’ll see a timestamped log of driver installations and start attempts. Look for the most recent “Device not started” entry and what preceded it — a driver update immediately before the failures began is a smoking gun. Note the driver version and provider for each entry. Then check Windows Logs, System in Event Viewer for related errors from the same timeframe. This history tells you whether the failure started with an update, a crash, or seemingly nothing.

  1. Open the adapter’s Properties and go to the Events tab.
  2. Find the most recent “Device not started” entry.
  3. Note what changed immediately before failures began.
  4. Record driver versions and providers from the log.
  5. Cross-check with System event log errors.

Fix 2: Test in Safe Mode with Networking

Restart into Safe Mode with Networking (Settings, Recovery, Advanced startup, or Shift+Restart). If the Wi-Fi adapter starts normally there, a third-party component in normal boot is the culprit — Safe Mode skips non-Microsoft drivers and startup software. If Code 10 persists even in Safe Mode, the problem is in the core driver, Windows itself, or the hardware. This single test cleanly splits the problem space and is the most valuable diagnostic step in this guide.

  1. Boot into Safe Mode with Networking.
  2. Open Device Manager and check the adapter status.
  3. Working in Safe Mode means third-party interference.
  4. Still Code 10 in Safe Mode means core driver or hardware.
  5. Record the result before continuing.

Fix 3: Clean-boot to isolate the interfering software

If Safe Mode worked, run msconfig, hide all Microsoft services, disable the rest, and disable all startup items in Task Manager. Reboot normally — with luck the adapter now starts. Re-enable services in halves, rebooting each time, until Code 10 returns; the last group contains the offender. VPN clients, endpoint security agents, and network monitoring tools are the usual suspects. Once identified, update or remove the offending software rather than leaving half your services disabled. Microsoft’s Windows support hub documents the clean boot procedure.

  1. Run msconfig and hide Microsoft services.
  2. Disable remaining services and all startup items.
  3. Reboot and check the adapter.
  4. Re-enable in halves to isolate the culprit.
  5. Update or remove the offending software.

Fix 4: Purge the driver store entry

When the Events tab shows the same broken driver version returning after every uninstall, Windows is reinstalling from its driver store. Open an elevated Command Prompt and run pnputil /enum-drivers to list third-party driver packages; find the one matching your Wi-Fi adapter’s provider and version. Remove it with pnputil /delete-driver oemXX.inf /uninstall (using the actual published name). Then uninstall the device in Device Manager with driver removal ticked, reboot, and install the manufacturer’s fresh package — Intel’s Driver & Support Assistant can supply a clean driver for Intel cards.

  1. Run pnputil /enum-drivers elevated and find the Wi-Fi package.
  2. Delete it with pnputil /delete-driver oemXX.inf /uninstall.
  3. Uninstall the adapter in Device Manager with driver removed.
  4. Reboot the laptop.
  5. Install a fresh manufacturer driver package.

Fix 5: Check firmware and BIOS handoff

The BIOS hands the Wi-Fi card to Windows during boot, and a buggy handoff can manifest as Code 10. Check your laptop maker’s support page for BIOS updates mentioning wireless, WLAN, or device initialization — Lenovo’s support site lists per-model BIOS changelogs. Apply only with the charger connected and the battery charged. Also check for a Wi-Fi card firmware update in the maker’s driver packages; some MediaTek and Intel cards have separate firmware updaters. For MediaTek-specific issues, see MediaTek Wi-Fi troubleshooting .

  1. Check the maker’s site for relevant BIOS updates.
  2. Apply BIOS updates only with charger connected.
  3. Look for separate Wi-Fi firmware updaters in driver packages.
  4. Reboot and verify the adapter initializes.
  5. Recheck Device Manager for Code 10.

If the failure is intermittent — Code 10 sometimes, working other times — suspect the physical connection. Power off, open the chassis per the service manual, and reseat the M.2 Wi-Fi card, ensuring it’s fully seated and the screw is snug. Reconnect the antenna leads firmly (black to MAIN, white to AUX). While inside, inspect for liquid residue or corrosion around the slot. Intermittent Code 10 that survives driver work is the classic signature of a marginal hardware connection.

  1. Power off and open the chassis per the service manual.
  2. Reseat the M.2 Wi-Fi card fully.
  3. Reconnect antenna leads: black to MAIN, white to AUX.
  4. Inspect the slot for corrosion or liquid damage.
  5. Reassemble and test across multiple boots.

Fix 7: Validate with an independent OS and decide

Boot a Linux live USB. If the card initializes and connects in Linux, the hardware is good and the fault is entirely in Windows’ driver stack — at this point a Windows reset (after backing up drivers ) is the rational fix. If Linux also fails to start the card, the hardware is dead: replace the M.2 card (Intel AX210 is the common reliable choice, BIOS whitelist permitting) or use a USB Wi-Fi adapter as a workaround.

  1. Boot a Linux live USB and test wireless.
  2. Working in Linux proves a Windows-only problem.
  3. Failing in Linux proves hardware failure.
  4. Back up drivers, then reset Windows if it’s software.
  5. Replace the card or use USB Wi-Fi if it’s hardware.

Closing

Code 10 troubleshooting is detective work: the Events tab names the suspect, Safe Mode tests the alibi, and the Linux test delivers the verdict. Most cases end at a corrupted or mismatched driver that a proper purge-and-reinstall fixes. The cases that don’t — the ones where every OS fails to start the card — are the ones where you stop reinstalling and replace hardware. Either way, you arrive at the answer with evidence instead of guesses.

Frequently asked questions

How is troubleshooting Code 10 different from just reinstalling the driver?
Reinstalling is one step; troubleshooting is the full diagnostic path. Code 10 can come from corrupted driver files, a mismatched driver, power management, filter conflicts, or dead hardware. Blindly reinstalling the same broken driver fixes nothing. A proper troubleshoot identifies which layer is failing first, so each fix targets the actual cause.
What should I check in Event Viewer for a Code 10 Wi-Fi failure?
Look in Windows Logs, System for warnings or errors from the network adapter driver source around boot time. The Events tab in the device’s own properties also logs driver load attempts. Repeated ‘device not started’ entries with the same driver version confirm a driver problem; entries mentioning power or firmware point toward hardware or power management.
Why does my Wi-Fi work in Safe Mode but throw Code 10 normally?
That pattern means a third-party driver or service loaded during normal boot is interfering with the adapter. Safe Mode loads only core Microsoft drivers, so the adapter starts fine. The culprit is usually a VPN filter, firewall driver, or another network tool — use a clean boot to isolate it by halves.
Can a BIOS update fix a Wi-Fi Code 10 error?
Occasionally, yes — if the BIOS update notes mention wireless, WLAN, or device initialization fixes for your model. The BIOS hands the Wi-Fi card to Windows during boot, and buggy handoff code can cause Code 10. But update the BIOS only for a listed relevant fix, with the charger connected, since a failed flash is far worse than a Wi-Fi problem.