0XC0232000: Wi-Fi stuck on auto-config, fix it in 3 steps

30-second fix: Kill the auto-config with one command

This is the first thing I try on every call. Open Command Prompt as admin — right-click Start, pick "Command Prompt (Admin)" or "Windows Terminal (Admin)". Then run:

netsh wlan set autoconfig enabled=no interface="Wi-Fi"

Replace "Wi-Fi" with your adapter's name if it's different — you can check with netsh wlan show interfaces.

This tells Windows to stop trying to manage the wireless connection entirely. The adapter then falls back to whatever driver-level settings it has. For many folks, that's enough. The error goes away, the Wi-Fi connects, and you're done.

If that didn't work — or if you got a "The parameter is incorrect" message — move on. It means something else is corrupt.

5-minute fix: Reset the driver stack

This handles the 90% case where the driver got confused by a Windows update or a power cycle. Here's the routine:

1. Open Device Manager (devmgmt.msc).
2. Find your wireless adapter under Network adapters.
3. Right-click it, select Uninstall device. Check the box that says "Delete the driver software for this device" if it shows up.
4. Reboot. Windows will reinstall the generic driver on restart.

Don't skip the delete checkbox — that clears corrupted registry entries. I had a client last month whose Dell XPS kept hitting this error after every Windows update. This fix broke the cycle.

After reboot, try connecting. If the error still pops up, it's time for the heavy stuff.

15+ minute fix: NDIS reset and manual driver surgery

This is the nuclear option. It resets the entire networking stack and forces a clean driver install.

Step 1: Reset Winsock and TCP/IP

netsh winsock reset catalog
netsh int ip reset
netsh int ipv6 reset

Run these from an admin command prompt. Reboot after.

Step 2: Wipe the adapter config

netsh wlan delete profile name=*
reg delete HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList /f

This deletes all saved Wi-Fi profiles and the network list cache. You'll need to reconnect to your network manually after.

Step 3: Replace the NDIS driver manually

Most Wi-Fi adapters use a chipset from Intel, Realtek, or Qualcomm. Go to the manufacturer's support site (Dell, HP, Lenovo, or the chipset vendor) and download the latest driver for your exact adapter model. Do not let Windows Update find one — it'll likely reinstall the same broken one.

• For Intel: use the Intel Driver & Support Assistant
• For Realtek: grab the driver from your PC vendor's support page
• Example: for a Realtek 8822CE, search "Realtek 8822CE driver Windows 11"
• Don't use the generic Realtek site — they often bundle crapware

Once downloaded, go to Device Manager, right-click the adapter, choose Update driver > Browse my computer > point to the folder you extracted the driver to.

Still broken? Check for BIOS or hardware failure

If none of this worked, you've got a hardware or firmware issue. Boot into BIOS and look for a "Wireless" or "WLAN" setting — make sure it's enabled. Some laptops have a physical switch or Fn key combo (like Fn+F2) that disables Wi-Fi entirely.

I've seen this error on a Lenovo ThinkPad where the Wi-Fi card was physically loose. Reseating it fixed it. If you're comfortable opening the laptop, try that. Otherwise, a USB Wi-Fi dongle is a cheap workaround.

One last thing: if you're using a VPN or third-party firewall, disable them temporarily. They sometimes hook into NDIS and cause this exact error. Had a client with McAfee that did this every Tuesday morning.