Microsoft Issues Mitigation for Exchange Server Issues Caused by October Windows Updates
A recently identified Windows Server issue is affecting Exchange Server stability in some environments, prompting Microsoft to publish a temporary mitigation while it works on a permanent fix.
Key Takeaways:
- The October Windows Server updates can cause Exchange Server stability issues in affected environments.
- Microsoft traced the problem to Endpoint Mapper request limitations under heavier workloads.
- A registry-based mitigation is available while Microsoft works on a long-term fix.
Organizations running on-premises Microsoft Exchange Server encountered unexpected stability issues after installing October 2026 Windows Server updates. Microsoft has acknowledged that the updates could cause Exchange services to become unreliable in certain environments, particularly those handling heavier workloads. Administrators reported problems ranging from Outlook on the web connectivity failures to broader mail flow disruptions, which left many IT teams scrambling to identify the root cause.
According to Microsoft, this issue caused email queues to grow, user access to messaging services became inconsistent, and some environments experienced database availability group (DAG) issues that affected service continuity. The symptoms often appeared after the updates were deployed, and IT admins spent considerable time troubleshooting Exchange rather than the underlying Windows Server component responsible for the instability. This bug affects Exchange Servers running Windows Server 2016, 2019, 2022, and 2025.
A registry-based mitigation is available to fix Exchange Server issues
To address this problem, Microsoft has issued guidance explaining that the bug originates from a limitation involving Endpoint Mapper requests. The company recommends applying a registry-based mitigation designed to increase capacity and reduce the likelihood of service degradation. Microsoft is continuing its investigation while working toward a more permanent resolution.
“For workloads such as Exchange Server, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load. We are investigating this issue and will provide more information when it is available,” Microsoft explained on the Windows Release Health Dashboard.
The situation highlights a common challenge that IT teams face regarding balancing security and stability. Organizations are encouraged to keep critical security updates in place to remain protected, but doing so may require implementing additional mitigation steps and monitoring affected systems more closely until a long-term fix becomes available. The incident also serves as a reminder that even routine patch deployments can introduce operational risks that must be managed alongside security priorities.
Rabia has a master's degree in Software Engineering and she has years of experience writing professionally about Microsoft products and other technologies. Rabia has also written for OnMSFT.com as well as Windows Report. She is always up to date on t...