For years, Microsoft has had NT LAN Manager (NTLM), a suite of legacy Windows authentication protocols that verify a user’s or computer’s identity. The company is finally phasing out NTLM, and the October update that tightened it hit my Windows 11 Pro machine on October 26, 2026.
Even if you’re not technical, you should know this will eventually touch you, and the check only takes a minute.
The login you never see
Windows picked a better method in 2000, so why is NTLM still running?
Windows handles two kinds of logins. You often see one of them: the password or PIN you type before reaching your desktop. The second takes place much later, when that computer has to prove who you are to a different device. This happens more commonly when you use a shared folder or network printer. For that second login, NTLM is one of the methods used, and it’s the older of the two major options.
In 2000, Microsoft made Kerberos the preferred option. Kerberos makes both sides verify each other, handing out tickets that expire.
This design was sturdier and should have signaled NTLM’s end. But Kerberos identifies network services by their names, and Windows may not find the service identity required for Kerberos authentication if you connect to the service using an IP address. So it falls back to NTLM without telling you.
However, in 2024, Microsoft deprecated NTLM. This means Microsoft stopped adding features to it, but it remained as a safety net.
A handshake with no ID check
How attackers turn NTLM’s blind trust into stolen access
NTLM’s main flaw is that it doesn’t verify the other side. This lack of server authentication is among its most prominent risks. Your computer cannot determine whether a service requesting your credentials is legitimate.
An Outlook bug tracked as CVE-2023-23397 is a very clear example. An attacker sends a specially crafted meeting invite with a reminder sound pointing to a file on one of their own servers. As soon as the reminder is fired, Outlook tries to fetch the sound and, in doing so, automatically sends a Net-NTLMv2 hash of the user’s credentials to the attacker’s server. It doesn’t require anyone to open the invite or click anything.
The attacker can then relay the stolen hash to authenticate against other systems that support NTLM, or attempt to crack it offline to recover the actual password. Russian state-linked groups allegedly exploited this bug for about eight months before it was patched in 2023.
While Outlook was the delivery method, the real weakness was within NTLM, and there had been several leaks even before this one. There were patches, but NTLM’s design is built around trusting whoever asks, so rather than chasing individual bugs, Microsoft is now changing the default.
It’s already switching off
Pieces are gone or locked down, and the main switch is still undated
The rollout has begun, and certain elements have already landed:
|
When |
What changes |
|---|---|
|
Windows 11 24H2 (2024) |
NTLMv1, the oldest version, is removed |
|
October 13, 2026 |
Windows blocks NTLMv1-based single sign-on by default |
|
November 10, 2026 |
PCs offer signed NTLM logins by default, increasing the difficulty of relay attacks (an attacker passing your login along to another server, which uses it on its own) |
|
May 2027 |
Servers begin requiring signed logins |
|
Next major Windows Server and client release |
Network NTLM is off by default, with no date |
These changes don’t happen overnight, and each stage will be introduced by a regular Windows update. According to Microsoft, these timelines may change. Also, being “off by default” doesn’t mean it’s deleted. The code remains on Windows, and admins may still be able to enable it even when Network NTLM is blocked from automatic use.
Kerberos-based fixes are in the works for those times that force NTLM today. Even though these were announced for the second half of 2026, I couldn’t confirm whether these have launched. It’s important they are in place before the switch flips to avoid breaking anything.
Will it break your PC?
If you use Windows 11 at home, you’re unlikely to notice any of this. Your work or school Wi-Fi and VPN connections may fail to connect on their own if they are configured to automatically sign you in via your Windows password, using the MS-CHAPv2 method.
This is a planned change that applies when a Windows security feature called Credential Guard is off. Home networks that have ordinary Wi-Fi passwords don’t use this method.
To check where your PC stands, open your Settings app and navigate to System > About. The change introduced in October applies to Windows 11 24H2 and later where Credential Guard is disabled. Next open Windows Update and check its history for the November 2026 security update. This update introduces the first NTLM signing change. You should refer to your IT department if a work or school computer starts failing.