A Code 10 error on your Wi-Fi adapter — “This device cannot start” — kills wireless completely: no networks, no icon, nothing. The message is blunt but honest: Windows found the hardware, loaded a driver, and the driver failed to bring the card to life. In most cases the card is fine and the driver installation is what’s broken.

The repair sequence is straightforward: confirm the error, clear out the broken driver completely, install a known-good driver from the laptop maker, and stop Windows from re-breaking it. Work the steps in order — skipping the full driver removal is the reason most Code 10 fixes fail on the first attempt. For the related Intel-specific variant, see Intel Wi-Fi 6 AX201 fixes .

Why this happens

  • Corrupted driver files: An interrupted update or disk error leaves the Wi-Fi driver partially installed and unable to initialize the card.
  • Wrong driver for the hardware: A generic or mismatched driver was installed that doesn’t understand this specific adapter.
  • Driver store holding a bad copy: Windows keeps reinstalling the same broken driver from its local store after every uninstall.
  • Power management killing initialization: The adapter is powered down before the driver finishes starting it.
  • Windows Update driver replacement: An update swapped your working driver for a broken one.
  • Registry corruption in the device instance: Stale device instance keys confuse the driver during startup.
  • Conflicting VPN or filter drivers: Network filter drivers from VPN clients interfere with adapter initialization.
  • Failing Wi-Fi card: The hardware genuinely can’t start — uncommon, but real, especially after liquid damage.

How to fix it

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

Fix 1: Confirm the Code 10 and read the details

Open Device Manager, expand Network adapters, and double-click the Wi-Fi adapter. On the General tab, confirm the Device status reads “This device cannot start. (Code 10).” Check the Events tab for the driver’s load history — it often shows exactly which driver version failed and when. Note the adapter’s exact model name and hardware IDs (Details tab, Hardware Ids) — you’ll need these to download the correct driver. This confirmation takes two minutes and prevents fixing the wrong device.

  1. Open Device Manager and expand Network adapters.
  2. Double-click the Wi-Fi adapter and read Device status.
  3. Check the Events tab for driver load failures.
  4. Copy the Hardware Ids from the Details tab.
  5. Note the exact adapter model name.

Fix 2: Power-cycle to clear stuck hardware state

Shut the laptop down fully — hold Shift while clicking Shut down to bypass Fast Startup — unplug the charger, and if the battery is removable, take it out. Wait 60 seconds, then reassemble and boot. This drains residual power and resets the Wi-Fi card at the hardware level, clearing stuck initialization states that survive normal reboots. If Code 10 clears after this but returns later, you’re looking at a driver or power-management issue rather than a one-time glitch.

  1. Hold Shift and click Shut down for a full shutdown.
  2. Unplug the charger and remove the battery if possible.
  3. Wait a full 60 seconds.
  4. Reconnect power and boot normally.
  5. Check whether Code 10 persists in Device Manager.

Fix 3: Uninstall the driver completely, then reinstall

This is the core fix. Download the Wi-Fi driver for your exact model from the manufacturer first — Dell’s support portal or Lenovo’s support site — since you’ll be offline after uninstalling. In Device Manager, right-click the adapter, choose Uninstall device, and tick “Attempt to remove the driver for this device.” Reboot, install the downloaded package, reboot again. The checkbox is critical: without it, Windows just reloads the broken driver.

  1. Download the Wi-Fi driver for your exact model while still online.
  2. In Device Manager, uninstall the adapter with driver software removed.
  3. Restart the laptop.
  4. Install the downloaded manufacturer driver package.
  5. Restart and verify the adapter starts without Code 10.

Fix 4: Disable power management on the adapter

In Device Manager, open the Wi-Fi adapter’s Properties, go to the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.” Then in Power Options, set Wireless Adapter Settings to Maximum Performance for both battery and plugged-in. Code 10 errors that appear after sleep or that come and go are classic power-management casualties — the adapter gets powered down mid-initialization and never recovers until a reboot.

  1. Open the adapter Properties in Device Manager.
  2. Uncheck power-saving on the Power Management tab.
  3. In Power Options, set wireless adapter to Maximum Performance.
  4. Apply to both battery and plugged-in profiles.
  5. Reboot and test across sleep/wake cycles.

