802.1x Authentication Failure After Windows 11 Update KB5058411 – Request for Technical Investigation

Question

I am encountering 802.1x enterprise network authentication failures on my Windows 11 device after installing the latest update KB5058411. Below are detailed observations and technical troubleshooting steps. I kindly request your assistance in confirming whether this issue is related to the update and providing remediation guidance.

Issue Description

• Authentication Protocol: Failure occurs during the PEAP (Protected EAP) Phase 2 MSCHAPv2 handshake.
• Packet Capture Analysis: Wireshark logs indicate that after the TLS tunnel is established, the server sends a hash value (EAP-Request/MSCHAPv2 Challenge), but the client fails to respond with subsequent requests (no EAP-Response packets observed).
• Impact: All 802.1x-dependent network connections (corporate Wi-Fi and wired networks) are unavailable.

Environment Details

• OS: Windows 11 Pro,
• Update Status: The issue emerged post-installation of KB5058411. Rolling back the update resolves the problem.
• Network Infrastructure: Ruijie wireless controllers.

Troubleshooting Steps Performed

1. Filtered Wireshark logs using eap && wlan.ta == [client MAC] to validate abnormal server-client interaction.
2. Reset network adapters, updated drivers, and enforced Group Policy (gpupdate /force) with no resolution.

Support Request

1. Please confirm whether KB5058411 includes changes impacting PEAP/MSCHAPv2 workflows (e.g., encryption algorithms, certificate validation logic).
2. Are there any known compatibility issues? If so, are there temporary workarounds or planned patches?
3. Guidance on additional logs or diagnostic steps to expedite resolution.

Attachments:

Thank you for your assistance. Please contact me if further details are required.

Answer 1

We are seeing the same problem with this patch and wired 802.1x with PEAP and MS-CHAPv2. It is acting as if the server side certificate is not trusted and the supplicant does not respond to the EAP POL.

Answer 2

Not an ideal solution, but I've been able to resolve this by uninstalling the network adapter and then rebooting. I usually have the network team bypass the 802.1x until after it's come back up and I've had a chance to run gpupdate /force. I'm not sure if the gpupdate afterwards is necessary.

Answer 3

Greetings,

Have you ever received any feedback on this? I've noticed similar behaviour on various Windows 11 systems with KB5058411 installed. Everything seems to work fine when I switch to 23H2 systems. Radius Server is Cisco ISE with version 3.3 P5.

Answer 4

hi

Is the 802.1x authentication issue resolved?

I have the same issue and I don't know how to fix it.

If you know how to fix it, please help me.

thank you.

Answer 5

Which RADIUS server are you using ?