Should I uninstall the October Windows updates on my Exchange server?

No. Microsoft's Exchange Team says explicitly to not uninstall the October 2026 Windows Server updates. Instead, apply the registry workaround from an elevated Command Prompt — reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f — reboot the server, and monitor it afterward.

Outlook on the web (OWA) may fail with the error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142), with event ID 1006 logged in the Application log. Mail queues may also grow through the day and delivery slows to a crawl. If you see either on a server that took the October updates, treat it as this issue until you rule it out.

Does this affect Exchange Online?

No. This applies to on-premises Exchange servers, and so to organizations running on-premises or hybrid Exchange. Mailboxes hosted only in Exchange Online are not affected.

Is it the Exchange security update or the Windows update?

The Windows update. Microsoft ties the problem to the October 2026 Windows Server cumulative updates — KB5126646 (Server 2025), KB5126655 (Server 2022), and KB5126651 (Server 2019). The October Exchange Server security update, KB5128895, lists no related known issue.

Blog · 3 min read · October 19, 2026

Exchange Unstable After October 2026 Windows Updates

Microsoft's Exchange Team warned October 16, 2026 that on-prem Exchange may become unstable after the October Windows Server updates (KB5126646 / KB5126655 / KB5126651). Microsoft says do not uninstall — apply a registry workaround and reboot.

ProIT NW, a senior-led Microsoft consultancy in Seattle serving the regulated mid-market, is flagging this for anyone who patches on-premises or hybrid Exchange: on October 16, 2026, Microsoft's Exchange Team warned that Exchange servers may become unstable after the October 2026 Windows Server cumulative updates are installed. If you patch Exchange hosts this month, read this before your next maintenance window. If you already installed the updates, check your servers now.

Everything in this alert — the cause and the fix — comes from Microsoft's Exchange Team blog. It is not our own diagnosis. We're passing it on because the failure is easy to misread as a mail-flow or database problem.

What Microsoft reported

In a post titled "Exchange servers may become unstable after installation of October 2026 Windows updates," the Exchange Team says there are "some reports of customer issues where Exchange Servers become unstable after a set of October updates are installed."

Symptoms to look for

OWA failures. Outlook on the web may fail with MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142), with event ID 1006 logged in the Application log.
Queues backing up. Mail queues may grow through the day and delivery slows to a crawl.

If you see either on a server that took the October updates, treat it as this issue until you've ruled it out.

Which updates trigger it

The trigger is the October 2026 Windows Server cumulative update — not Exchange itself:

Windows Server 2025 — KB5126646
Windows Server 2022 — KB5126655
Windows Server 2019 — KB5126651

The October Exchange Server security update, KB5128895, lists no related known issue. This is a Windows-layer problem showing up on Exchange hosts — the same shape as last month's Windows update problem with Remote Desktop Services.

What Microsoft recommends

Microsoft's guidance is to keep the updates and apply a workaround:

Do not uninstall the October 2026 Windows Server updates.
From an elevated Command Prompt on the Exchange server, run:

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

Reboot the server.
After the reboot, monitor the server. If the issue recurs, raise the limit — use the Exchange Team post itself for that guidance rather than a number from a third party.

Run the command on each affected Exchange server.

How we'd handle it this week. Hold the updates on Exchange hosts you haven't patched yet until you have the workaround staged and a window to reboot — pausing a patch is not the same as uninstalling one. Apply the registry change and reboot on any host that has already taken the update, even if it looks healthy. Watch event ID 1006 and queue depth for the first few business days after the reboot. And if you're in a regulated environment, record the registry value, the date, and the source in your change log so an auditor can follow it later.

The 30-second version

Microsoft's Exchange Team warned on October 16, 2026 that on-premises Exchange servers may become unstable after the October 2026 Windows Server updates (KB5126646 / KB5126655 / KB5126651). The symptom is an OWA MapiExceptionMdbOffline error with event ID 1006, and queues backing up. Do not uninstall the Windows updates; instead add the EpmapSavedContextCap registry value, reboot, and monitor. This is on-premises and hybrid Exchange only — Exchange Online is unaffected. Check the Exchange Team post for any revised guidance, and if you'd like a senior engineer to review your Exchange hosts before the next window, the project intake form takes about three minutes.

Sources and further reading

Pro IT NW handles Microsoft 365 and on-premises/hybrid Exchange for the regulated mid-market in Seattle and the Pacific Northwest. Vendor-neutral, labor-only. This alert relays Microsoft's own published guidance; confirm the current steps on the Exchange Team blog before you act, as Microsoft may revise them.

Questions we get asked

Should I uninstall the October Windows updates on my Exchange server?: No. Microsoft's Exchange Team says explicitly to not uninstall the October 2026 Windows Server updates. Instead, apply the registry workaround from an elevated Command Prompt — reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f — reboot the server, and monitor it afterward.
What's the symptom?: Outlook on the web (OWA) may fail with the error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142), with event ID 1006 logged in the Application log. Mail queues may also grow through the day and delivery slows to a crawl. If you see either on a server that took the October updates, treat it as this issue until you rule it out.
Does this affect Exchange Online?: No. This applies to on-premises Exchange servers, and so to organizations running on-premises or hybrid Exchange. Mailboxes hosted only in Exchange Online are not affected.
Is it the Exchange security update or the Windows update?: The Windows update. Microsoft ties the problem to the October 2026 Windows Server cumulative updates — KB5126646 (Server 2025), KB5126655 (Server 2022), and KB5126651 (Server 2019). The October Exchange Server security update, KB5128895, lists no related known issue.

Related service

Microsoft 365 & Exchange migration

Written by the team at Pro IT NW · Senior-led Microsoft project consultancy · Seattle and the Pacific Northwest, delivered USA-wide.

Share on LinkedIn Follow Pro IT NW