
The Wi-Fi outage that wasn't an outage
October's Patch Tuesday landed on the 13th, and by the 14th the reports were piling up: corporate Wi-Fi clients could no longer authenticate. WPA2-Enterprise with 802.1X and PEAP, the bread and butter of office wireless, was failing on machines that had just taken KB5127648. Admins on Spiceworks and the Microsoft forums were rolling out registry fixes within hours.
It looked like a broken patch. It wasn't. This was Microsoft enforcing a security change it had been telegraphing since August 2025. The admins who got surprised are the ones who never read the release notes or turned on the auditing that would have warned them. If that stings, it should. I say it as someone who has been the surprised admin before.
Here is what actually changed, how to prove it is your problem before you touch anything, and what the real fix looks like.
What the update changed
KB5127648, the October 13 security update for Windows 11 24H2, 25H2, and 26H2, flipped the default of a registry setting called BlockNtlmv1SSO from Audit (0) to Enforce (1). Microsoft added this line to the KB release notes on October 15, after the first wave of reports:
Windows now blocks the generation of NTLMv1-derived credentials for Single Sign-On. The change applies only where two conditions are true: Credential Guard is disabled, and the registry value was never set explicitly.
Those NTLMv1-derived credentials matter for one specific family of connections: anything doing MS-CHAPv2 inside the single sign-on path. That means PEAP-MSCHAPv2 on WPA-Enterprise Wi-Fi, EAP-MSCHAPv2 on wired 802.1X, and MS-CHAPv2 based VPNs. With Enforce on, the client simply will not hand over the legacy credential. The RADIUS server sees an authentication attempt that goes nowhere. One network engineer reported their NAC logs just showing the request going stale.
The M365 message center notice, MC1508562, says it plainly: this is a planned change, originally documented in August 2025, not a known issue with the October update. Microsoft's September 2025 updates had already put devices in Audit mode, logging an event every time one of these credentials was used. That was your thirteen months of warning, in event form.
Prove it before you fix it
Do not just push the registry workaround because a forum thread said so. Verify the failure matches this exact story first. It takes ten minutes.
1. Confirm the build. Run winver on an affected machine. You are looking for the October cumulative builds: 26100.9711, 26200.9711, or 26300.9711. If the machine is not on one of these, your Wi-Fi problem is something else.
2. Check the NTLM operational log. Open Event Viewer and go to Applications and Services Logs, then Microsoft-Windows-NTLM, then Operational. Look for Event 4025, which means an attempt to use NTLMv1-derived credentials for SSO was blocked by policy. If you only see 4024s, those are Audit mode warnings: the attempt was allowed but logged, which means this machine is not in Enforce mode and is not your patient zero.
3. Check the registry value. Look under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 for a DWORD named BlockNtlmv1SSO. If the value is missing entirely, the update's new default applies. If it is 1, someone set Enforce deliberately. If it is 0, Audit mode is on and this machine should not be failing for this reason.
4. Check Credential Guard. Devices with Credential Guard enabled were already blocking this behavior and are not affected by the October default change. Your fleet management tool or the Device Guard status in msinfo32 can confirm. If Credential Guard is on, look elsewhere.
5. Confirm the symptom pattern. The classic signature: authentication fails when the connection uses the logged-on Windows account (single sign-on), but succeeds when you uncheck that and type domain\username plus password manually. That split is the fingerprint of this change. If both fail, it is a different problem.
The temporary fix
If the diagnosis matches, Microsoft's official temporary option is to put the affected machines back in Audit mode while you fix the underlying dependency. Under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0, create or set the REG_DWORD BlockNtlmv1SSO to 0. Per Microsoft's own guidance, no restart is needed; just reconnect the network. The audit warnings (Event 4024) keep flowing, so you can inventory which connections still rely on the legacy path.
For a fleet, push this through Group Policy or Intune, scoped as narrowly as you can. One Spiceworks admin reported rolling it out both ways the same day. But treat it as a bandage with a label on it. Microsoft is explicit: Audit mode reduces the protection Enforce mode provides and should be a scoped, temporary exception. Document it, set a date to revisit, and mean it.
The real fix: stop using MS-CHAPv2
The durable answer is the one Microsoft keeps recommending and nobody wants to schedule: move your Wi-Fi and VPN authentication off MS-CHAPv2 and onto certificate-based authentication like EAP-TLS or PEAP-TLS. MS-CHAPv2 is weak crypto by modern standards. It carries the same class of problems that got NTLM itself deprecated, and Microsoft is quite open that the NTLM phase-out road map ends with it gone.
This is a project, not a patch: a certificate authority or Intune-issued machine and user certs, RADIUS server changes, wireless profiles redeployed, the VPN gateway reconfigured. It touches everything, which is exactly why it keeps getting deferred. October's update just changed the cost of deferring. Schedule it now, while the memory of the outage is fresh, because the next hardening step will not come with a registry off-ramp.
The boring lesson
The part that keeps getting repeated in these monthly episodes is the least technical one. Microsoft announced this in August 2025. It put Audit mode on in September 2025 so the evidence would accumulate in your own logs. It repeated the warning in the M365 message center on October 14. Then it flipped the switch.
Nobody can read every line of every release note. But the NTLM operational log and message center take-action notices are exactly the low-effort, high-signal feeds that separate the admin who saw October coming from the one who got the helpdesk tickets. Audit first, then enforce. Microsoft did it to the whole fleet this month. The least we can do is run the same playbook on our own networks.
Sources
- October 13, 2026—KB5127648 (OS Builds 26300.9711, 26200.9711 and 26100.9711) — Microsoft Support, October 13, 2026 (release note added October 15, 2026)
- Windows message center: Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard (MC1508562) — Microsoft Learn, October 14, 2026
- October 13, 2026—KB5126646 (OS Build 26100.33650) — Microsoft Support, October 13, 2026
- KB5127648 breaks WPA2-Enterprise (802.1X PEAP) Wi-Fi authentication on Windows 11 — Spiceworks Community, October 14, 2026
- Microsoft fixes VPN issues caused by September Windows updates — BleepingComputer, October 14, 2026



