When October 2026 Windows Updates Stall Exchange Mail

On 16 October 2026, Microsoft's Exchange team said that Exchange servers have become unstable after the Windows updates released on Patch Tuesday, 13 October 2026. Sign-in to Outlook on the web can fail, and mail queues can grow until email crawls to a halt. If your company keeps Exchange on its own servers, that is the mailbox your staff and your customers use every day.

I look after setups like this. Able Watch is $99 a month: uptime monitoring, with me as the engineer who works the alert. If your mail sits on one of these Exchange servers, write to greg@ableadmins.com and I will help you see whether Watch fits.

What happened

The Exchange team says these reports are not caused by the October 2026 Exchange Server security updates. The team ties the instability to the October Windows updates. On the Windows release health page, Microsoft says the update added a default limit of 512 simultaneous Endpoint Lookup calls, which may be too low for Exchange under heavy load. An Endpoint Lookup call is a program asking Windows where a service is listening. The RPC Endpoint Mapper is the part of Windows that answers. When that answer is capped and the server is busy, people can notice it as mail that stops moving.

The named updates are KB5126646 on Windows Server 2025, KB5126655 on Windows Server 2022, KB5126651 on Windows Server 2019, and KB5126868 on Windows Server 2016. Exchange Server 2016, Exchange Server 2019, or the Subscription Edition, on those Windows versions, may be affected. Microsoft says some servers may never see a problem, because severity depends on load.

Windows release health marks the issue as Mitigated. The title on that page is Users might be unable to sign in to OWA or send emails on Exchange Server. The issue was opened at 16:19 PT on 16 October 2026. The originating update is KB5126646, OS Build 26100.33650, dated 13 October 2026. Affected platforms are Windows Server 2016, 2019, 2022, and 2025. Microsoft says no client versions are affected, meaning Windows on a person's computer. OWA is simply Outlook on the web.

What you would see is straightforward. People might be unable to sign in to Outlook on the web, or to send mail. Microsoft lists a specific failure, MapiExceptionMdbOffline: Unable to make connection to the server (hr=0x80004005, ec=1142), together with Application log event ID 1006. Queues grow until email crawls to a halt. In a database availability group, Microsoft's name for Exchange servers that hold mailbox copies for one another, members can fail to reach quorum. Quorum is the point where enough servers agree the group can keep running. A reboot may bring service back, and Microsoft says that improvement can be temporary. If that pattern matches the last few weeks, the questions in the next section are what I would ask.

What to do this week

Keeping the October 2026 Windows Server updates in place is the path Microsoft describes. The published workaround is one registry value. Set the DWORD value EpmapSavedContextCap to 65536 under HKLM\SOFTWARE\Microsoft\Rpc, then reboot the server. If the trouble comes back, Microsoft says to raise the value, and only then. The 20 October 2026 FAQ says you can set the value before the updates are installed. It also says there is no imminent follow-up release from Windows or from Exchange. On 19 October 2026, The Register reported that Microsoft had acknowledged the issue, had advised against uninstalling the updates, and had not committed to an out-of-band fix. That phrase means a patch shipped outside the normal monthly release. Read the Microsoft posts linked below before anyone edits the registry. They carry the detail, and your IT person can follow them line by line.

Here is a short list you can forward.

Which of KB5126646, KB5126655, KB5126651, and KB5126868 are installed on each Exchange server?
Since 13 October 2026, has Outlook on the web sign-in failed, and has the outbound queue been growing?
Is the registry value above set to 65536, and did the server reboot after it was set?
If the October Windows updates are still waiting, can that value be set first, with a backup and a reboot your staff expects?

When those answers are in front of you, the next step is usually clear. When the answers match Microsoft's description, the published setting is the path they gave you. When the answers are mixed, it helps to have a person read them with you. I am that person if you want me, and the section just below is how we start.

How Able can help

This is a good fit for Able Watch. For $99 a month I monitor uptime, and a real engineer works the alert. That engineer is me. I aim the checks at the services your people use to read and send mail, and I pick up the alert when a check fails. If your Exchange hosts are in the group Microsoft described, email greg@ableadmins.com with the Windows Server version and a note on how mail has behaved since 13 October 2026. I will read it and write back with a plain plan.

Sources

If a calm watch on that mail server would help, Able Watch is ready when you are.