Quick answer: Microsoft says Exchange servers can become unstable after the October 2026 Windows Server updates, not after the Exchange security update. The fix is to install the November 2026 (or a later) update for the Windows Server version that Exchange runs on. Do not uninstall the October update. Until you can patch, a registry workaround, EpmapSavedContextCap set to 65536, was the interim advice.
Since Patch Tuesday on 13 October 2026, administrators have reported Exchange servers that work for a while and then fail, with a restart only helping temporarily. Microsoft’s Exchange team traced it to Windows, and updated its guidance on 10 November 2026. This page explains what is affected, how to confirm it, and the order to fix it.
What is affected
The problem is tied to four October 2026 cumulative updates for Windows Server, and it can hit any Exchange version running on them: Exchange Server 2016, 2019 and Subscription Edition.
| Windows Server version | October 2026 update |
|---|---|
| Windows Server 2025 | KB5126646 |
| Windows Server 2022 | KB5126655 |
| Windows Server 2019 | KB5126651 |
| Windows Server 2016 | KB5126868 |
Microsoft states that the October 2026 Exchange security update (KB5128895) is not the cause, and that installing it is not required for the issue to occur. Early reports blamed it, so check you are looking at the right update.
Symptoms to look for
- Users cannot sign in to Outlook on the web, with an error such as MapiExceptionMdbOffline: Unable to make connection to the server.
- Mail flow slows or stops, so users have trouble accessing or sending email.
- Services appear healthy at first but fail after some hours or days.
- A server restart clears the problem for a while, then it returns.
A recurring pattern of failures that starts soon after 13 October on an updated server points to this issue rather than a mail-database fault.
Why it happens
Microsoft places the cause in the Windows update, not in Exchange. Reporting on the issue links the same October updates to a fix for a denial-of-service vulnerability in the RPC Endpoint Mapper, and Microsoft’s interim workaround raised a limit on simultaneous Endpoint Lookup calls. Treat that explanation as reported detail and read Microsoft’s own post for the authoritative description.
Step 1: confirm you have the October update
On each Exchange server open PowerShell as administrator and check for the KB that matches your Windows Server version, for example Get-HotFix -Id KB5126651 on Windows Server 2019. If it returns a result, the server has the update and is exposed.
Step 2: install the November 2026 update (the fix)
Microsoft’s guidance was updated on 10 November 2026: install the November 2026 or a newer cumulative update for the Windows Server version your Exchange server runs on. Do this in your normal maintenance window.
- Back up Exchange databases and note the current state of services.
- Put the server into maintenance mode or drain it from the DAG as you normally would.
- Install the November 2026 or later cumulative update and restart.
- Check that services start cleanly and mail flows.
Interim workaround if you cannot patch yet
Before the November update was available, Microsoft advised setting a registry value named EpmapSavedContextCap under the RPC key to 65536 from an elevated command prompt, then restarting the server. Use the exact command shown in the Exchange team’s blog post rather than typing a path from memory. If you already created the key in October, you can leave it in place, but it is not required once the November update is installed.
What not to do
- Do not uninstall the October Windows Server updates. Microsoft advises against it, and they also close a security vulnerability. An early support note suggested uninstalling as a temporary measure, which Microsoft’s later guidance replaced.
- Do not wait for a separate Exchange fix. Microsoft says the Windows November update addresses it.
- Do not rely on restarts. They only hide the problem for a while.
After you patch
- Watch the Application and System event logs for repeated service stops or RPC errors over the next few days.
- Test Outlook on the web sign-in and send a test message.
- Document the KB, date and result for your change record.
If you run Exchange on Windows Server 2016, note that the operating system leaves extended support on 12 January 2027. See our Windows Server 2016 end-of-life guide.
Frequently asked questions
Is the October 2026 Exchange security update causing the instability?
No. Microsoft says the cause lies in the October 2026 Windows Server updates, and the Exchange update KB5128895 lists no related known issue.
Which Windows Server updates are affected?
KB5126646 for Windows Server 2025, KB5126655 for 2022, KB5126651 for 2019 and KB5126868 for 2016.
What is the fix?
Install the November 2026 or a later update for the Windows Server version your Exchange server runs on.
Should I uninstall the October update?
No. Microsoft advises against removing the October 2026 Windows Server updates.
Does a restart fix it?
Only temporarily. The symptoms return until the November update is installed.
Can I keep the registry key after patching?
Yes. Microsoft says the key can stay, but it is not required once the November update is installed.
Sources
- Microsoft Exchange Team: Exchange servers may become unstable after October 2026 Windows updates
- Microsoft Support: Exchange servers instability after October 2026 Windows Server updates
- ITdaily: October Windows updates cause instability for Exchange servers
- The Back Room Tech: October Windows updates cause some Exchange servers to become unstable
- Franky’s Web: Exchange Server SE problems with the October updates
Last checked: 15 November 2026. Microsoft may update its guidance, so check the Exchange team blog before you change a production server.

