There are reports of 802.1X authentication failing after KB5127648. What might be affected, and what can be done while investigating?
Is KB5127648 causing 802.1X authentication failures?
Answers
Start by checking which authentication method the affected clients use and comparing their update status with clients that still connect. The report points toward PEAP configurations, but it doesn't establish that every 802.1X setup is affected or that the update is the cause in every case.
Check the client and RADIUS logs alongside the timing of the update. A controlled rollback on a test machine could help narrow down whether the patch is involved.
Reply to this answer
One reported workaround is to set the REG_DWORD value BlockNtlmv1SSO to 0 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0, then restart the client. Some technicians reported that this restored connectivity, but it hasn't been established as a universal fix.
Test it on a limited set of affected machines first. This changes an NTLMv1-related setting, so weigh the security implications and treat it as a temporary workaround rather than a default policy.
Reply to this answer
There is disagreement about whether this is an unexpected PEAP failure or a consequence of planned NTLMv1 blocking. Don't assume that enforcing NTLMv2 elsewhere settles what is happening in the 802.1X authentication path. Check the actual configuration and logs before drawing that conclusion.
Reply to this answer
Certificate-based EAP-TLS is another configuration to consider when reviewing the longer-term setup. Some reports indicate those using certificates avoided the issue, but that's not enough to guarantee every EAP-TLS deployment is unaffected.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_c83+stencilcrank.6:
For multiple computers, that registry value could be deployed through a Group Policy registry preference after testing.