Microsoft’s October Windows updates have left some Exchange servers struggling to deliver email, turning routine security maintenance into a potential business disruption.
Microsoft has confirmed that Windows Server security updates released Oct. 13 can disrupt some on-premises Exchange Server deployments, affecting webmail access, message delivery and mailbox availability. The company says the problem is linked to Windows updates rather than the separate October security updates for Exchange Server.
The affected systems include Exchange Server 2016, Exchange Server 2019 and Exchange Server Subscription Edition (SE). Four Windows Server updates have been identified:
- KB5126646: Windows Server 2025
- KB5126655: Windows Server 2022
- KB5126651: Windows Server 2019
- KB5126868: Windows Server 2016
According to Microsoft’s Exchange Team, affected servers may display a MapiExceptionMdbOffline error and log Event ID 1006 in the Application log. Administrators may also see growing email queues, failed Outlook on the web (OWA) sign-ins and problems with Database Availability Group (DAG) members maintaining quorum. Microsoft says the severity varies with server workload, and some systems may not experience the issue.
Microsoft recommends a registry workaround
According to Microsoft’s Windows release health notice, the October updates introduced an Endpoint Mapper memory limit corresponding to 512 simultaneous Endpoint Lookup calls. That limit may be insufficient for Exchange workloads under heavy load.
Endpoint Mapper helps Windows services establish remote procedure call (RPC) connections. Under heavy Exchange workloads, the default limit may be insufficient, eventually disrupting communication between components and affecting email services.
Microsoft’s Exchange Team recommends against uninstalling the Windows updates. Instead, Microsoft recommends a registry workaround that increases the simultaneous-call limit and allows Endpoint Mapper to use more memory. Administrators should run the following command from an elevated Command Prompt on an affected Exchange server, then reboot it:
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
Microsoft says customer cases it has assisted indicate the change can resolve the problem. Administrators should monitor the server after restarting and raise the limit further if the issue returns. Microsoft lists the issue as mitigated while its investigation continues. An additional mitigation is available through Microsoft Support for affected organizations.
What security and Exchange administrators should check
Employees may find that Outlook on the web will not accept their sign-ins, messages remain stuck in the Outbox, or email delivery slows considerably. A temporary recovery after a server restart does not guarantee that the problem has gone away.
For security teams managing the October Patch Tuesday updates, the practical challenge is restoring email availability while retaining security protection. After applying the workaround and restarting, administrators should test webmail access and message delivery, then monitor email queues, Application logs, and DAG health under normal workloads.
As part of their patch-management procedures, administrators should test updates against representative email traffic. Because the disruption depends on server load, an initially healthy server does not establish that the problem has been resolved. Track the registry workaround separately from installed security updates: patch management and vulnerability management cover related but distinct responsibilities. Record the configuration change and check Microsoft’s guidance before making further adjustments.
Exchange Server 2016 and 2019 reached end of support on Oct. 14, 2025. Organizations enrolled in Microsoft’s Period 2 Extended Security Update program remain eligible for released security updates through the end of October 2026. Administrators should verify their coverage and migration plans alongside the immediate recovery work. Microsoft’s immediate advice is to retain the Windows security updates and apply its documented mitigation, rather than risk trading an availability problem for a security exposure.
Read more: Review Cisco’s critical Smart Software Manager On-Prem fixes and the release checks administrators should make before upgrading to extend your infrastructure patch review beyond Exchange.