October Windows Server updates can stall on-premises Exchange

October Windows Server updates can stall on-premises Exchange

17 October 2026: Microsoft says the October 2026 cumulative updates for Windows Server can make Exchange Server 2016, 2019 and Subscription Edition unstable under load: Outlook on the web stops connecting, mail queues grow, and database availability group members can lose quorum. The cause is a new limit on the Windows Endpoint Mapper, and Microsoft's advice is to keep the updates and raise that limit with a registry value.

Not yet independently verified. Microsoft lists the issue as mitigated, not fixed, and has not given a date for a permanent fix. The symptoms and the registry value come from Microsoft alone. We will update this when it can be confirmed, and remove this note.

Which updates trigger it

The Exchange team names four Windows updates released on 13 October:

• KB5126646 for Windows Server 2025 (OS Build 26100.33650)
• KB5126655 for Windows Server 2022
• KB5126651 for Windows Server 2019
• KB5126868 for Windows Server 2016

It stresses that the October security updates for Exchange itself are not the cause, and that any Exchange version running on an affected Windows build can be hit. How fast the problem appears depends on load. "Some servers might never see a problem," the team writes, which explains why a quiet test server can pass while a busy production node fails days later.

What the failure looks like

Typical symptoms in the Exchange post are an OWA error reading MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with event ID 1006 in the Application log, queues that build through the working day "with email crawling to a halt", and DAG members unable to reach quorum. A reboot clears the problem for a while, which is why some administrators first blamed hardware or storage.

The Windows release health dashboard explains the mechanism. The October update "introduced a default limit on the amount of memory used by Endpoint Mapper when handling Endpoint Lookup calls", and the default of 512 simultaneous lookups is not enough for workloads such as Exchange under heavy load. Microsoft opened the entry on 16 October and marks it Mitigated.

The registry change Microsoft recommends

Uninstalling the October update would remove that month's Windows security fixes, and Microsoft tells administrators not to. Instead, from an elevated command prompt on each Exchange server:

reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f

Then reboot, watch the server, and raise the value again if the symptoms return. Microsoft says this has solved the problem in the customer cases it has handled so far. Microsoft Support for business also offers an additional mitigation on request.

The value raises the memory Endpoint Mapper may use, so it is worth applying in a maintenance window and recording in the server build standard: a rebuilt or newly added DAG member installed from an older image will hit the same limit. Microsoft says it is still investigating and will publish more when it has it.

Where this leaves patch schedules

For organisations that hold Windows updates on Exchange servers until a week of testing has passed, this is a case where the test may pass and production may still fail, because the trigger is concurrency rather than a feature. Applying the registry value before rolling out the October update to the remaining servers is the cleaner order. Our patch management category lists seven products and our email management category ten.

Sources

• Microsoft Exchange Team Blog: Exchange Servers may become unstable after installation of October 2026 Windows updates, 17 October 2026
• Microsoft Learn: Windows Server 2025 known issues and notifications (entry opened 16 October, read 2026-10-19), 19 October 2026