Exchange OWA Not Working After October 2026 Updates? Fix It Without Uninstalling

By Ahmet Tolga KAYA 7 min read
Exchange OWA Not Working After October 2026 Updates? Fix It Without Uninstalling

Exchange OWA not working after the October 2026 updates? You are not alone, and you are not looking at a corrupt mailbox database. Microsoft has confirmed that the October 13 Windows Server security updates can leave some on-premises Exchange servers in a state where OWA sign-in fails, Outlook messages sit in the Outbox, and mail queues keep growing. The fix for Exchange OWA not working does not involve uninstalling anything. It is a single registry value and a reboot.

Why Exchange OWA Is Not Working After the October Updates

According to the Exchange team’s post, Exchange servers may become unstable after installation of the October 2026 Windows Server updates. The trigger is the Windows update itself, not the Exchange security update released the same month. Microsoft explicitly says the issues are not related to the Exchange updates and that you should not uninstall them.

As BleepingComputer reported, the October update added a default limit on the memory the Endpoint Mapper can use for Endpoint Lookup calls. The default of 512 simultaneous calls can be too low for a busy Exchange server. Exchange 2016, Exchange 2019 and Exchange Subscription Edition can all be affected, and how hard it hits depends on server load. Some servers may never show a problem.

Microsoft lists these Windows Server updates in its guidance:

  • KB5126646 for Windows Server 2025
  • KB5126655 for Windows Server 2022
  • KB5126651 for Windows Server 2019
  • KB5126868 for Windows Server 2016

Exchange OWA Not Working: How to Know You Are Hit

Exchange OWA not working is only one face of this bug, and the pattern is distinctive enough to separate it from a generic Exchange outage:

  • Exchange OWA login failed, and the Application log shows Event ID 1006 with MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142).
  • Messages sent from Outlook stay in the Outbox instead of being delivered.
  • Mail queues grow during the day and mail flow slows to a halt.
  • DAG members struggle to reach quorum, and mailbox replication can stall.
  • A server reboot makes everything work again, but only for a while.

That last point is the giveaway. If your Exchange OWA is not working and a restart fixes it temporarily and the problem returns after hours of normal load, you are almost certainly looking at Endpoint Mapper exhaustion rather than a database or certificate problem.

Step 1: Confirm Exchange OWA Not Working Is Caused by This Bug

Run these from an elevated Exchange Management Shell. First check which of the October updates are installed, then look for the telltale event:

Get-HotFix -Id KB5126646,KB5126655,KB5126651,KB5126868 -ErrorAction SilentlyContinue

Get-WinEvent -FilterHashtable @{LogName="Application"; Id=1006} -MaxEvents 50 |
    Where-Object { $_.Message -like "*MapiExceptionMdbOffline*" } |
    Select-Object TimeCreated, Id, ProviderNameCode language: JavaScript (javascript)

Then check how bad the mail flow impact is across the organization:

Get-Queue | Sort-Object MessageCount -Descending | Select-Object Identity, Status, MessageCount

Get-MailboxDatabaseCopyStatus * | Select-Object Name, Status, ContentIndexState, CopyQueueLengthCode language: JavaScript (javascript)

If the hotfix is present, event 1006 shows up with that exact exception, and queues are climbing, move to the workaround.

Step 2: Apply the Registry Workaround

Microsoft’s temporary workaround for Exchange OWA not working raises the Endpoint Mapper limit. From an elevated Command Prompt on the Exchange server, run:

reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /fCode language: JavaScript (javascript)

Note that 65536 is a decimal value, so do not enter it as hex. If you prefer PowerShell, the same change looks like this:

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Rpc" -Name EpmapSavedContextCap -PropertyType DWord -Value 65536 -ForceCode language: PHP (php)

Verify the value was written before you restart, or the Exchange OWA not working symptoms will come back:

reg query "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCapCode language: JavaScript (javascript)
Exchange OWA not working fix: set EpmapSavedContextCap to 65536 and reboot

Step 3: Reboot the Exchange Server Safely

The Exchange OWA not working fix only takes effect after a restart. If the server is a DAG member, do not just hit restart. Put it into maintenance mode first so you do not trigger a failover storm on a server that is already struggling. Move active databases away, drain the transport queues, then reboot:

