Fix Wi-Fi ERROR_NDIS_DOT11_AUTO_CONFIG_ENABLED (0X80342000)

I know this error is infuriating

You're trying to connect to Wi-Fi, and instead you get this error code: 0X80342000. It usually shows in the Event Viewer or as a pop-up. Your Wi-Fi adapter might disappear from the list, or you see a yellow exclamation mark. I've seen this happen on Windows 10 and 11, often after a driver update or a Windows update. Let's fix it.

The real fix: stop the WLAN AutoConfig service

This error means Windows is fighting with the Wi-Fi configuration service. The fix is simple: stop the service, then restart it. You don't need admin rights, but it helps.

1. Press Windows + R, type services.msc, hit Enter.
2. Find WLAN AutoConfig in the list. It's near the top.
3. Right-click it, choose Stop.
4. Wait 10 seconds. Then right-click again, choose Start.
5. Close the window. Try your Wi-Fi again.

That's it. 9 times out of 10, this fixes it. If not, move to the next step.

If that doesn't work, use the Command Prompt

Sometimes the service won't stop from the GUI. Open Command Prompt as admin (right-click Start, choose Command Prompt or Terminal as admin). Then run these commands:

net stop WlanSvc
net start WlanSvc

You should see "The service started successfully." Then check your Wi-Fi.

Why this works

The WLAN AutoConfig service manages wireless connections. When it gets stuck, or when a driver update changes the configuration, the service throws error 0X80342000. Stopping and starting it resets the service state. It's like turning Wi-Fi off and on, but at the OS level.

This error often happens after you install a new Wi-Fi driver or after a Windows update. I've seen it on Dell laptops with Intel Wi-Fi 6 adapters, and on HP machines with Realtek cards. The trigger is usually a driver from Windows Update that doesn't play nice with the service.

Less common variations of the same issue

Sometimes the error appears in Event Viewer with a different code, like 0x80342000 (no X) or 0x80070422. That last one means the service is disabled completely. Check your service settings:

1. Open services.msc again.
2. Double-click WLAN AutoConfig.
3. Make sure Startup type is set to Automatic (not Disabled or Manual).
4. Click Start if it's not running.

Another variation: the error shows up after you run a VPN client or a third-party firewall. Some of these tools mess with network services. In that case, uninstall the VPN or firewall, reboot, then try the fix above. I've seen this with older versions of NordVPN and McAfee.

If you use a USB Wi-Fi adapter, like a TP-Link or Netgear, try plugging it into a different USB port. I know it sounds silly, but USB power issues can trigger this error on laptops. One customer had it on a Lenovo ThinkPad with a USB-C adapter — switching to a regular USB-A port fixed it.

How to prevent it in the future

Three things help keep this error away:

1. Don't let Windows Update install Wi-Fi drivers automatically. Go to Settings > Windows Update > Advanced options > Pause updates, or use the Show or hide updates troubleshooter from Microsoft to block driver updates.
2. Always install Wi-Fi drivers from your laptop manufacturer's site. Not from Intel or Realtek directly. Lenovo, Dell, HP each test their own drivers. The generic ones can cause this conflict.
3. Reboot once a week. I know, it's basic. But the WLAN service can get corrupted after long uptime. A simple restart clears it.

That's the whole fix. If none of this works, try a system restore point from before the error started. Or reset your network adapter: Settings > Network & Internet > Advanced network settings > Network reset. That's a nuclear option, but it works.

Good luck. You got this.