Microsoft has confirmed that some on-premises Exchange Server environments can become unstable after the October 2026 Windows Server updates. The issue can affect Outlook on the web (OWA), mail flow and general Exchange stability, and Microsoft says it is linked to the Windows update rather than the Exchange security update itself.
The warning applies to on-premises Exchange environments, including Exchange Server 2016, Exchange Server 2019 and Exchange Server Subscription Edition. Businesses using Exchange Online only are not affected in the same direct way.
Microsoft is still working with the Windows team on the final guidance. A registry-based mitigation is available, but Microsoft has described it as temporary rather than a permanent fix.
What is causing Exchange Server to become unstable?
Microsoft says the problem started appearing after the 13 October 2026 Patch Tuesday Windows Server updates were installed.
The October update introduced a limit on the amount of memory used by the Windows Endpoint Mapper when handling Endpoint Lookup calls. For workloads such as Exchange Server, Microsoft says the default limit may not be sufficient, which can cause Exchange services to become unstable over time.
This is important because the problem is tied to the Windows Server update itself. Microsoft has explicitly said that the Exchange update level is not the cause.
What symptoms can businesses see?
Affected Exchange environments may experience a range of symptoms rather than one single failure.
- Outlook on the web sign-in failures
- mail remaining stuck in the Outbox
- general mail flow disruption
- Exchange services becoming unstable or restarting
- temporary improvement after a server reboot
- errors such as MapiExceptionMdbOffline or 0x80004005
- Event ID 1006 in affected environments
The instability may not appear immediately after patching. Some administrators have reported systems running normally for many hours before the problem develops.
Who is affected?
This issue is relevant mainly to organisations still running on-premises Exchange Server.
That includes:
- Exchange Server 2016
- Exchange Server 2019
- Exchange Server Subscription Edition (SE)
- hybrid Microsoft 365 environments where Exchange Server is still running locally
If your business uses Exchange Online only and has no on-premises Exchange Server, this particular issue is unlikely to affect your email service directly.
Not sure whether your Exchange environment is affected?
KES can check your Exchange Server health, recent Windows updates, event logs and Microsoft 365 hybrid configuration before the issue causes wider disruption.
What should IT teams check now?
If your organisation runs on-premises Exchange, IT teams should check:
- whether the October 2026 Windows Server updates have been installed
- whether Exchange services are stable after patching
- whether users can still sign in to Outlook on the web
- whether outbound messages are leaving normally
- whether Exchange event logs show repeated service or MAPI-related errors
- whether the server becomes unstable again after a reboot
It is also worth reviewing server monitoring and backup status so that any deterioration is detected before users start reporting widespread problems.
Is there a workaround?
Microsoft has acknowledged a registry-based mitigation that increases the maximum number of simultaneous Endpoint Lookup calls allowed by Windows Server.
The Exchange Team has described this as a temporary relief and has said it is waiting for final guidance from the Windows team before presenting a permanent fix.
Because this involves changing a Windows Server registry setting, businesses should not apply it casually or without understanding their Exchange environment. It should be handled by the IT team or Exchange specialist responsible for the server.
Should the October update be removed?
Microsoft has not advised organisations to broadly uninstall the October updates as the first response.
The October security cycle contains important Windows and Exchange security fixes, so rolling back updates can reintroduce vulnerabilities. The safer approach is to follow Microsoft’s current mitigation guidance and monitor the Exchange Team Blog for the final resolution.
If your Exchange environment is already unstable, the decision to remove an update should be made carefully and with a clear rollback and security plan.
Does this affect Microsoft 365 Exchange Online?
No, not in the same direct way.
The warning concerns on-premises Exchange Server. Businesses using Exchange Online only are not running the Windows Server workload that is affected by this issue.
However, some Microsoft 365 tenants still depend on an on-premises Exchange Server for hybrid management, SMTP relay or legacy applications, so it is worth checking whether one still exists in the environment.
You can read more about how we manage and monitor Microsoft 365 environments on our Microsoft 365 monitoring and security management page.
What should businesses ask their IT provider?
If your email environment is managed by an external IT provider, ask them:
- Do we still run any on-premises Exchange servers?
- Have the October 2026 Windows Server updates been installed?
- Have Exchange health and event logs been checked since patching?
- Has Microsoft’s temporary mitigation been assessed for our environment?
- Are our backups and recovery procedures current and tested?
A good answer should be based on the actual server state rather than simply confirming that email appears to be working right now.
Quick answers
Why has Exchange Server stopped working after the October update?
Microsoft says some October 2026 Windows Server updates can cause Exchange Server to become unstable over time because of a Windows Endpoint Mapper resource limit.
Does this affect Exchange Online?
No. The issue affects on-premises Exchange Server, not Microsoft’s cloud-hosted Exchange Online service.
Can the problem appear hours after patching?
Yes. Microsoft and administrators have reported that systems may run normally for some time before instability develops.
Is there a fix?
A temporary registry-based mitigation is available, but Microsoft is still working with the Windows team on the final guidance.
Should businesses uninstall the update?
Not as a general first step. Microsoft has not recommended broad removal of the October updates, which also contain important security fixes.
Sources
