Intel AX201 Code 10 After Sleep? The Real Fix

I know how infuriating it is when your laptop wakes from sleep and the Wi-Fi icon shows that little globe with a slash — no networks, no internet, and Device Manager is throwing Code 10 on your Intel AX201. You've probably already tried reinstalling the driver twice. Don't. The real fix isn't in the driver package.

The fix: disable Modern Standby's selective suspend for the AX201

This is the one that actually sticks. It's a registry change, so back up first if you're the cautious type (File > Export in regedit).

Open Device Manager (devmgmt.msc).
Expand Network adapters, right-click Intel(R) Wi-Fi 6 AX201 160MHz, choose Properties.
Go to the Details tab, pick Property: Hardware Ids from the dropdown. Note the first value — something like PCI\VEN_8086&DEV_02F0&SUBSYS_.... You'll need the VEN and DEV.
Open Registry Editor as admin (regedit).

Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}

You'll see subkeys 0000, 0001, etc. Click each one and check the DriverDesc value until you find the AX201.
In that subkey, create a new DWORD (32-bit) value named EnableDynamicPowerGating and set it to 0.
Also create a DWORD named PnPCapabilities and set it to 24 (hex 0x18). This tells Windows not to power the adapter down during sleep.
Reboot. Sleep the machine. Wake it. Wi-Fi should come back on its own.

If it still fails after sleep, open the adapter's Power Management tab (back in Device Manager) and uncheck Allow the computer to turn off this device to save power. Then re-check it. That sounds superstitious, but it forces Windows to rewrite the power policy against the new registry values.

Why this works

The AX201 is a CNVi part — the Wi-Fi MAC lives inside the Intel chipset, not on the card itself. That means when Windows enters Modern Standby (S0 low-power idle), the chipset can gate power to the CNVi block independently of the PCIe link state. On some BIOS revisions — especially on Dell XPS 13 9300/9310, Lenovo ThinkPad X1 Carbon Gen 8/9, and certain ASUS ZenBook 14 models — the handshake between the platform and the driver on wake fails, and the adapter enumerates with a bad status code. Windows reports that as Code 10: "This device cannot start."

Reinstalling the driver doesn't help because the driver is fine. The device node itself never reinitializes properly. By disabling dynamic power gating and setting PnPCapabilities to 0x18, you're telling Windows to keep the adapter's power context alive across the sleep transition, which sidesteps the buggy handshake entirely.

Less common variations

Not everyone hits the same root cause. If the registry fix didn't take, try these in order:

Fast Startup is fighting you. Fast Startup (hybrid shutdown) and Modern Standby don't play nicely. Disable it:
```
powercfg /h off
```
in an admin Command Prompt. Yes, this disables hibernation too. If you use hibernate, skip this step.
Older Intel driver with an old date. The 22.40.0.7 driver from 2020 was notorious for this on Windows 10 2004. Grab the latest driver directly from Intel's site — not Windows Update, which ships a stale one. As of writing, 23.x or later is what you want.
BIOS power settings. On some ThinkPads, Intel Speed Shift or Deep Sleep in BIOS triggers this on wake. Set Deep Sleep to Linux (yes, really — it changes the sleep behavior in a way Windows tolerates better).
Bluetooth coexistence bug. The AX201 shares an antenna path with Bluetooth. If BT is also misbehaving after sleep, disable the Bluetooth radio in Device Manager, sleep/wake once, then re-enable. That clears a stuck coexistence state.
Windows 11 22H2 specific. There's a known regression with Netwtw10.sys on 22H2 where the adapter fails to re-enumerate after >30 minutes of sleep. The Intel 23.60.1 driver fixed it. Check your version in Device Manager > Driver tab.

Prevention so it doesn't come back

Once you're stable, do three things:

Pin the Intel driver version. Don't let Windows Update silently downgrade you. In Device Manager, right-click the adapter > Update driver > Browse my computer > Let me pick > uncheck "Show compatible hardware" is overkill; instead, just set ExcludeWUDriversInQualityUpdate under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate to 1 if you manage your own drivers.
Update your BIOS. Dell, Lenovo, and ASUS have all shipped firmware updates in the last 18 months that fix CNVi wake behavior. Check your model's support page — not the generic driver updater apps.
Keep a recovery shortcut. Create a .bat on your desktop:
```
@echo off
net stop wxvwifi
net start wxvwifi
pause
```
Run as admin. This restarts the Intel Wi-Fi service stack in about 4 seconds when the adapter inevitably misbehaves again — much faster than a full reboot.

Quick reality check: if Code 10 shows up on a cold boot too — not just after sleep — you're looking at a different problem. That's usually a dead CNVi block, a loose M.2 seating on models where the AX201 is a discrete module, or a failed BIOS flash. Run pnputil /enum-devices /problem from an admin prompt to see if other devices are also faulting. If they are, it's a platform issue, not a Wi-Fi issue.

Give the registry fix a shot first. It's a two-minute change that solves this for the vast majority of AX201 owners, and it survives Windows feature updates — unlike half the workarounds you'll find on Reddit.