Forum Discussion
Unable to Connect to a Specific Network after upgrade to windows 11
I am carrying out a windows 10 to 11 upgrade of devices in my domain and observed users are unable to connect to a specific network.
We are using GPO to force the machines to connect to the networks SSID when in range using PEAP on Certification authentication.
The Network shows "Action Needed" and does not connect when you connect to the network manually.
error thrown when checking status of the connectivity from CISCO ISE: 12937 Supplicant stopped responding to ISE after sending it the first inner EAP-MSCHAPv2
After upgrading to Windows 11, devices may fail to connect to a specific Wi-Fi network using PEAP with certificate authentication. The error “Supplicant stopped responding” usually points to a certificate or GPO issue. Make sure the user/machine certificates are properly installed, GPO settings for the network are correctly applied, and the network adapter driver is up to date. Also, try disabling the “Enable identity privacy” option in the network settings, as it can cause issues in newer Windows versions.
4 Replies
After upgrading to Windows 11, devices may fail to connect to a specific Wi-Fi network using PEAP with certificate authentication. The error “Supplicant stopped responding” usually points to a certificate or GPO issue. Make sure the user/machine certificates are properly installed, GPO settings for the network are correctly applied, and the network adapter driver is up to date. Also, try disabling the “Enable identity privacy” option in the network settings, as it can cause issues in newer Windows versions.
Network profile is set to Private.
The certificate used by the PEAP authentication is still valid and trusted.
The Root CA certificate is installed in the Trusted Root Certification Authorities store.
The core issue is likely related to EAP/MSCHAPv2 negotiation failing due to configuration or compatibility issues introduced in Windows 11.
The error "12937 Supplicant stopped responding" indicates the supplicant (Windows wireless client) is not responding to ISE during inner EAP authentication.
