Skip to main content
Mallory
← Back to News
widely-deployed-product-advisorypatch-regression

Windows Update Enforces NTLMv1-Derived SSO Blocking, Risking Network Authentication Failures

Patch & Detection Intelligence · 3 sources · Updated 1mo ago · First seen Aug 29, 2025

Windows Update Enforces NTLMv1-Derived SSO Blocking, Risking Network Authentication Failures

Microsoft’s October 2026 Windows security update changes the default handling of NTLMv1-derived single sign-on credentials from auditing to blocking, potentially disrupting Wi-Fi, Ethernet, and VPN authentication. The change affects Windows 11 version 24H2 and Windows Server 2025 systems with Credential Guard disabled when administrators have not explicitly configured the enforcement setting. Microsoft’s advisory KB5066470 explains that, although these operating systems removed the NTLMv1 protocol, authentication scenarios including domain-joined deployments using MS-CHAPv2 can still rely on NTLMv1-derived cryptography. Blocking these credential-generation requests advances Microsoft’s broader NTLM retirement; manually entering credentials remains supported.

An administrator discussion raised concerns about an Absolute Secure Access deployment using RADIUS and PEAP with EAP-MSCHAPv2, while reporting that certificate-based machine authentication still worked. Those deployment-specific claims remain unverified, but illustrate the operational risk for organizations relying on automatic use of logged-on user credentials. Administrators should inventory affected authentication paths, review audit evidence, and test network access after patching. Explicitly configuring Audit mode can provide a temporary exception, but Microsoft warns that it reduces protection. Migration planning should prioritize alternatives such as certificate-based EAP-TLS and address certificate provisioning before enforcement interrupts the connectivity users need to obtain certificates.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

9 events · 1993 – Oct 2026
  1. Reported Oct 15, 20261mo ago

    Administrators raise VPN compatibility and certificate-migration concerns

    In a Reddit discussion about KB5127648, an administrator questioned compatibility with an Absolute Secure Access deployment using PEAP-MSCHAPv2 and described a connectivity dependency preventing user-certificate provisioning for EAP-TLS. Another commenter reported being caught off guard by the update, while participants discussed a registry workaround whose technical details were not authoritatively substantiated in the discussion.

    KB5127648 and Radius with Microsoft Protected EAP (Peap) : r/sysadmin
  2. Oct 2026

    October Windows update enables NTLMv1-derived SSO enforcement by default

    The October Windows security update changed the default from Audit to Enforce mode when the registry control is unset, blocking NTLMv1-derived single sign-on credentials on affected devices without Credential Guard. The change can disrupt legacy Wi-Fi, Ethernet, and VPN authentication; explicitly selecting Audit mode remains a temporary exception.

    Networking problems after the October 2026 Windows update? NTLM might be to blame
  3. Sep 2026

    Microsoft reiterates continued NTLM support alongside its retirement goal

    Microsoft said that in-market Windows client and Windows Server versions would continue supporting NTLM, while reiterating its long-term objective of a Windows platform that does not need it.

    Networking problems after the October 2026 Windows update? NTLM might be to blame
  4. Reported Jul 13, 20264mo ago

    Microsoft removes the NTLMv1 protocol from newer Windows releases

    Microsoft removed the NTLMv1 protocol from Windows 11 version 24H2, Windows Server 2025, and later versions. NTLMv1-derived cryptography nevertheless remained available in some authentication scenarios, including domain-joined deployments using MS-CHAPv2.

    Upcoming changes to NTLMv1 in Windows 11, version 24H2 and Windows Server 2025 | Microsoft Support
  5. Aug 29, 20251y ago

    Microsoft publishes KB5066470 on remaining NTLMv1-derived credentials

    Microsoft published advisory KB5066470 describing auditing and planned enforcement for NTLMv1-derived credentials on devices with Credential Guard disabled. It documented the BlockNtlmv1SSO registry control and warned that enforcement could disrupt affected Wi-Fi, Ethernet, and VPN single sign-on flows.

    Upcoming changes to NTLMv1 in Windows 11, version 24H2 and Windows Server 2025 | Microsoft Support
  6. Aug 2025

    Microsoft introduces auditing for NTLMv1-derived credential use

    Microsoft introduced NTLMv1 usage audit logs to help administrators identify remaining dependencies. Audit mode permits authentication while logging warning Event ID 4024.

    Upcoming changes to NTLMv1 in Windows 11, version 24H2 and Windows Server 2025 | Microsoft Support
  7. 2024

    Microsoft adds NTLM to its deprecation list

    Microsoft formally added NTLM to its deprecation list as part of its transition away from legacy authentication.

    Networking problems after the October 2026 Windows update? NTLM might be to blame
  8. 2023

    Microsoft states its goal of eliminating the need for NTLM

    Microsoft stated that its ultimate goal was to eliminate the need for NTLM on Windows.

    Networking problems after the October 2026 Windows update? NTLM might be to blame
  9. 1993

    NTLM debuts with Windows NT 3.1

    NTLM originated with Windows NT 3.1, beginning its long-standing use in Windows authentication.

    Networking problems after the October 2026 Windows update? NTLM might be to blame
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

4 linked
WindowsWindows 11Windows ServerWindows Server 2025
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.