Microsoft Confirms October Windows Updates Can Break Exchange Server Email Services

Microsoft has confirmed that Windows Server security updates released on October 13, 2026, can disrupt Exchange Server email services, blocking webmail access and leaving messages undelivered.

The issue affects some on-premises systems running Exchange Server 2016, Exchange Server 2019, and Exchange Server Subscription Edition. Microsoft has published a workaround and advises administrators not to uninstall the Windows updates.

The failures stem from changes in Windows Server, not the separate October Exchange Server security updates. Servers can experience problems even without installing the latest Exchange patches, making the underlying operating system update the key factor when investigating these outages.

Affected Updates and Exchange Server Symptoms

Microsoft identified four Windows updates linked to the failures. These are KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016. The impact depends on server workload, and some systems may never develop symptoms.

Users may be unable to sign in to Outlook on the web, while messages sent through Outlook remain stuck in the Outbox. Administrators may notice growing mail queues, failed mailbox access during replication, or problems with Database Availability Group members reaching quorum. Restarting an affected server may restore service temporarily.

One error administrators should watch for is MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142). Affected systems may also record Event ID 1006 in the Application log, providing a useful sign when checking whether an outage matches Microsoft’s report.

According to Microsoft’s Windows release health notice, the October updates introduced a default limit of 512 simultaneous Endpoint Lookup calls. This limit controls memory use by Endpoint Mapper, a Windows component involved in remote procedure call communications. Heavy Exchange workloads can exceed the default allowance.

Increasing the limit allows Endpoint Mapper to use more memory to handle these calls. Microsoft currently lists the issue as mitigated rather than resolved and says its investigation remains ongoing. An additional mitigation is available through Microsoft Support for affected organizations.

Microsoft’s Registry Workaround

Microsoft’s Exchange Team advisory instructs administrators to open an elevated Command Prompt on the Exchange server and run reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f. The server must then be restarted.

After the reboot, administrators should monitor the environment for recurring failures. Microsoft says the limit should be raised further if problems return, although its advisory does not specify a second value. The company reports that this approach has resolved the issue in customer cases it has handled.

Keeping security updates installed remains important. Cybersecurity News recently covered Microsoft’s reissued Exchange Server security update, highlighting the continuing need for supported patches.

The disruption also arrives as Exchange 2016 and 2019 approach the end of their final paid update period. Following earlier reporting on out-of-support Exchange servers, Microsoft says October 2026 marks their last scheduled ESU security release, with future updates limited to Subscription Edition.

An EDR alert reveals an attack. But can it tell the full story? Discover how to reconstruct the attack timeline.