This last update affected also 802.1x EAP-TLS Wired connections. We get "No EAP response from client" on our NAC. We use our own MS PKI for machine certificates and they are deployed via GPO
KB5127648 breaks WPA2-Enterprise (802.1X PEAP) Wi‑Fi authentication on Windows 11
After installing KB5127648, Windows 11 clients can no longer authenticate to our WPA2-Enterprise (802.1X/PEAP) wireless network. Authentication starts but never completes (Event 12014: OneX Held State timeout). WPA2-Personal networks continue to work. The issue reproduces across multiple hardware vendors and wireless chipsets. Uninstalling KB5127648 immediately restores connectivity. Has anyone else observed this with PEAP-based 802.1X environments?
Windows for business | Windows Client for IT Pros | Networking | Other
16 answers
Sort by: Most helpful
-
MarkGRubin-4760 0 Reputation points
2026-10-14T12:39:47.1833333+00:00 Dozens of machines in our org affected by this only recourse so far is to uninstall the update and restart
-
Ashley C 0 Reputation points
2026-10-14T09:13:43.7633333+00:00 This is going down like a sack of potatoes here!
-
Hüseyin NAZLI 0 Reputation points
2026-10-14T08:30:44.7166667+00:00 Hello, I am experiencing the same issue; machines that received the update cannot connect to Wi-Fi using 802.1X. As a workaround, we connect using a different SSID with a username and password, or we uninstall the latest update. -
Spencer Mathews 0 Reputation points
2026-10-14T14:49:49.3966667+00:00 I am having the same problem in my network, but my question is this: If I uninstall the update, won't it just get installed again?