October Windows Server update breaks on-premises Exchange email: what to do without uninstalling the patch

Microsoft has confirmed that the Windows Server security updates released on October 13, 2026 can cause problems on Exchange servers that companies run themselves (on-premises). According to BleepingComputer, users may be unable to sign in to Outlook on the web (OWA), and messages sent from Outlook may stay stuck in the Outbox.

Companies that only use Exchange Online, as part of Microsoft 365, are not affected by this issue: it hits Exchange servers the company maintains itself.

What is happening

• The October update introduced a default memory limit for Endpoint Mapper, the Windows component that helps services set up RPC connections. That limit corresponds to 512 simultaneous lookups, which Microsoft says may not be enough for Exchange under heavy load.
• Reported symptoms include failed OWA sign-ins, email stuck in the Outbox, growing mail queues, problems accessing mailboxes during replication and, in some cases, the “MapiExceptionMdbOffline” error with Event ID 1006 in the Application log.
• In the Exchange team’s October 16 advisory, the updates listed are KB5126646 (Windows Server 2025), KB5126655 (2022), KB5126651 (2019), and KB5126868 (2016), as reported by TechRepublic. Exchange Server 2016, 2019, and Subscription Edition (SE) may be affected.
• Microsoft says not every server will be affected the same way: severity depends on load, and some servers may never see the problem.

What to do

Microsoft’s guidance is not to uninstall the updates. The company says the problem is not tied to the October Exchange security updates, but to the Windows ones.

While it works on a permanent fix, Microsoft published a temporary workaround: change a registry key on the affected Exchange server by running the command below from an elevated Command Prompt, then restart the server.

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

After the restart, the recommendation is to monitor the environment and raise the limit if the problem comes back. Before touching the registry, make sure you have a recent backup of the server and make the change during a maintenance window.

One more warning if you still run Exchange 2016 or 2019

According to BleepingComputer, Microsoft stops shipping extended security updates (ESU) for Exchange 2016 and 2019 this month, October 2026. Ivanti, in its October Patch Tuesday analysis, gives October 31 as the end date and notes that this month brought a critical remote code execution flaw for those versions (CVE-2026-70571).

In practice, anyone still relying on those versions needs to decide soon between moving to Exchange Server SE or to Exchange Online.

What every company can review

• Inventory: does your company still have an on-premises Exchange server, even if only to relay email from systems or printers?
• Update routine: are updates tested first on a less critical server, or do they go to all servers at once?
• Monitoring: does someone watch mail queues, logs, and alerts after each update, not just the next day?
• Restarts: is a server that started working again after a restart actually stable, or could the problem return under normal load?
• Exit plan: if Exchange 2016 or 2019 stops getting security updates, what is the plan and the deadline to migrate?

Not every item applies to every environment. What matters is having these answers before email stops.

How CGT can help

CGT supports small and mid-sized businesses with IT management, server updates, and Microsoft 365, within the scope agreed with each client: applying and tracking patches, monitoring services, and planning the move from on-premises Exchange to Exchange Online.

Still running an Exchange server and not sure whether it was affected? Meet CGT and talk to us.

Sources: BleepingComputer, Oct 19, 2026, Exchange team advisory, Oct 16, 2026, TechRepublic, Oct 20, 2026, and Ivanti, October 2026 Patch Tuesday analysis.