r/SysAdminBlogs • u/insightrecon • 4h ago
Wrote up the NTLMv1 SSO block from this month’s update (PEAP-MSCHAPv2 Wi-Fi/VPN breaking)
Full disclosure, this is our blog (Insight Recon).
Saw a bunch of threads this week about Wi-Fi and VPN breaking after the October update, so I wrote down what we found. If you’ve got PEAP-MSCHAPv2 set to use the user’s Windows login automatically, it’s getting blocked now on Win 11 24H2+ and Server 2025 unless Credential Guard is on. Typed creds still work. Look for 4025 in the NTLM operational log.
There’s also a script in there that pulls your wireless/wired GPOs out of AD and lists which profiles are still PEAP-MSCHAPv2 with Windows creds, so you can see what’s going to break before users start calling.