The Exchange Server October Update Issue: What Breaks, the Registry Fix, and Why Not to Uninstall

The Exchange Server October update problem comes from Windows, not Exchange. According to Microsoft’s Exchange Team blog, the October 13, 2026 Windows Server cumulative updates can make on-premises Exchange servers unstable. Users may fail to sign in to Outlook on the web (OWA), mail can sit in the Outbox, and queues can grow until mail flow stops.

Microsoft’s Exchange Team posted guidance on October 16 and added an FAQ on October 20. The fix for now is one registry value and a reboot. Microsoft says not to uninstall the Windows updates. This post covers which versions are affected, the symptoms, the exact steps and their risks, the uninstall question, how to tell when a lasting fix ships, and why this keeps landing on small organizations that still run Exchange on their own servers.

The short version: if you run Exchange Server 2016, 2019 or Subscription Edition (SE) on Windows Server 2016 through 2025, set EpmapSavedContextCap to 65536 and reboot, during a maintenance window. Keep the October Windows updates installed. As of October 22, 2026, Microsoft says no follow-up release is imminent, so do not wait for one.

Which servers the Exchange Server October update issue affects

The trigger is the October 2026 Windows Server security update, not the Exchange security update released the same day. The Exchange Team’s post, Exchange servers may become unstable after installation of October 2026 Windows updates, names four Windows updates.

Build numbers come from each update’s Microsoft support page, such as KB5126655. The last column comes from Microsoft’s Exchange Server supportability matrix. The Exchange Team says any Exchange version on an affected Windows version could be hit. It also says installing the October Exchange security updates is not required for the problem to appear.

Not every server will break. The Exchange Team says severity and speed depend on server load, and some servers may never see a problem. Exchange Online is not part of this issue. Microsoft’s known-issue entry refers to on-premises Exchange servers only.

The symptoms to look for

Microsoft lists these on its Windows Server 2025 release health page and in the Exchange Team post:

• Users cannot sign in to OWA.
• Messages sent from Outlook stay in the Outbox and are not delivered.
• Exchange has trouble reaching mailboxes during mailbox replication.
• OWA fails with MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142), with Event ID 1006 in the Application log.
• Mail queues grow during the day until mail slows to a halt.
• Database Availability Group (DAG) members cannot reach quorum.

The pattern matters as much as the list. The Exchange Team says failures appear "after certain time." A reboot might clear them for a while. If your help desk saw OWA sign-in complaints that went away after a restart, then came back, the Exchange Server October update issue is the likely cause.

What changed in Windows

The Exchange Server October update issue traces to one change. Microsoft’s release health entry explains it. The October update added a default limit on the memory Endpoint Mapper uses for Endpoint Lookup calls. The default allows 512 simultaneous calls. Microsoft says that for workloads such as Exchange, 512 might not be enough under heavy load.

The registry value raises that limit. The same entry says the setting increases the number of simultaneous lookups allowed, and with it the memory Endpoint Mapper can use. That memory increase is the tradeoff you accept.

The registry workaround, step by step

The Exchange Team’s recommendation for the Exchange Server October update problem, as of its October 20 update:

1. Do not uninstall the October 2026 Windows Server updates.
2. Open an elevated Command Prompt on the Exchange server.
3. Run this command:
   reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
4. Reboot the server.
5. Monitor OWA, queues and replication, and confirm the problem does not return.

To check that the value is set, run reg query "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap. It should show 0x10000, which is 65536.

If the problem comes back, Microsoft says to raise the limit. It also says it has not yet seen a case that needed a value above 65536, and it does not publish a higher number. If you reach that point, open a case instead of guessing.

You can set the value before installing the updates. Microsoft’s FAQ says the key has no effect until the October updates are installed, and it survives the installation. That makes it a reasonable step to add to your patch runbook for any Exchange server still waiting on October patches.

Risks to weigh before you change the registry

The change has tradeoffs:

• More memory for Endpoint Mapper. That is how the fix works. On a server already short on memory, watch resource use after the change.
• It is a temporary mitigation. Microsoft’s release health entry says the issue “can be temporarily mitigated” with the registry change and lists its status as Mitigated.
• Registry edits carry the usual risk. Export the Rpc key or take a backup first, and paste the command rather than retyping it.
• Record the change. Note it in your change log so the next admin, or your managed service provider, knows why it is there when a later update changes the default.

The release health entry also says an additional mitigation is available through Microsoft Support for business. Microsoft does not describe it publicly.

Should you uninstall the Exchange Server October update?

No. The Exchange Team says to install the October Windows updates as soon as possible and not delay them over one Exchange issue. Its FAQ says the October Windows Server updates "carry a significant security payload."

Uninstalling removes those fixes. The registry change handles the Exchange problem.

Uninstalling the October Exchange security update would not help either. The Exchange Team says that update is not the cause. For Exchange 2016 and 2019, the October 2026 Exchange release post says that update went only to organizations in the paid Period 2 ESU program.

For a wider view of the patch dates landing this quarter, see our Q4 2026 platform calendar.

How to know when a lasting fix ships

As of October 22, 2026, there is no date for a lasting fix to the Exchange Server October update issue. The Exchange Team’s FAQ says there is "no imminent follow-up release" from either Windows or Exchange, and that both teams are still analyzing the problem. Some early press reports, including BleepingComputer’s October 19 story, said a fix was in progress. Microsoft’s October 20 FAQ is the more recent word.

Three places will show a change first:

• The release health entry. The known issue on the Windows Server 2022 status page and its siblings is marked “Mitigated.” Watch for “Resolved” and a named KB.
• The KB articles. The “Known issues” section of each update page, such as KB5126646, carries the same entry.
• The Exchange Team post. It keeps a dated list of major updates at the bottom.

The next Patch Tuesday is November 10, 2026. Read its release notes for an Endpoint Mapper change before you assume the registry value can come out. Microsoft has not said whether it should be removed later.

Why small organizations carry this risk

Many organizations have moved mail to Exchange Online. Those still running Exchange on their own hardware often include small nonprofits, associations, schools and local agencies. Many have one server, no DAG and no one watching queues on a Saturday. A problem like the Exchange Server October update issue, which a large shop catches in monitoring, can look like "email is down" to a small office.

Support status makes this sharper. Exchange Server 2016 and 2019 reached end of support on October 14, 2025, according to Microsoft’s Exchange Server 2019 lifecycle page. Microsoft sold a paid Extended Security Update program in two periods. Its Period 2 ESU post says the final ESU updates for both shipped on October 13, 2026. None will follow. Organizations without ESU last got public updates in October 2025, the same post says. From here, only Exchange SE gets updates. Exchange SE was released July 1, 2025, and follows the Modern Lifecycle Policy, according to Microsoft’s SE announcement. It has no fixed end date as long as you stay current.

This is the same pattern we covered with Office 2021 and Windows 11 24H2, and again with .NET 8 and Umbraco 13. Each piece of on-premises software brings its own end date and its own patch risk. For agencies that look after a client’s Exchange server, this month is a good point to check which version it runs and whether the client has a plan past Exchange 2019. Account security on the Microsoft 365 side is changing too, as our post on Microsoft’s SMS MFA retirement explains.

Frequently Asked Questions