For Server 2025 NTLM changes, the short answer is that NTLMv1 has been removed, NTLMv2 still works, and Microsoft plans to disable network NTLM by default in the next major Windows Server release. Windows Server 2025 is the transition release: it adds enhanced NTLM auditing now and is due to receive Kerberos improvements that reduce NTLM fallback. Use it to find and remove NTLM dependencies before the default changes.
What Is NTLM and Why Is Microsoft Phasing It Out?
NTLM (NT LAN Manager) is an older Windows challenge-response authentication protocol that Microsoft is phasing out because Kerberos is more secure and NTLM is a common target in credential attacks such as relay and pass-the-hash. Kerberos has been the default for domain authentication since Windows 2000; NTLM survives as a fallback when Kerberos cannot be used.
Microsoft's deprecated features list records that all versions of NTLM, including LANMAN, NTLMv1 and NTLMv2, were deprecated in June 2024 and are no longer under active feature development. Its advice to developers is to call Negotiate, which tries Kerberos first and falls back to NTLM only when necessary.
What Is the Timeline for NTLM Changes?
The NTLM timeline runs from deprecation in 2024 to a planned default-off state in the next major Windows release, with Windows Server 2025 in the middle. Microsoft marks some dates as tentative, so treat the later rows as plans rather than guarantees.
| When | Change | Applies to |
|---|---|---|
| June 2024 | All NTLM versions deprecated | All Windows versions |
| November 2024 (documented) | NTLMv1 removed | Windows 11 24H2 and Windows Server 2025 onward |
| Late 2025 | Auditing of NTLMv1-derived single sign-on credentials rolls out | Windows 11 24H2+ and Windows Server 2025 |
| January 2026 | Microsoft publishes a three-phase plan to disable NTLM by default | Future Windows client and server releases |
| Second half of 2026 (planned) | Phase 2: IAKerb and Local KDC to reduce NTLM fallback | Windows Server 2025 and Windows 11 24H2 or later |
| Next major release (no date) | Phase 3: network NTLM disabled by default, re-enable by policy | Next Windows Server and client releases |
Windows Server 2025 itself is supported until 9 October 2029 (mainstream) and 10 October 2034 (extended), according to Microsoft's lifecycle page, so most organisations will run it through the switch-over.
What Has Already Changed in Windows Server 2025?
Windows Server 2025 has already removed NTLMv1 and added better NTLM auditing; NTLMv2 continues to work. Microsoft's support article on changes to NTLMv1 in Windows 11 24H2 and Windows Server 2025 notes that some NTLMv1 cryptography remains in specific scenarios, such as MS-CHAPv2 used for network sign-in in domain-joined environments.
To close that gap, Microsoft added a registry value, BlockNtlmv1SSO, under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0. In audit mode (0) it logs warning event 4024 when NTLMv1-derived credentials are used for single sign-on; in enforce mode (1) it blocks them and logs error event 4025. Microsoft's published, tentative schedule moves the default from audit to enforce from October 2026 where the value has not been set. The effect is that Wi-Fi, wired 802.1X or VPN single sign-on that depends on MS-CHAPv2 can stop working, although typing credentials manually still works. Devices with Credential Guard enabled are not affected, and Microsoft recommends Credential Guard where hardware supports it.
Is NTLM Disabled in Windows Server 2025?
No. NTLM (NTLMv2) is not disabled in Windows Server 2025. Microsoft's January 2026 plan, published on its Windows IT Pro blog, puts the default-off change in the next major Windows Server release. Even then, NTLM will remain in the operating system and can be re-enabled through policy for legacy needs.
Phase 1 of that plan is enhanced auditing, available now on Windows Server 2025 and Windows 11 24H2. Phase 2 adds IAKerb, which lets Kerberos work when a client can reach the application server but not a domain controller, and Local KDC, which brings Kerberos to local accounts on standalone and workgroup machines. Both were previewed to Windows Insiders in June 2026, with Microsoft targeting availability for Server 2025 and Windows 11 24H2 or later in the second half of 2026. Check your servers' monthly update notes to see when they arrive.
How Do You Find Where NTLM Is Still Used?
You find NTLM use by switching on auditing and reading the NTLM operational log, which records the accounts, processes and machines that still authenticate with NTLM.
- In Group Policy Management, edit a policy linked to your servers and go to Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options.
- Set Network security: Restrict NTLM: Audit Incoming NTLM Traffic to enable auditing for all accounts. On domain controllers, also set Network security: Restrict NTLM: Audit NTLM authentication in this domain.
- On Windows Server 2025 and Windows 11 24H2 or later, enable the newer enhanced NTLM logging policies Microsoft introduced for Phase 1, which add detail such as why Kerberos was not used.
- After a representative period, open Event Viewer → Applications and Services Logs → Microsoft → Windows → NTLM → Operational on each server.
- Export the events and group them by source machine, account and application to build a dependency list.
Auditing only records; it does not block anything, so it is safe to run on production systems.
Why Do Applications Still Fall Back to NTLM?
Applications fall back to NTLM when Kerberos cannot complete, and the reasons are usually configuration rather than the application itself.
-
Connecting by IP address. Kerberos tickets are issued for service names, so connecting to
\\10.0.0.5instead of\\fileserverusually forces NTLM. Reliable DNS matters here; our guide to fixing slow DNS lookups on Windows covers common name-resolution faults. - Missing or duplicate SPNs. A Service Principal Name tells Kerberos which account runs a service. If it is missing or registered twice, Kerberos fails and Negotiate drops to NTLM. This often affects SQL Server service accounts; see our guide on how to install SQL Server for service account setup.
- Hard-coded NTLM. Some older applications and appliances call NTLM directly instead of Negotiate and need a vendor update.
- Local accounts and workgroups. Without a domain controller, there is no Kerberos today, which is what Local KDC is designed to address.
- No line of sight to a domain controller. Remote clients that can reach a server but not a DC fall back to NTLM, the case IAKerb targets.
What Should Admins Do Before NTLM Is Turned Off?
Admins should audit, fix and test now, so the default change in a future release becomes a non-event.
- Enable NTLM auditing on servers and domain controllers, as above.
- Rank dependencies by business impact and fix the easy ones first: replace IP-based connections with DNS names and correct SPNs.
- Ask vendors of applications that call NTLM directly for Kerberos-capable versions.
- Decide on
BlockNtlmv1SSOdeliberately rather than letting the default change surprise your network team, and deploy Credential Guard where supported. - Test "NTLM off" in a lab using the Restrict NTLM deny policies before considering them in production.
- Review health of core Active Directory services while you are there; our explainer on FSMO roles is a useful checklist for domain controller roles.
A Common Mistake We See
The most damaging mistake is jumping straight to a "deny all NTLM" policy on domain controllers without auditing first. Authentication failures then appear as unrelated problems: mapped drives that ask for passwords, printers that vanish, line-of-business apps that will not log in. Audit for a full business cycle, including month-end jobs, before blocking anything.
The second mistake is assuming a new server licence fixes legacy authentication. Moving workloads to Windows Server 2025 gives you the auditing and Kerberos tools, but the dependencies move with the applications unless you fix them.
Frequently Asked Questions
Does Windows Server 2025 support NTLM?
Yes, it supports NTLMv2, which works as before. NTLMv1 was removed starting with Windows Server 2025 and Windows 11 24H2. Microsoft plans to disable network NTLM by default in the next major Windows Server release, while keeping the protocol available to re-enable by policy for legacy needs.
When will Microsoft disable NTLM by default?
Microsoft's January 2026 roadmap places the default-off change in the next major Windows Server and client releases, without a fixed date. Before that, Phase 2 Kerberos improvements, IAKerb and Local KDC, are planned for Windows Server 2025 and Windows 11 24H2 or later in the second half of 2026.
What is the difference between NTLMv1 and NTLMv2?
Both are challenge-response protocols, but NTLMv1 uses much weaker cryptography and can be cracked far more easily. NTLMv2 strengthened the response calculation. Microsoft removed NTLMv1 from Windows Server 2025, and deprecated every NTLM version in 2024, recommending Kerberos through the Negotiate package instead.
How do I check NTLM usage on Windows Server 2025?
Enable the Restrict NTLM audit policies and the enhanced NTLM logging policies through Group Policy, then review Applications and Services Logs → Microsoft → Windows → NTLM → Operational in Event Viewer. The events identify the client, account and process using NTLM so you can trace and fix each dependency.
Will disabling NTLM break Active Directory?
Disabling NTLM does not break Active Directory itself, which relies on Kerberos for domain authentication. It can break applications, devices and connections that still use NTLM, such as access by IP address, misconfigured service accounts or older appliances. Auditing first shows exactly what would be affected before you block anything.
What are IAKerb and Local KDC?
They are Kerberos features designed to remove common reasons for NTLM fallback. IAKerb lets a client authenticate with Kerberos through the application server when it cannot reach a domain controller directly. Local KDC runs a small Kerberos service on the machine so local accounts can use Kerberos instead of NTLM.
Conclusion
Server 2025 NTLM changes are a staged transition: NTLMv1 is gone, NTLMv2 still works, auditing is available now and Kerberos improvements are on the way before NTLM is disabled by default in a later release. Start auditing now and fix dependencies at your own pace. For new or replacement servers, see our Windows Server 2025 collection, including Windows Server 2025 Standard.
Useful Links
| Resource | Link |
|---|---|
| Windows Server 2025 licences | Shop Windows Server 2025 |
| Windows Server 2025 Standard | Buy Server 2025 Standard |
| Active Directory roles | FSMO Roles Explained |
| SQL Server setup | How to Install SQL Server |
| Deprecated features incl. NTLM (Microsoft) | Microsoft Learn |
| NTLMv1 changes (Microsoft) | Microsoft Support |
| Disabling NTLM by default (Microsoft) | Windows IT Pro Blog |
השאירו תגובה