Updated New · rolling out

NTLM is being blocked: older devices can no longer sign in

Since the Windows updates of 12 November 2026, NTLM logins without 128-bit encryption are rejected, and from May 2027 servers require NTLM signing. Scanners and systems that sign in with NTLM to Exchange or Windows servers may stop working.

What is happening?

Since Windows updates KB5131079 and KB5131080 took effect on 12 November 2026, updated Windows servers reject NTLM logins that do not support 128-bit encryption. Applications on Windows that sign in to an SMTP SERVER with NTLM can no longer send – even though username and password are correct.

NTLM is a legacy Windows sign-in protocol. Microsoft has deprecated it and is disabling it by default in favour of Kerberos.

Phase 1 (10 November 2026): Windows clients offer NTLM signing by default, and servers log which clients do not sign.

Phase 2 (May 2027): Windows servers require NTLM signing. Clients that do not sign are rejected.

Many scanners, multifunction printers and older ERP integrations sign in with NTLM – for example SMTP login against on-premises Exchange or scan-to-folder. Their firmware often cannot sign.

Timeline

  1. 29 Jan 2026Microsoft publishes the plan to disable NTLM by default.
  2. 10 Nov 2026Phase 1: signing offered, audit events show clients without signing.
  3. 12 Nov 2026KB5131079/KB5131080 take effect. Event ID 4010 appears in the NTLM log and SMTP login with NTLM fails.
  4. May 2027Phase 2: servers require signing and reject other clients.

Who is affected?

  • Scanners and printers using SMTP login against on-premises Exchange
  • Scan-to-folder (SMB) on Windows file servers
  • ERP and payroll systems using NTLM sign-in
  • Old scripts and applications with hard-coded NTLM

Typical errors

Event ID 4010 (NTLM-log) 535 5.7.3 Authentication unsuccessful SMTP AUTH NTLM failed SMB: Access denied / logon failure

What to check

  • Open the NTLM log on the server and look for Event ID 4010. First occurrence on 12 November and none before? Then it is this issue.
  • Check that KB5131079 and KB5131080 are installed and took effect the same day.
  • Test the same username and password with AUTH LOGIN/PLAIN. If it works, the credentials are correct – the failure is NTLM.
  • Enable NTLM auditing on domain controllers and Exchange servers, and find devices without signing in the event log.
  • List which devices use SMTP login (AUTH NTLM) against your own mail server.
  • Check whether the scanner firmware supports NTLMv2 with signing or Kerberos.
  • Note which devices cannot be updated.

What to do

  • Ask SMTP.dk to disable NTLM for your account so login falls back to AUTH LOGIN/PLAIN – or for a hostname/port that offers only AUTH LOGIN/PLAIN. No change to the application (with a new port, only the connection target).
  • Use AUTH LOGIN/PLAIN only over an encrypted connection (STARTTLS), as credentials are otherwise easily decoded.
  • Update scanner and printer firmware to a version that supports signing or Kerberos.
  • Move email sending from devices that cannot be updated to an SMTP SERVER with IP authentication – then the device does not need NTLM at all.
  • Do not use temporary exceptions as a permanent fix.

Sources

Guidance only. Always check Microsoft's current documentation for your setup.