The Endpoint Mapper Limit Changed Under Windows Server. Four October Update Notes Don't List It.
The Endpoint Mapper limit that Microsoft's October 2026 Windows Server updates introduced is described in two Microsoft pages, and neither is the update notes that shipped with it. The October 13 cumulative updates for Windows Server 2025, 2022, 2019 and 2016 are documented in four notes. I read the improvement and summary sections of all four on October 19. None of them mentions it. Other…
Microsoft's October 2026 Windows Server updates introduced a new default limit on the memory used by Endpoint Mapper during Endpoint Lookup calls. However, this information is not listed in the update notes that accompany the four Windows Server 2025, 2022, 2019, and 2016 cumulative updates. The change surfaced three days after release, causing Exchange servers to fail and become unstable.
According to Microsoft, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load for workloads like Exchange Server. Symptoms include OWA errors, growing mail queues, and DAG members being unable to reach quorum. A reboot temporarily resolves the issue.
Microsoft has provided a mitigation by setting EpmapSavedContextCap to 65536 and rebooting the server. This workaround was shown to solve the problem for several customers. Microsoft is currently investigating a permanent fix.
The lack of mention of this change in the update notes could lead administrators to miss it during deployment. Therefore, it's crucial to track this default limit and apply the recommended mitigation to ensure the stability and performance of Exchange Server workloads on Windows Server 2025, 2022, 2019, and 2016.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
