STATUS_NDIS_DOT11_MEDIA_IN_USE (0XC0232001) Fixes

Cause #1: Faulty or Outdated Wi-Fi Driver

This is the most common trigger. I've seen this error pop up on Dell XPS and Lenovo ThinkPad laptops after a Windows Update drops a bad driver — especially with Intel AX201 or AX211 chips. The driver gets confused and the NDIS interface stays in a busy state. Don't bother reinstalling the latest driver from Windows Update; it rarely helps here. The real fix is rolling back to a known-good version.

How to fix it

1. Open Device Manager (Win + X, then M).
2. Expand Network adapters.
3. Right-click your Wi-Fi adapter (usually Intel Wireless-AC or AX) and pick Properties.
4. Go to the Driver tab.
5. Click Roll Back Driver if it's not grayed out. If it is, you'll need to manually install an older driver.

If rollback isn't available, head to your laptop manufacturer's support page (not Intel's) and grab the Wi-Fi driver from two or three versions back. Install it, reboot, and test. I've fixed this exact error on Windows 11 23H2 with Intel driver version 22.220.0.4 — the newer 23.x releases seem to cause the hang.

Cause #2: Power Management Blocking the Interface

Windows loves to turn off your Wi-Fi adapter to save power. Problem is, when it tries to wake it back up, the adapter sometimes stays stuck in a transitional state — that's when you hit 0XC0232001. You'll see this most often on laptops that go to sleep or hibernate, then wake up with no Wi-Fi.

How to kill power management on the adapter

1. Open Device Manager.
2. Right-click your Wi-Fi adapter → Properties → Power Management tab.
3. Uncheck Allow the computer to turn off this device to save power.
4. Also hit the Advanced tab. Look for a setting called Wake on Magic Packet or Wake on Pattern Match — set both to Disabled if you see them.

Reboot after this. I've seen this alone fix the error on HP EliteBooks running Windows 10 22H2. It's a one-minute change that often works when the driver rollback didn't.

Cause #3: Stuck WLAN AutoConfig Service or Netsh State

Sometimes the Windows WLAN AutoConfig service itself gets hung. This happens when the service tries to start a wireless profile and the adapter doesn't respond in time. You'll notice this after a forced shutdown or Blue Screen — the error appears right after login.

Reset the service and interface from command line

Open Command Prompt as Administrator. Run these commands in order:

net stop WlanSvc
net start WlanSvc
netsh wlan stop hostednetwork
netsh wlan set hostednetwork mode=disallow
netsh int ip reset
netsh winsock reset

After that, reboot. The netsh commands clear stuck virtual adapters (common if you ever used a mobile hotspot). I've also seen cases where disabling and re-enabling the adapter from Control Panel does the trick — go to Network and Sharing Center, Change adapter settings, right-click Wi-Fi, Disable, then Enable. This forces the NDIS stack to reinitialize.

If none of these work, check Event Viewer (System logs) for a Tcpip or NETwNb64 event. That usually points to a corrupt TCP/IP stack. A full network reset via Settings → Network & Internet → Advanced network settings → Network reset is your last move. It'll nuke all your saved Wi-Fi profiles and VPNs, so note those down first.

Quick-Reference Summary Table

Start with the driver fix. Nine times out of ten, that's your problem. If not, kill the power management — that gets the other one. The netsh reset is your hail-mary. I've never needed to replace hardware for this error, so don't go buying a new Wi-Fi card yet.