Last updated:
Windows updates can bring Exchange environments to a halt after several hours. Microsoft confirms the issue and has published a workaround.
Since Patch Tuesday on October 13, 2026, administrators have reported serious problems with Exchange Server 2016, 2019 and Subscription Edition (SE).
Particularly concerning: affected systems may initially work normally. Problems appear only hours after installation, depending on server load.
🔎 Observed symptoms
* Outlook Web App (OWA) becomes unreachable.
* Emails remain stuck in queues.
* Some Exchange databases are still shown as Mounted even though access fails.
* DAG members may have difficulty reaching quorum.
* A restart may resolve the outage only temporarily.
A typical error in the Application event log:
Event ID 1006
MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142)
⚠️ Affected Windows updates
* Windows Server 2025: KB5126646
* Windows Server 2022: KB5126655
* Windows Server 2019: KB5126651
* Windows Server 2016: KB5126868
Important: the October 2026 Exchange Security Updates are not the actual trigger. The issue can occur even without installing them.
🔬 Technical background
Microsoft confirms that the October Windows updates introduced a new default limit for the RPC Endpoint Mapper.
It limits the number of concurrent endpoint lookup calls to 512.
High Exchange load may reach this limit, causing Exchange components to lose their connection to mailbox databases.
🛠️ Microsoft’s official workaround
Run the following in an elevated command prompt on the affected Exchange server:
|
1 2 |
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f |
Then restart the server in a controlled manner.
The registry value increases the limit for concurrent endpoint lookup calls to 65,536.
Microsoft explicitly recommends not uninstalling the October Windows updates.
Restarts in DAG environments must be coordinated. Afterwards, check mail flow, database access and queues.
My recommendation:
Anyone running Exchange on-premises should now check installed Windows KBs, review event logs and monitor transport queues.
A successfully started Exchange service or a database shown as Mounted does not automatically mean Exchange is actually working.
Source – Microsoft Exchange Team:
