Endpoint & Detection

NTLM signing in May 2027: what could break in a small office, and how to check now

From May 2027, Windows servers will reject NTLM connections that don't sign. How a small office finds the devices that would fail, before they do.

SMB

Short answer: Microsoft's November 10, 2026 Windows updates began a two-step change to NTLM, an older sign-in method Windows still uses inside office networks. Today, updated Windows computers offer NTLM signing and servers still accept connections that don't sign. From May 2027, Microsoft says Windows servers will require signing by default and reject devices that don't offer it. A scanner, storage box or older application that connects to your server without signing would stop working that day, so the time to find those devices is now, using the audit log Microsoft added in November.

Key facts

  • Will something break in May 2027? Possibly. Microsoft says servers will reject clients that don't offer signing. It does not say which devices those are, so your server's audit log is the answer.
  • What changed November 10, 2026: Windows clients offer NTLM signing by default. Servers accept signed and unsigned clients, and audit events identify the clients that don't sign.
  • What changes in May 2027: Windows servers require NTLM signing by default. Microsoft says rejected clients get the error SEC_E_UNSUPPORTED_FUNCTION, and the server logs it as event 4023.
  • Why: Microsoft ties the change to CVE-2026-118737 and to reducing exposure to NTLM relay attacks.
  • Where to look: Events 4022 (client side) and 4023 (server side) in the Microsoft-Windows-NTLM/Operational log, plus a PowerShell script in Microsoft's KB5135557.
  • Not affected: Kerberos, anonymous connections and Guest connections, according to Microsoft.
  • Source: Microsoft KB5135557, NTLM signing security improvements in Windows, last updated November 10, 2026.

Ridge Core

Obsidian Ridge's Ridge Core includes endpoint MDR and Microsoft 365 or Google Workspace ITDR at $25 per person per month, month-to-month with no minimum and business onboarding separate. A security team monitors and acts 24/7; Obsidian Ridge provides CISSP-led follow-through within one business day, serving the Research Triangle and businesses across the United States.

Discuss Ridge Core

What NTLM signing is, in one paragraph

When a computer opens a shared folder or another resource on a Windows server, the two machines have to agree on who is signing in. NTLM is one of the ways they do it. Signing adds a cryptographic check to that conversation, which makes it much harder for an attacker sitting in the middle to relay it somewhere else. Microsoft's page says the change makes sure authenticated NTLM sessions always set up a session key and negotiate real signing.

What happens in each phase

Phase 1, November 10, 2026. Windows client devices begin offering NTLM signing on all connections by default. Servers accept both signed and unsigned clients, and new audit events start recording which clients don't sign.

Phase 2, May 2027. Windows servers begin requiring NTLM signing by default. Microsoft says clients that don't offer signing will be rejected.

Microsoft lists these versions as affected: Windows 11 versions 23H2 through 26H2, Windows 10 Enterprise LTSC 2021, and Windows Server 2016, 2019, 2022 and 2025. It also says all supported Windows Server versions are capable of signing, so the server is not the problem. The devices that connect to it might be.

Which devices to check first in a small office

Microsoft's page does not name device types. The list below is ours. It is where we would look first, because each of these connects to a Windows shared folder or server and is not a current Windows PC that received the November update:

  • Scanners and copiers that save to a network folder. To save a scan there, the device signs in to the server.
  • Network storage boxes that sign in to the server, or that the server's users reach through it.
  • Imaging acquisition computers in a dental practice, which may run an older Windows build to stay compatible with the imaging software. Our Dentrix, Eaglesoft and Open Dental hardening guide covers why practice software can lag behind Windows releases.
  • Older line-of-business applications that reach files on the server, such as an older practice-management, document-management or tax software install.
  • Anything you cannot patch, such as a machine kept on an old Windows release for one program.

Whether each of these signs is not something we can tell you from here. The audit log can.

One question Microsoft's page leaves open: it says "Windows servers". It does not say whether a Windows 11 PC that shares a folder for the office will enforce the same default. Check that PC's audit log too. It costs nothing.

How to find the devices that don't sign

  1. Install the November 2026 updates on the server and the Windows computers. Phase 1 has to be in place before the audit means anything.
  2. Open the Microsoft-Windows-NTLM/Operational log on the server. Event 4023 records what the server negotiated with each client, and event 4022 records the client side. Microsoft says these rely on NTLM enhanced auditing, described in its auditing overview. On Windows Server 2019 and 2022, that overview says the feature arrives with updates released on or after October 13, 2026.
  3. Filter on the signing flag, not the event level. Microsoft says signed and unsigned connections both log at Warning level. A connection is fine when the SIGN flag (0x10) and the KEY_EXCH flag (0x40000000) are set and the session key status reads Present.
  4. Run Microsoft's script. KB5135557 includes a PowerShell script that reads events 4022 and 4023 and lists every connection without the SIGN flag, with the client address, host name, user and process.
  5. Write down every device the script finds: what it is, who supports it, and whether it can be updated, reconfigured or replaced before May 2027.

If your server runs Windows Server 2016, confirm the events actually appear in its log before you rely on an empty result. Microsoft lists 2016 as affected, and its auditing overview is not consistent about whether 2016 gets the enhanced events.

When to turn enforcement on yourself

Microsoft documents two registry values under HKLM\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0:

Setting0 (default)1
ServerRequireNtlmSignServer accepts signed and unsigned clientsServer rejects unsigned clients. No restart needed.
ClientAllowUnsignedNtlmClient offers signingClient does not offer signing. Microsoft calls this temporary, for compatibility only.

Microsoft suggests setting ServerRequireNtlmSign to 1 early, once auditing shows no unsigned connections. We agree, with one condition: choose a quiet day and keep someone available, so that if a forgotten device fails, it fails while you are watching rather than on a Monday morning in May.

Microsoft also says it might remove these registry keys in the future. Treat them as a way to schedule the change, not a way to avoid it.

The Outlook flaw from the same month

The same Patch Tuesday fixed CVE-2026-124194, an Outlook flaw attackers were already exploiting. Computerworld reports that a crafted message file makes Outlook connect to an attacker's server without the usual warning and leaks the user's NTLMv2 password hash. Microsoft rated it Moderate. The fix ships in the Microsoft 365 Apps and Office LTSC updates, so a fully patched Windows computer is not proof that Outlook is patched.

Two steps from us, not from Microsoft: confirm the Office update installed on every computer that runs Outlook, and make sure the office firewall blocks outbound file-sharing traffic (TCP port 445) to the internet. A leaked hash needs somewhere to go.

What this means for a dental, law or accounting office

For a practice with a server in the closet, May 2027 is a scheduling problem, not an emergency. The risk is an outage on a day nobody chose: the scanner stops saving, the imaging station cannot reach its folder, or a document system cannot open files. Six months is plenty of time to find those devices if someone starts now. It is not enough if nobody looks until the day things stop working.

The on-premises tax server section of our Lacerte, Drake and CCH hardening guide covers the rest of the server baseline.

The short version

  1. Since November 10, 2026, Windows offers NTLM signing by default. In May 2027, Windows servers require it.
  2. Devices that don't sign will be rejected. Microsoft does not say which ones, so check your own log.
  3. Read events 4022 and 4023, or run the script in KB5135557, and list every device without the SIGN flag.
  4. Update, reconfigure or replace each one, then turn on ServerRequireNtlmSign yourself on a day you choose.
  5. Patch Office separately for CVE-2026-124194, and block outbound TCP 445 at the firewall.

The audit itself is a one-off project for whoever manages your server. If you would like a second pair of eyes on what your audit log shows, bring the list to a free review.

Sources

Ridge Core

Obsidian Ridge's Ridge Core includes endpoint MDR and Microsoft 365 or Google Workspace ITDR at $25 per person per month, month-to-month with no minimum and business onboarding separate. A security team monitors and acts 24/7; Obsidian Ridge provides CISSP-led follow-through within one business day, serving the Research Triangle and businesses across the United States.

Discuss Ridge Core

Last updated

November 16, 2026. We refresh this content as the threat landscape and tools evolve.

Questions readers usually ask next

Will the May 2027 NTLM change break anything in my office?

It can. Microsoft says that from May 2027, Windows servers will require NTLM signing by default and reject clients that don't offer it. Anything that signs in to a Windows server with NTLM without signing would fail.

Microsoft does not name which devices those are, so the only reliable answer for your office is the audit log Microsoft added in November 2026.

What changed in the November 2026 Windows update?

Updates released on and after November 10, 2026 make Windows clients offer NTLM signing on all connections by default. Servers still accept signed and unsigned clients, and new audit events record the clients that don't sign. Microsoft ties the change to CVE-2026-118737.

How do I find out which devices don't sign?

Read events 4022 and 4023 in the Microsoft-Windows-NTLM/Operational log, or run the PowerShell script in Microsoft's KB5135557, which lists connections where the signing flag is missing.

Filter on the signing flag itself, not the event level, because Microsoft says signed and unsigned connections both log as warnings.

Can I turn on enforcement before May 2027?

Yes. Microsoft documents a registry value, ServerRequireNtlmSign, that makes a server reject unsigned clients without a restart, and suggests turning it on early once auditing shows no unsigned connections. Do it only after the audit is clean, or you schedule the outage yourself.

Can I keep an old device working after May 2027?

Do not plan on it. Microsoft documents a client setting, ClientAllowUnsignedNtlm, as a temporary compatibility measure and says it might remove these registry keys in the future.

Its page does not describe a server-side exception for May 2027. Plan to update, reconfigure or replace any device that doesn't sign.

Does this affect Kerberos or guest connections?

No. Microsoft says Kerberos is not affected, and that anonymous and Guest connections are exempt in both phases.

Full bio & provenanceSee related service