Microsoft confirmed that a set of security patches released on October 13, 2026 are causing serious disruptions in Exchange Server email services. On-premises systems running Exchange Server 2016, 2019, and Subscription Edition are affected—users are deprived of webmail access, emails get stuck unsent, and certain mailboxes become unavailable. Microsoft emphasized that the root cause lies in the Windows Server updates themselves, not in separate Exchange security patches. Even systems fully updated with the latest Exchange fixes can still suffer outages if the underlying Windows Server updates are installed.
Which Updates and Symptoms to Look For
Four specific October Windows updates were identified as triggers. These are KB5126646 for Windows Server 2025, KB5126655 for 2022, KB5126651 on Server 2019, and KB5126868 on Server 2016. Depending on server workload, some environments may display no issues, while others may experience major failures. Key symptoms include inability to log into Outlook on the web, unsent messages remaining in the Outbox, mailbox access issues during replication, or imbalanced cluster states in Database Availability Group setups. Affected servers might show errors like MapiExceptionMdbOffline(hr=0x80004005, ec=1142) or Event ID 1006 in the Application log. Temporarily restarting servers has helped in some cases.
What Microsoft Recommends
To prevent ongoing outages, Microsoft advises against uninstalling the October patches. Instead, it suggests administrators use a registry-based workaround. The fix involves running a command to raise the default limit on simultaneous Endpoint Lookup calls—a value embedded in Windows that governs memory used by the Endpoint Mapper component, which handles remote procedure call communications. The specific instruction is: reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f, followed by a server restart. Environments should be monitored post-update, and if issues recur, the limit should be increased further, although no alternative value is yet provided. Microsoft classifies the problem as mitigated rather than fully resolved, and its investigation remains ongoing.
Compounding timing risks: this comes as Microsoft winds down paid support for Exchange 2016 and 2019. October 2026 marks the final month in which Extended Security Updates (ESU) will be released for those versions, with future patches available only under Subscription Edition.
Administrators can check whether this issue applies to their environment by reviewing their server version, verifying whether the affected Windows updates are installed, and watching for the error indicators mentioned. Applying the registry change is currently the primary mitigation until a permanent resolution is implemented.
Analysis: This incident shows how interdependent Windows Server and Exchange patches are—fixing one layer can accidentally break another. With Exchange 2016/2019 reaching end-of-paid support, many organizations are already stretched thin on maintenance. This makes resilience and careful testing of updates ever more critical. Those still running on-premises Exchange should plan for the inevitability: either move to Subscription Edition sooner or prepare for recurring trade-offs between maintaining legacy infrastructure and accepting potentially disruptive updates. What to watch next: Microsoft’s full fix timeline, whether more performant thresholds for the Endpoint Lookup limits emerge, and how this situation influences migration away from older Exchange versions.
