Your PEAP-MSCHAPv2 Wi-Fi stopped auto-connecting. That's not a bug, that's the roadmap.

Call: Deploy with care. KB5127648 and KB5126646 enforce NTLMv1 SSO blocking by default on machines where Credential Guard is off and BlockNtlmv1SSO is unset.

What breaks: only SSO pass-through, the “use my Windows logon” option for PEAP-MSCHAPv2 and EAP-MSCHAPv2 on Wi-Fi, wired 802.1X and VPN. Typed credentials still work, and so does machine-certificate auth. If your network already does EAP-TLS, you can stop reading and feel smug.

Microsoft lists this as a planned change, not a known issue, so no fix is coming. About 4 independent commenters in the r/sysadmin megathread hit it, plus two dedicated threads and a Microsoft Q&A post.

Temporary: Set DWORD BlockNtlmv1SSO = 0 under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 (audit mode), and push it by GPO before the update lands. Event 4024 means audit and 4025 means blocked, so you can see who still depends on NTLMv1. Put an expiry date on that exception.

Permanent: EAP-TLS, PEAP-TLS, or TEAP with TLS.

Sources: KB5127648, Windows message center, Microsoft Q&A, r/sysadmin 1x6oy6g, r/sysadmin 1x5mxs1, October megathread, Extreme Networks.