If Outlook on the web started failing with MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) after the October 2026 Windows Server updates, the cause is a new limit in the RPC Endpoint Mapper. Exchange hits it under load. One registry value and a restart fix it, and Microsoft says not to uninstall the update.
Status as of November 7, 2026: Microsoft lists the issue as Mitigated. The registry change is the documented workaround you can apply yourself, and Microsoft Support has an additional mitigation if that is not enough. The October 26 out-of-band update for Server 2025, KB5134137, still lists it as a known issue, so installing it does not help. Check the November 10 Patch Tuesday notes before removing the workaround.
For owners: this only affects businesses that run their own Exchange server on site. If your email is Microsoft 365 only, you can skip this. If staff can’t open webmail or mail is stuck in the Outbox, send this page to whoever looks after the server.
Quick Fix
Run this in an elevated Command Prompt on each affected Exchange server. It is the exact command from Microsoft’s support article:
reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /fRestart the server. The value does nothing until the reboot. Confirm it stuck:
reg query "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCapThen watch the server through a full business day. The failures build up under load, so a quiet morning proves little. If the symptoms come back, Microsoft says to raise the limit again.
Confirm This Is Your Problem
Check the update. The trigger is the October 2026 security update for your Windows Server version: KB5126646 on Server 2025, KB5126655 on Server 2022, KB5126651 on Server 2019 and KB5126868 on Server 2016. Exchange Server Subscription Edition, 2019 and 2016 are all affected. You do not need the October Exchange security update installed to hit this.
Get-HotFix -Id KB5126646, KB5126655, KB5126651, KB5126868 -ErrorAction SilentlyContinueLook for Event ID 1006. Microsoft’s release health page ties the OWA error to Event ID 1006 in the Application log:
Get-WinEvent -FilterHashtable @{ LogName = 'Application'; Id = 1006 } -MaxEvents 20 |
Format-Table TimeCreated, ProviderName, Message -AutoSize -WrapCheck the queues. In the Exchange Management Shell, queues that keep growing through the day are the other giveaway. Mail sent from Outlook may also sit in the Outbox.
Get-Queue | Sort-Object MessageCount -Descending | Select-Object Identity, Status, MessageCount, NextHopDomain -First 10What Happened
The October updates added a default limit of 512 on the Endpoint Lookup work the RPC Endpoint Mapper holds at once, to cap the memory it uses. Most servers never get close. Exchange makes a lot of these lookups, so a busy server hits the limit and new connections fail. That is why Microsoft says the impact varies with workload and the queues build up through the day.
Raising the cap to 65536 gives Exchange room again. The trade-off is that Endpoint Mapper can use more memory than the new default allows, which is why Microsoft calls this a temporary workaround.
Database Availability Groups and Edge Servers
DAG members. The same bug can stop DAG members from talking to each other or forming quorum. Apply the fix to one member at a time. Move the active databases off a server, or drain it with StartDagServerMaintenance.ps1 if that is your usual routine, then set the value, restart, check that copies are healthy and do the next one:
Move-ActiveMailboxDatabase -Server EX01
Get-MailboxDatabaseCopyStatus -Server EX01Edge Transport. Microsoft’s article does not mention Edge servers, but they run the same Windows update. Check their queues too, and treat climbing queues there the same way.
Do not uninstall the update. It is a security update, and Microsoft’s first instruction is to leave it installed. Removing it reopens what it patched and only puts off the fix.
References
Microsoft Learn: Windows Server 2025 known issues and notifications
Microsoft Support: KB5134137 out-of-band update
Related Posts
October 2026 Patch Tuesday Known Issues
Fix Exchange Database Mount Error 0x80004005
Wi-Fi or VPN Won’t Connect After KB5127648: MS-CHAPv2 Fix
Need help getting Exchange stable again? Contact Rain City Techworks.