← Back to the cybersecurity blog

Windows NTLM retirement date: Microsoft's timeline and what it means for your business

By Thilina Manana · COO, Director Técnico de Seguridad hard2bit y socio fundador · Published: 21 November 2026 · Updated: 21 November 2026
Windows NTLM retirement date

When will Microsoft disable NTLM?

Short answer: there is no date. Microsoft will switch network NTLM off by default only in the next major version of Windows and Windows Server, which has no release date and is "subject to change". Current versions keep NTLM. The date that matters now is May 2027, when Windows servers start refusing clients that do not sign NTLM.

Last reviewed: 21 November 2026, against Microsoft's own documentation.

Windows NTLM retirement timeline
WhenChangeWhat you will noticeStatus
June 2024All versions of NTLM deprecatedNothing. NTLM keeps working, with no new featuresDone
Windows 11 24H2 and Windows Server 2025NTLMv1 removed from the operating systemOld devices that only speak NTLMv1 cannot authenticate to these versionsDone
13 October 2026NTLMv1-derived single sign-on blocked by defaultAutomatic Wi-Fi, Ethernet or VPN sign-in using MS-CHAPv2 may fail on Windows 11 24H2+ and Server 2025In force
10 November 2026Windows clients offer NTLM signing on every connectionSome third-party proxies may already fail to authenticateIn force
May 2027Windows servers require NTLM signing by defaultDevices and applications that cannot sign NTLM are rejectedScheduled
"Coming months"IAKerb and Local KDC generally availableFewer cases where Windows has to fall back to NTLMIn preview, behind the "second half of 2026" target
No dateNetwork NTLM disabled by default in the next major Windows releaseNTLM refused unless re-enabled by policy on the new releaseNot released
No dateNTLM removed completelyNone for nowA "longer-term goal"

Compiled by Hard2bit from the Microsoft sources below. Wi-Fi and VPN sign-in is not affected where Credential Guard is on, because it already blocks that use. NTLM signing applies to Windows 11 23H2 to 26H2, Windows 10 Enterprise LTSC 2021 and Windows Server 2016 to 2025.

Does it affect your company? A one-minute check

  • Do printers or multifunction devices scan to a file share?
  • Do you use NAS or storage from vendors other than Microsoft?
  • Do you run legacy business applications, or ones whose vendor no longer issues updates?
  • Does corporate Wi-Fi or VPN sign users in with their Windows username and password (PEAP with MS-CHAPv2)?
  • Is there a third-party proxy or appliance between users and Windows servers?

A yes to any of these means the May 2027 change probably affects you, and it is worth checking before then.

Where each date comes from

  • Deprecation of all NTLM versions, June 2024: Deprecated features for Windows client, which adds that "use of NTLM will continue to work in the next release of Windows Server and the next annual release of Windows".
  • Removal of NTLMv1 in Windows 11 24H2 and Windows Server 2025: Removed features for Windows client.
  • Enhanced NTLM auditing, extended to Windows Server 2022 and 2019 with the updates of 13 October 2026: KB5064479.
  • NTLMv1-derived credentials blocked by default from the October 2026 update: KB5066470, now titled "Manage NTLMv1 changes and prevent network authentication issues in Windows".
  • NTLM signing, 10 November 2026 and May 2027, with its known issue for third-party proxies: KB5135557, which addresses CVE-2026-118737.
  • The three-phase plan, IAKerb, Local KDC and default disablement: Microsoft's Windows IT Pro post Advancing Windows security: disabling NTLM by default (29 January 2026, updated 22 October 2026) and its NTLM retirement FAQ (updated 19 October 2026).

Which Windows versions are affected?

Microsoft's FAQ says default disablement "applies to the future release train" and that in-market versions, including Windows Server 2019, 2022 and 2025 and Windows 10 and 11, "will continue to support NTLM". The switch-off will reach an organisation when it deploys the next major Windows Server release or its client, not through a monthly update.

Current versions still change in the meantime. Windows 11 24H2 and later and Windows Server 2025 block NTLMv1-derived single sign-on by default since October 2026. The NTLM signing changes cover Windows 11 23H2 to 26H2, Windows 10 Enterprise LTSC 2021 and Windows Server 2016 to 2025; Microsoft's list does not include Windows 10 22H2. Microsoft lists the removal of NTLMv1 only from Windows 11 24H2 and Windows Server 2025, so older releases are not covered by it.

What does this mean for a business?

NTLM seldom appears in an asset register, because no one ever chose it. It is what Windows falls back to when Kerberos cannot complete, and in the networks we audit it often turns up in more places than the IT team expects. The places to look are fairly predictable.

  • Legacy business applications that call NTLM directly instead of Negotiate, often from vendors that no longer issue updates.
  • Printers and multifunction devices that sign in to the domain or save scans to a file share.
  • NAS units and storage appliances that only support NTLM for SMB access.
  • Shares, scripts and backup jobs that reach servers by IP address rather than by name, which rules out Kerberos.
  • Machines outside the domain, or users who connect before the VPN is up, and so cannot reach a domain controller.
  • Vendor integrations and appliances with their own NTLM implementation; Microsoft lists third-party proxies with incomplete NTLM support as a known issue with the signing changes.
  • Service accounts and local administrator accounts used to authenticate across the network.

What happens if nothing is done

On most networks the visible effects so far are limited. Since 13 October 2026, on Windows 11 24H2 and later and on Windows Server 2025, Wi-Fi, Ethernet and VPN connections that rely on MS-CHAPv2 single sign-on may stop signing in automatically. Since the November 2026 update, authentication through some third-party proxies may fail; Microsoft's temporary workaround is a registry value on the affected clients. From May 2027, Windows servers will also reject clients that do not offer NTLM signing.

