Microsoft’s October security updates have created an unexpected problem for some Exchange Server administrators: email services that stop working properly.
Windows Server updates released October 13, 2026, can disrupt mailbox access, delay outgoing messages and interfere with database replication in on-premises Exchange environments. Microsoft confirmed the problem and published a temporary registry workaround on October 16 while investigating the issue.
The failures complicate an already demanding patch cycle. October’s Patch Tuesday release included fixes for 1,413 vulnerabilities, according to CrowdStrike’s analysis, leaving administrators balancing security protections against potential email disruptions.
October Windows Server updates trigger Exchange failures
In an October 16 advisory, Microsoft’s Exchange Team identified four potentially affected updates:
- Windows Server 2025: KB5126646
- Windows Server 2022: KB5126655
- Windows Server 2019: KB5126651
- Windows Server 2016: KB5126868
Exchange Server 2016, 2019 and Subscription Edition (SE) installations may experience problems, although not every deployment is affected. The issue concerns on-premises Exchange infrastructure rather than the cloud-hosted Exchange Online service.
Symptoms include Outlook on the web (OWA) sign-in failures, messages stuck in Outlook’s Outbox and growing mail queues. Database Availability Group (DAG) members may also struggle to maintain quorum, affecting mailbox availability and replication.
Administrators may encounter MapiExceptionMdbOffline errors alongside Event ID 1006 in the Windows Application Log. Failures can emerge after a period of normal operation, and Microsoft says their severity varies with server load.
According to Windows Server release-health documentation, the October updates introduced a default limit on memory used by the Windows RPC Endpoint Mapper. The limit permits 512 simultaneous Endpoint Lookup calls, potentially insufficient for demanding Exchange workloads.
The failures are associated with Windows Server updates, not the separate October Exchange security patches.
Microsoft’s registry workaround keeps security updates installed
Microsoft recommends increasing the RPC Endpoint Mapper limit rather than uninstalling the affected Windows updates. Administrators can run this command from an elevated Command Prompt on an Exchange server:
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
On servers running the October 2026 Windows updates, the command sets the EpmapSavedContextCap registry value to 65,536. Administrators must then restart the server, monitor Exchange operations and increase the limit further if symptoms return.
Microsoft reports that the workaround has resolved problems in customer cases its teams have assisted with, although it remains a temporary mitigation.
DAG administrators should coordinate restarts with established failover procedures. A reboot alone may temporarily restore service without changing the underlying limit.
The disruption follows September’s faulty Windows updates, which affected Remote Desktop and Hyper-V workloads before Microsoft issued an out-of-band fix. That month’s Patch Tuesday release addressed 974 vulnerabilities, underscoring the scale of security fixes administrators must deploy while maintaining system stability.
Microsoft advises against uninstalling October’s Windows Server updates because doing so would remove their security fixes. Organizations with persistent problems can request additional mitigation assistance through Microsoft Support for business.
As of October 20, 2026, Microsoft’s release-health dashboard lists the Exchange issue as mitigated, with its investigation ongoing. Administrators should continue monitoring mail queues, mailbox access and database replication while awaiting a permanent resolution.
Read more: Another recent Windows update issue has disrupted Remote Desktop connections on some enterprise-managed Windows 11 devices, with Microsoft identifying Administrator protection as a contributing factor.