Fix 5: Remove conflicting network filter drivers

VPN clients, some firewalls, and network monitoring tools install filter drivers that bind to the Wi-Fi adapter and can break its startup. Open the adapter’s Properties, go to the Networking tab, and uncheck everything except the core Microsoft items (Client for Microsoft Networks, QoS Packet Scheduler, Internet Protocol versions) as a test. Also uninstall any VPN client you don’t actively use. If the adapter starts cleanly with filters removed, re-enable them one at a time to find the offender; Microsoft’s Windows support pages explain the network adapter properties involved.

  1. Open the adapter Properties, Networking tab.
  2. Uncheck non-Microsoft items as a test.
  3. Uninstall unused VPN clients and network tools.
  4. Reboot and check for Code 10.
  5. Re-enable items one by one to identify the culprit.

Fix 6: Reset the network stack

Open an elevated Command Prompt and run the network reset sequence: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, ipconfig /flushdns. Then use Settings, Network & internet, Advanced network settings, Network reset to reinstall all network adapters and reset networking components to defaults. This rebuilds the software environment around the adapter. Reboot after the reset and reinstall the manufacturer’s Wi-Fi driver if Windows doesn’t do it automatically. For the deeper diagnostic path, see troubleshooting a Code 10 Wi-Fi failure .

  1. Run netsh winsock reset in an elevated Command Prompt.
  2. Run netsh int ip reset and the ipconfig sequence.
  3. Use Settings, Network reset for a full rebuild.
  4. Reboot the laptop.
  5. Reinstall the manufacturer Wi-Fi driver if needed.

Fix 7: Test the hardware independently

If Code 10 survives every software fix, verify the hardware. Boot a Linux live USB — if the Wi-Fi card works there, the hardware is fine and Windows’ driver stack is the problem (consider a Windows reset at that point). If Linux also can’t bring the card up, the card is likely dead. On many laptops the Wi-Fi card is a replaceable M.2 module; check the service manual. Also try reseating the card and its antenna leads if you’re comfortable opening the chassis — a loose card can throw Code 10 intermittently.

  1. Boot a Linux live USB and test the Wi-Fi card.
  2. Working in Linux means a Windows software problem.
  3. Failing in Linux points to dead hardware.
  4. Check the service manual for card replacement steps.
  5. Reseat the card and antenna leads if accessible.

Closing

Code 10 on Wi-Fi is a driver-stack problem far more often than a hardware problem, and the full uninstall-reinstall with the manufacturer’s package resolves most cases. The two details that make or break the fix: ticking the driver-removal checkbox, and stopping Windows Update from reinstalling the broken driver afterward. When the error survives a Linux test too, you’ve got your hardware answer — replace the card and move on.

Frequently asked questions

What does Code 10 mean on a Wi-Fi adapter?
Code 10 means ’this device cannot start’ — Windows loaded a driver for the Wi-Fi adapter but the driver failed to initialize the hardware. The usual causes are a corrupted driver installation, a driver that doesn’t match the hardware, or power-management cutting the adapter off mid-start. It is a software problem in most cases, not a dead card.
Why does Code 10 keep coming back after I reinstall the driver?
Recurring Code 10 usually means Windows is reinstalling the same broken driver from its driver store, or a Windows Update keeps replacing your working driver with a bad one. Uninstall with the driver software fully removed, install the manufacturer’s package fresh, and then block driver updates from Windows Update to break the cycle.
Can Code 10 on Wi-Fi mean the card is physically dead?
It can, but hardware death is the less common cause. Suspect hardware only after clean driver installs from the manufacturer fail, the error persists in a Linux live environment, and the card shows Code 10 immediately on every boot. A card that sometimes works and sometimes throws Code 10 is more likely a power or seating issue.
Will resetting Windows fix a Wi-Fi Code 10 error?
A Windows reset usually fixes Code 10 because it rebuilds the entire driver stack from scratch. But it is a heavy hammer — try clean driver reinstallation, power management fixes, and network resets first. Reserve the reset for cases where the error survives every targeted fix, and back up your drivers beforehand.