Microsoft warns October Windows Server updates can disrupt Exchange

Microsoft says some on-premises Exchange Server systems may suffer Outlook on the web sign-in failures and undelivered email after organisations install the October 2026 Windows security updates. The warning covers Windows Server 2016, 2019, 2022 and 2025 systems, although Microsoft says not every server will be affected to the same degree. ¹²

The symptoms include OWA failing to authenticate, messages remaining in Outlook’s Outbox, growing mail queues and problems accessing mailboxes during replication. Some affected servers may also log a “MapiExceptionMdbOffline” error and Event ID 1006. Microsoft’s release-health notice lists the issue as mitigated, but says it is still investigating and recommends contacting Microsoft Support for an additional mitigation where needed. ¹

What is causing the Exchange problems?

Microsoft’s Exchange team says the failures are not caused by installing the October Exchange Server security updates themselves. Instead, the issue can appear after installing the Windows Server updates listed in the company’s advisory, including KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019 and KB5126868 for Windows Server 2016. ²

The company links the problem to a new default limit on simultaneous Endpoint Mapper calls. The limit is intended to control memory usage, but busy Exchange workloads can exceed 512 concurrent lookup calls. That can leave Exchange unable to reach mailboxes or keep up with delivery. ¹²

Microsoft’s temporary workaround

Microsoft advises administrators not to uninstall the Windows updates. Its current workaround is to raise the Endpoint Mapper limit from an elevated Command Prompt, then reboot the Exchange server:

`reg add "HKLM\\SOFTWARE\\Microsoft\\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f`

After rebooting, administrators should monitor the environment and increase the limit again if the symptoms return. Microsoft says the severity depends on server load, so a system that is currently healthy may still need watching after patching. ²

Our opinion

This is exactly the kind of compatibility problem that makes enterprise patching so difficult: the update is important, but the failure may emerge in a separate workload rather than during installation. Microsoft’s advice not to uninstall the patches is sensible, provided administrators test the registry workaround carefully and keep an eye on mail queues, OWA sign-ins and replication. The mitigation is useful, but it is not a substitute for a permanent fix or a clear statement of which server configurations are most vulnerable.