Skip to content
Microsoft

Windows Server October 2026 updates can break Exchange sign‑in and mail flow

October 2026 Windows Server updates may stop Outlook Web Access sign‑in and delay mail on Exchange servers; a registry tweak raises the Endpoint Mapper limit as a temporary fix.

Close-up of a blue screen error shown on a data center control terminal.

If your organisation runs an on‑premises Exchange Server on Windows Server 2019 or newer, the October 2026 Windows Server security updates may suddenly stop users from signing into Outlook Web Access (OWA) and disrupt outbound mail.

The root cause is a new default limit in the Endpoint Mapper, the Windows component that resolves network‑service endpoints. The update caps the number of simultaneous Endpoint Lookup calls at 512. Under heavy Exchange load, this ceiling can be reached, causing the mapper to reject further requests and resulting in OWA sign‑in failures and delayed mail delivery.

Not every Exchange server will see the problem. Servers with modest traffic may never hit the 512‑call limit, while heavily used mailboxes can experience the issue within minutes of the patch being applied. The severity therefore depends on your specific workload patterns.

Microsoft supplies a temporary workaround that raises the limit. Add the following registry value and reboot the affected server:

reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
Modern server rack with blue lighting in a secure data center environment.

Photo by panumas nikhomkhai on Pexels

The EpmapSavedContextCap key tells the Endpoint Mapper to allow up to 65 536 simultaneous calls, far above the default. This change is reversible, simply delete the value and restart the server if you later wish to revert.

It is important to note that the problem is not caused by the October 2026 Exchange Server security updates themselves. Microsoft advises against uninstalling those Exchange patches; the issue originates solely from the Windows Server update.

A related timeline to keep in mind: Microsoft will cease shipping Extended Security Updates (ESU) for Exchange 2016 and Exchange 2019 in October 2026, after a six‑month extension announced in April 2026. Organisations still relying on those ESU licences should plan migration or upgrade paths well before that date.

What you should do now

  1. Verify whether any Exchange servers in your environment are running on Windows Server 2019 or later and have the October 2026 update installed.
  2. If you observe OWA sign‑in errors or delayed mail, apply the registry tweak above on the affected servers and reboot.
  3. Monitor mail flow and OWA log‑on metrics after the change to confirm the issue is resolved.
  4. Begin planning for the end of Exchange 2016/2019 ESU support, assess upgrade options to Exchange 2022 or a move to Microsoft 365.

Terms used in this article

  • Endpoint Mapper, a Windows service that matches network requests to the correct service endpoint.
  • Endpoint Lookup call, a request sent to the Endpoint Mapper to resolve a service address.
  • Registry, the hierarchical database Windows uses to store configuration settings.
  • Extended Security Updates (ESU), a paid support programme that extends security patches for products that have reached end‑of‑life.

The workaround is a stop‑gap measure; future Windows updates may adjust the default limit again. Keep an eye on Microsoft’s release notes and be prepared to re‑apply the registry change if needed.

Read next