Set-ServerComponentState -Identity EXCH01 -Component HubTransport -State Draining -Requester Maintenance
Redirect-Message -Target EXCH02.contoso.com
Suspend-ClusterNode -Name EXCH01
Set-MailboxServer -Identity EXCH01 -DatabaseCopyActivationDisabledAndMoveNow $true
Set-MailboxServer -Identity EXCH01 -DatabaseCopyAutoActivationPolicy Blocked
Set-ServerComponentState -Identity EXCH01 -Component ServerWideOffline -State Inactive -Requester MaintenanceCode language: JavaScript (javascript)

Replace EXCH01 and EXCH02 with your own server names. After the reboot, reverse the maintenance mode steps by setting both components back to Active, resuming the cluster node and re-enabling database activation. Microsoft’s guidance is to monitor afterwards and raise the limit only if the problem returns. The Exchange team says it has not yet seen a case where that was needed.

Step 4: Confirm Exchange OWA Not Working Is Resolved

Test-ServiceHealth -Server EXCH01
Test-OwaConnectivity -ClientAccessServer EXCH01 -TrustAnySSLCertificate
Get-Queue | Where-Object { $_.MessageCount -gt 100 }Code language: JavaScript (javascript)

Watch the queues for a few hours under real load, not just right after the reboot. Because a restart alone hides the problem temporarily, a clean result in the first ten minutes proves nothing. Check again after the busiest part of your day.

Once the queues stay low and sign-in succeeds under load, the Exchange OWA not working problem is resolved on that server. Repeat the same steps on every Exchange server in the organization, because the registry value is set per server.

Patch Before You Get Hit: Avoid Exchange OWA Not Working in the First Place

If you have not yet installed the October Windows Server updates on an Exchange server, you can create the value first. Microsoft says the key has no effect until the October updates are installed and stays in place during installation. To keep Exchange OWA not working from hitting you mid-patch, and for anyone staging patches across a DAG, add the registry value to your pre-patch checklist, then install the updates, then reboot as usual.

Do not skip the Exchange October 2026 update cycle to avoid this. The Exchange team advises installing them as soon as possible because of their security payload. If you are still catching up on Exchange security patching in general, our guide on how to patch the CVE-2026-96940 Exchange Server flaw safely walks through a safe order of operations.

When Will There Be a Real Fix?

At the time of writing, there is no release date for a permanent fix. The Exchange team’s post says there is no imminent follow-up release from Windows or Exchange, and that both teams are still analyzing the issue over the long term. Treat the registry value as the supported answer to Exchange OWA not working for now, and check the Windows release health page and the Exchange team blog for updates.

Also keep in mind the broader lifecycle picture: BleepingComputer notes that Extended Security Updates for Exchange 2016 and 2019 end this month, so if you are still on those versions this is a good prompt to plan your move to Exchange Subscription Edition.

Read more: KB5124008 Breaks Certificate-Based Always On VPN on Windows 11 24H2 and 25H2

Read more: Best Fix Missing Teams Calendar Issue in Exchange On-Premises

Why is Exchange OWA not working after the October 2026 updates?

Microsoft says the October 2026 Windows Server updates added a default cap on Endpoint Mapper memory for Endpoint Lookup calls. On a busy Exchange server the default of 512 simultaneous calls can run out, which breaks OWA sign-in and mail delivery.

Should I uninstall the October 2026 Windows Server updates?

No. Microsoft says not to uninstall them and to install them as soon as possible because of their security fixes. Use the EpmapSavedContextCap registry workaround instead.

What value should EpmapSavedContextCap be set to?

Microsoft’s workaround sets it as a REG_DWORD under HKLM\SOFTWARE\Microsoft\Rpc with a decimal value of 65536, followed by a server reboot. Monitor afterwards and raise it only if the issue returns.

Which Exchange versions are affected?

Exchange Server 2016, Exchange Server 2019 and Exchange Server Subscription Edition can be affected when running on a Windows Server version that received the October 2026 update. Impact depends on server load.

Can I set the registry value before installing the October updates?

Yes. Microsoft says the key can be created before the updates are installed, has no effect until they are, and remains in place during installation.

References

Microsoft Exchange Team: Exchange Servers may become unstable after installation of October 2026 Windows Server updates

Microsoft: Windows Server 2025 release health

BleepingComputer: Microsoft: October Windows Server updates cause Exchange issues

Ahmet Tolga KAYA

Systems Engineer and Technical Writer focused on Windows, Microsoft technologies, infrastructure, cybersecurity, automation, and platform reliability.