Fix ERROR_NDIS_DOT11_MEDIA_IN_USE (0x80342001) in 2 Minutes

Yeah, This Error is Annoying — Here's the Fix

You're staring at that 0x80342001 error, and your Wi-Fi just sits there dead. I've seen this more times than I can count, especially on Windows 10 22H2 and Windows 11 23H2, after the machine wakes from sleep or when the network profile gets corrupted. The culprit is almost always the WLAN AutoConfig service getting stuck in a bad state. Skip the deep registry edits — try this first.

The Fix: Restart WLAN AutoConfig + Reset the Adapter

Open Command Prompt as Admin. Hit Start, type cmd, right-click, choose "Run as administrator." Don't skip this — normal mode won't cut it.
Stop the WLAN service:
```
net stop wlansvc
```
Wait 10 seconds. If it hangs, use sc query wlansvc to check state, then sc stop wlansvc if needed.

Reset the adapter:

netsh wlan disconnect
netsh int ip reset
netsh winsock reset

Ignore any "must reboot" messages for now.

Restart the service:
```
net start wlansvc
```
Reconnect to your network. Click the Wi-Fi icon, find your SSID, connect.

That sequence clears the lock on the wireless LAN interface. In 9 out of 10 cases, this kills the 0x80342001 error immediately. If it doesn't work, read on.

Why This Works

The error means the NDIS driver layer thinks the Wi-Fi adapter is already in use by another process — usually the WLAN AutoConfig service itself got stuck mid-operation. By stopping the service, you force the adapter to release any pending I/O requests. The netsh commands reset the IP stack and Winsock, which clears any leftover socket locks. Then restarting the service reloads everything fresh. It's the equivalent of pulling the plug on a frozen network card without rebooting the whole machine.

I've seen this happen after a driver update from Intel or Realtek where the new driver doesn't fully release the adapter on sleep. Starting fresh like this sidesteps the bug.

Less Common Fixes — When the Basic Fix Fails

Sometimes the service restart alone doesn't cut it. Try these in order:

1. Disable and Re-enable the Adapter in Device Manager

Press Win + X and choose Device Manager.
Expand Network adapters.
Right-click your Wi-Fi adapter (usually "Intel Dual Band Wireless-AC 7265" or "Realtek 8822CE") and select Disable device.
Wait 10 seconds, then right-click and Enable device.

This forces a hardware-level reset. Works when the service restart doesn't — the driver itself is hung.

2. Delete Stored Profiles and Reconnect

netsh wlan delete profile name="YourNetworkName"
netsh wlan add profile filename="C:\path\to\exported\profile.xml"

Better yet, just delete all profiles and reconnect manually:

netsh wlan delete profile *

Then click the network icon and connect fresh. Corrupted profiles are a common trigger for this error.

3. Update or Roll Back the Wi-Fi Driver

Open Device Manager, right-click your adapter, choose Properties → Driver. If you just updated, hit Roll Back Driver. If you haven't updated in months, check the manufacturer's site for a new version. Intel's drivers after 22.200.0 are notorious for this bug on certain chipsets.

Prevention — Don't Let This Keep Happening

Two things cause this error to recur. First, power management settings. Go to Device Manager → Network adapters → right-click your Wi-Fi adapter → Properties → Power Management tab. Uncheck "Allow the computer to turn off this device to save power." That alone stops most sleep/wake triggers.

Second, keep your Wi-Fi driver at a known-good version. For Intel adapters, stick with version 22.180.0 or earlier. Realtek users should use the driver from the OEM (Lenovo, Dell, HP) — not the generic Realtek one. Generic drivers often miss the power-reset fixes these manufacturers test.

If you're in a corporate environment with group policies that manage network profiles, have your team push a script that runs the service restart on wake:

# Save as reset-wlan.cmd, run via Task Scheduler on system wake
@echo off
net stop wlansvc
ping -n 5 127.0.0.1 > nul
net start wlansvc
nbtstat -RR

That's it. This error is a pain, but it's fixable without a rebuild or a new adapter. Save yourself the headache and just restart the service before diving into anything deeper.