The larger effect comes later. The first new Windows Server or client deployed after default disablement will refuse network NTLM, so every dependency that has not been mapped turns into a support call on the day of the upgrade, although NTLM can be re-enabled by policy as a stopgap. Waiting also leaves the attack surface open: NTLM enables relay attacks and makes pass-the-hash easier, which is why a flaw like the Outlook vulnerability that leaks NTLM hashes matters far more on a network that still accepts NTLM.

What should we do now?

The owner is usually the Active Directory administrator or the managed service provider. The first step costs mostly internal time: turn on auditing and collect logs for a few weeks. As a guide, aim to have the list of devices that do not sign, and written questions to their vendors, ready well before May 2027, and test with a pilot group first. The work is the same whatever date Microsoft eventually sets:

  • Inventory and audit. Turn on NTLM auditing, collect the Microsoft-Windows-NTLM/Operational log centrally and answer three questions: which accounts use NTLM, against which servers, and why.
  • Close relay first, while NTLM is still enabled: require SMB and LDAP signing, enable channel binding and Extended Protection for Authentication on AD CS, Exchange and IIS, and block outbound SMB to the internet.
  • Fix causes, then retire in phases. Replace IP-based access with names, clean up service principal names, agree fixes with vendors, isolate what cannot be fixed and block NTLM by scope, starting with privileged accounts.
  • Prepare for May 2027. Event 4023 on each server shows which clients still connect without NTLM signing; a pilot server set to require signing shows today what will be rejected then.

The technical detail, with the event IDs, the policies and the blocking order, is in our guide to auditing and retiring NTLM without breaking the network. Privileged accounts deserve the earliest attention, in line with an Active Directory tiering model.

How Hard2bit can help

Finding where NTLM still lives is an audit job, and the same exercise usually turns up services without signing, relay paths and over-privileged accounts. As part of our infrastructure and network security audit we carry out an NTLM exposure review ahead of May 2027, with a list of the devices and applications that would be affected. To check your own exposure, contact us.

This article summarises Microsoft's published plans as of 21 November 2026. Microsoft describes its timelines, and its target for default disablement in particular, as subject to change, and the table will be updated as it publishes new information. Configuration changes to authentication should be tested in a limited scope, with a rollback path, before being applied to production.

Frequently asked questions

When will Microsoft disable NTLM? ▾

Microsoft has not given a date. Its stated target is to disable network NTLM by default in the next major release of Windows Server and its client, and it says this is subject to change. NTLM will be disabled by default rather than removed, so it can be re-enabled by policy.

Is NTLMv1 already removed? ▾

Yes, from Windows 11 24H2 and Windows Server 2025. Since the October 2026 security update, those versions also block NTLMv1-derived credentials for single sign-on by default. Microsoft lists the removal only from those releases onwards.

Is NTLMv2 deprecated too? ▾

Yes. Microsoft deprecated every version of NTLM, including NTLMv2, in June 2024. Deprecated means no new features, not that it stops working: NTLMv2 still works on all current versions, and applications should call Negotiate, which tries Kerberos first.

Does it affect Windows 11 or Windows Server 2022? ▾

Network NTLM keeps working on both. Windows 11 24H2 and later have lost NTLMv1 and block NTLMv1-derived single sign-on by default. Windows Server 2022 gets enhanced NTLM auditing through updates from 13 October 2026, and both are covered by the NTLM signing changes of November 2026 and May 2027.

What changed for NTLMv1 in October 2026? ▾

The October 2026 security update switched the default of the BlockNtlmv1SSO setting from audit to enforce on Windows 11 24H2 and later and Windows Server 2025. Wi-Fi, Ethernet and VPN connections using MS-CHAPv2 single sign-on may stop completing automatically, unless the setting is configured or Credential Guard is enabled.

What is the NTLM signing change planned for May 2027? ▾

Under KB5135557, on supported versions with the November 2026 update installed, Windows clients have offered NTLM signing on all connections since 10 November 2026. From May 2027, Windows servers will require it by default and reject clients that do not offer it. Anonymous and guest connections are exempt.

Is NTLM being removed from Windows completely? ▾

Not on any published timeline. Microsoft says the code will remain in Windows for a period after default disablement, so administrators can re-enable NTLM by policy, and describes complete removal as a longer-term goal.

What should a company do first? ▾

Audit. Turn on NTLM auditing, centralise the logs and find out which accounts, servers and applications still use NTLM and why. In parallel, close NTLM relay by requiring signing and Extended Protection, which reduces risk today without waiting for any Microsoft date.

Share this article

Cite this article

If you write about this topic, you can cite it like this:

Thilina Manana (21 November 2026). Windows NTLM retirement date: Microsoft's timeline and what it means for your business. Hard2bit. https://hard2bit.com/en/blog/windows-ntlm-retirement-date-microsoft-timeline/

<a href="https://hard2bit.com/en/blog/windows-ntlm-retirement-date-microsoft-timeline/">Windows NTLM retirement date: Microsoft's timeline and what it means for your business</a> (Hard2bit)

Want a straight answer on scope, priorities and price?

Most organizations reach us mid-question: something needs fixing, nobody has scoped it, and finance wants a number. Thirty minutes with a technical consultant — not a salesperson — gets you a defined scope, priorities ranked by risk and a price range. With what comes out of that call, we turn it into a fixed proposal. We work with organizations in Spain, across the EU and in LATAM.

If your situation is different, tell us anyway — we also take one-off questions on cybersecurity and regulatory compliance.

Based in Spain · Working across the EU and LATAM · ENS High · ISO 27001 · We usually reply in under 24 business hours