October Windows Updates Cause Widespread Exchange Server Outages
Microsoft has confirmed that recent Windows Server security updates can break on-premises Exchange Server email services, impacting mail flow and webmail access.
Microsoft has officially acknowledged that its October 2026 Windows Server security updates are causing significant disruptions to on-premises Exchange Server environments. The issue, which affects Exchange Server 2016, 2019, and Subscription Edition, can lead to complete outages of webmail access and prevent emails from being delivered.
The root cause has been identified as a new default limit of 512 simultaneous Endpoint Lookup calls introduced in the Windows operating system. This limit, designed to manage memory usage for the Endpoint Mapper component, is insufficient for the demands of heavy Exchange workloads, leading to service failures. The problem is not related to the separate October security updates for Exchange Server itself, meaning servers could experience issues even if their Exchange software remains unpatched.
Several specific Windows updates have been linked to these failures: KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016. The severity of the impact varies depending on the server's workload, with some systems potentially showing no symptoms at all.
Administrators experiencing these issues may observe users unable to log into Outlook on the web, messages stuck in the Outbox, growing mail queues, failures in Database Availability Group quorum, or problems during mailbox replication. A common error message to look for is MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142). Event ID 1006 in the Application log can also serve as an indicator.
Microsoft has provided a registry workaround to address the problem, which involves increasing the Endpoint Mapper call limit. Administrators are instructed to run a specific reg add command in an elevated Command Prompt and then restart the affected server. While this workaround has resolved the issue for some customers, Microsoft currently lists the problem as mitigated rather than fully resolved, with ongoing investigations.
Despite the disruption, Microsoft strongly advises against uninstalling the problematic Windows updates due to the security risks involved. Instead, the registry modification is presented as the recommended path forward. If issues persist after applying the workaround, administrators may need to further increase the call limit, though specific guidance on higher values is not yet detailed.
This incident highlights the critical interdependence between the Windows Server operating system and its applications, particularly for core services like email. It also underscores the ongoing challenges with managing on-premises Exchange Server environments, especially as older versions approach end-of-life support. Microsoft recently noted that October 2026 marks the final scheduled ESU security release for Exchange 2016 and 2019, with future updates exclusively for the Subscription Edition.
Organizations relying on on-premises Exchange Server should carefully review their systems for the symptoms described and apply the provided registry workaround to restore service and prevent further email delivery failures. Continuous monitoring of Windows release health notices and Exchange Team advisories is crucial for staying ahead of such operational disruptions.