Fix 0X000009CA: Windows can't connect to this network

You try connecting to a known Wi-Fi network — maybe your home SSID or an office guest network you've used before. Windows spins for a moment, then throws 0X000009CA in a dialog that says "Can't connect to this network." You might see it after a driver update, a Windows update, or just randomly after a reboot. The trigger is almost always a stale authentication state: either the saved profile is corrupted, or the wireless adapter's internal state machine got stuck.

What's actually happening here

The error code maps to STATUS_UNSUCCESSFUL in the NT status hierarchy. In networking terms, the WLAN AutoConfig service attempted the 802.11 association and 4-way handshake, but something in the authentication chain failed silently. The two main culprits: a corrupted profile (the wlan profile stored in %ProgramData%\Microsoft\Wlansvc\Profiles\Interfaces\) or a driver that's holding onto a bad security context. Less common but still relevant: the DHCP client service or the network adapter itself is in a broken state from a prior disconnect.

The reason step 3 in the fix works is that netsh wlan delete profile removes the stored credentials and security parameters, forcing Windows to renegotiate the handshake from scratch. The profile isn't just a convenience — if it contains stale EAP parameters or a mismatched PMKID, the connection fails before it even tries to ask for a password.

The fix — three steps, in order

1. Forget the network and reconnect
   Open Settings > Network & Internet > Wi-Fi > Manage known networks. Find the network that's failing, click Forget. Then re-connect by selecting the SSID from the list and entering the password fresh. This clears the profile from the WLAN service cache. Many people skip this because they think "I know the password, it should just work." It doesn't — the profile is the problem, not the password.
2. Reset the network stack
   If forgetting didn't fix it, open an elevated Command Prompt (Win+R, type cmd, Ctrl+Shift+Enter). Run these commands in order:
   

   netsh int ip reset
   netsh winsock reset
   netsh wlan reset
   ipconfig /release
   ipconfig /renew
   ipconfig /flushdns

   Reboot. This resets the TCP/IP stack, Winsock catalog, and the WLAN service state. The netsh wlan reset command specifically tells the WLAN AutoConfig service to stop and restart its internal state machine, which clears whatever stuck the adapter in a half-associated limbo.
3. Delete the profile via netsh (nuclear option)
   Open Command Prompt as admin. List all profiles with netsh wlan show profiles. Find the failing network's name. Delete it with:
   

   netsh wlan delete profile name="YourNetworkName"

   Replace YourNetworkName exactly as it appears — case-sensitive. Then reconnect manually. This deletes the profile at the system level (not just the Windows UI cache), which is deeper than the "Forget" button. I've seen cases where the UI Forget button fails to remove the profile entirely — netsh always works.

If it still fails

If you're still getting 0X000009CA after all three steps, the problem is likely driver-level. Open Device Manager, find your wireless adapter under Network adapters, right-click, and select "Uninstall device." Check the box that says "Delete the driver software for this device" if you're on Windows 11 or recent Win10 builds. Reboot — Windows will reinstall the generic driver. Then visit your laptop manufacturer's support site (Dell, Lenovo, HP, etc.) and download the latest Wi-Fi driver dated within the last 6 months. Notice I said the manufacturer's site, not the chipset vendor's (Intel, Realtek, Qualcomm). The OEM driver includes custom power management and antenna selection settings that the generic driver doesn't. A Windows Update driver might work, but I've seen it fail on Dell XPS 13 and Lenovo ThinkPad X1 Carbon units specifically.

One more thing: check if your router is using WPA3 if your adapter is older than 2020. Some Realtek RTL8821CE adapters on Windows 11 22H2 can't negotiate WPA3 and fall over with this exact error. Drop the router to WPA2/WPA3 mixed mode or WPA2-only as a test.

That's it. Windows networking is fragile, but nine times out of ten this error is a profile or driver state problem, not hardware failure.