Microsoft’s October Patch Tuesday came with a nasty surprise for email admins. Over the weekend, the company confirmed that this month’s Windows Server security updates are breaking Outlook Web Access sign-in and mail delivery on some on-premises Exchange Server systems, and its advice is blunt: don’t uninstall the patch, tweak the registry instead.
The admission went up on Microsoft’s Windows release health dashboard, as reported by BleepingComputer and several security outlets on Sunday and Monday. Users on affected servers may find they can’t sign in to Outlook on the web at all, or that messages sent from Outlook sit in the Outbox forever, never delivered. In some cases Exchange also struggles to reach mailboxes during mailbox replication, and mail queues grow.
That’s the kind of breakage that ruins a Monday morning for IT teams.
A 512-call ceiling nobody asked for
Microsoft has already identified the culprit. The October 2026 Windows security update introduced a default limit on how much memory Endpoint Mapper can use when handling Endpoint Lookup calls, specifically, a cap of 512 simultaneous calls. Endpoint Mapper is a Windows component involved in remote procedure call (RPC) communications, and Exchange is one of the heaviest users of it.
“For workloads such as Exchange Server, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load,” Microsoft wrote in its known-issue entry.
So under light load, everything works. Push the server hard enough and Endpoint Mapper hits the ceiling, RPC lookups start failing, and email grinds to a halt. That also explains why the problem is intermittent across organizations: the severity and onset depend entirely on server load. Microsoft says some Exchange deployments may never develop symptoms.
How to tell if your Exchange is hit by the October Windows Server update
The telltale signs go beyond vague mail slowness. Affected deployments report Exchange Server OWA failing with the error “MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142)”, logged as Event ID 1006 in the application log. Outbox pileups and stalled mailbox replication are the other big giveaways.
Independent reporting has also spotted a pattern Microsoft hasn’t officially confirmed. Writing up the incident, Exchange specialist Rafael Pfister reported that servers fail after roughly 22 to 30 hours of uptime, that a restart restores service, and that the failure returns after about the same interval — along with Outlook clients dropping their mailbox connection and database copies that stop replicating. That timing detail comes from reports, not from Microsoft, so treat it as a field observation rather than official guidance. But if your Exchange box died overnight and recovered after a reboot only to fail again, it fits.
The fix: registry tweak, not uninstall
Microsoft’s workaround is a registry setting that increases the maximum number of simultaneous Endpoint Lookup calls, which in turn lets Endpoint Mapper use more memory. Apply it, restart the device, and monitor; if the problem returns, raise the limit again. The company lists the issue’s status as mitigated rather than fully resolved, and says its investigation continues.
The company was emphatic about one thing: the reported problems are not related to installing the October 2026 security updates for Exchange Server, and customers should not uninstall anything.
“Issues reported are not related to installation of October 2026 security updates for Exchange Server. This is not a ‘known issue’ related to October 2026 Exchange update. Any version of Exchange that runs on impacted versions of Windows could be impacted,” Microsoft said in a separate blog post describing the issues.
That matters because the instinctive admin response to a broken patch is to roll it back. Rolling back the Exchange update would do nothing here — the fault is in the OS update, and removing the security patches would just reopen vulnerabilities for no benefit.
The affected Windows updates are KB5126646 for Windows Server 2025, KB5126655 for Server 2022, KB5126651 for Server 2019, and KB5126868 for Server 2016, per reports from Cybersecurity News and secondary analysis. Microsoft’s own KB page documents the known issue for Windows Server 2025; confirm the mapping for the other three in the release-health entry before acting on them.
Why this keeps happening
There is an almost comedic regularity to Microsoft breaking Exchange with Windows updates. Patch Tuesday landmines have hit on-premises Exchange for years, and this one is especially awkward: the change was a security hardening that throttled Endpoint Mapper’s memory usage and quietly broke a first-party workload running at scale.
Microsoft is still the dominant email platform for large organizations, and on-premises Exchange persists at plenty of them, including government agencies, hospitals, and law firms that can’t or won’t move mailboxes to the cloud. A security update that intermittently kills email access is a serious matter for those shops. The 22-to-30-hour failure cycle, if it holds up, means the outage arrives as a surprise on a server that looked fine after patching — the worst kind of regression.
For admins, the playbook is clear. Check the release-health entry, apply the registry mitigation before your users wake up, and leave the security updates in place. Microsoft says a permanent fix is in development.
FAQ
Why is Exchange sign-in failing after the October Windows Server update?
Microsoft says the October 2026 Windows Server security updates introduced a default limit of 512 simultaneous Endpoint Lookup calls for Endpoint Mapper, the Windows component that handles RPC communications. Heavy Exchange workloads can exceed that ceiling, producing OWA sign-in failures, the MapiExceptionMdbOffline error, messages stuck in the Outbox, and stalled mailbox replication.
Which systems are affected by the Exchange mail flow issue?
Any on-premises Exchange version running on Windows Server 2016, 2019, 2022, or 2025 could be affected, according to Microsoft. The affected updates are KB5126646 (Server 2025), KB5126655 (Server 2022), KB5126651 (Server 2019), and KB5126868 (Server 2016). Whether a given server breaks depends on its load: lightly loaded systems may never show symptoms.
How do you fix the Exchange OWA outage?
Microsoft recommends a registry setting that raises the maximum number of simultaneous Endpoint Lookup calls, then restarting the device. After the restart, monitor the Exchange environment and increase the limit further if problems return. The company explicitly advises against uninstalling the security updates — that would remove protections without fixing the underlying issue.
Are the October Exchange Server security updates the cause?
No. Microsoft says this is not a known issue tied to the October 2026 Exchange Server security updates, and urges customers to keep those installed. The fault is in the Windows Server update itself; any Exchange version on an affected Windows build can be impacted.
Sources: BleepingComputer, Cybersecurity News, Microsoft Windows Release Health Dashboard, kira-ai.de, rasne.dev