Microsoft breaks Exchange Server with October Windows Server updates, forces admins into weekend fixes

Registry edit workaround issued; Microsoft advises against uninstalling the update

By LineZotpaper

Published20 October 2026

Read Time2 min

Microsoft has acknowledged that its October 2026 Windows Server updates are destabilising Exchange Server, causing OWA connection glitches and email queues that grind to a halt. The bug, affecting Exchange running on Windows Server 2016, 2019, 2022 and 2025, has forced administrators into marathon weekend repair sessions. Microsoft has provided a registry-based workaround but warned against uninstalling the update.

Microsoft has confirmed that the October 2026 security updates for Windows Server may be interfering with Exchange Server, leading to severe performance issues. The problems are not related to the separate October security updates for Exchange itself, the company said.

The glitch can hit Exchange Server OWA, causing connection errors or lengthy email queues, "with email crawling to a halt," Microsoft wrote. Rebooting the server temporarily alleviates the issue, but a permanent workaround requires a registry edit.

The destabilisation affects Exchange Server 2016, 2019, and the new Subscription Edition (SE). Microsoft stated, "Not all Exchange servers will be impacted by installation of those updates equally; the severity and speed of impact varies based on Exchange server load. Some servers might never see a problem."

The root cause is a default limit on memory used by Endpoint Mapper when handling Endpoint Lookup calls. In its Release Health Dashboard, Microsoft explained: "For workloads such as Exchange Server, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load." The registry setting increases that maximum.

Customer frustration was evident on Microsoft's support page. One administrator wrote: "We have had the problem like every 20h since Wednesday, when we installed the windows updates for October and the exchange su. Reboot only solution," before noting that the registry setting appeared to help. Another fumed: "Also please release your updates tested and without problems. Without giving us the job to test for you. We're already paying for the software and you want to make tests with us?! I spent all weekend on my servers because of this."

Microsoft has yet to commit to issuing an out-of-band fix and said it is investigating. The company has not said how long the registry workaround will be necessary.

Analysis

Why This Matters

IT administrators running Exchange on Windows Server face unplanned downtime, forcing weekend work and risking email disruption for thousands of organisations.
The issue exposes a fundamental quality-control problem in Microsoft’s patching pipeline, eroding trust among enterprise customers who pay for reliability.
Without an official out-of-band fix, companies must either apply a registry tweak or accept periodic server reboots, neither of which is ideal in production environments.

Background

Microsoft ships monthly security updates for Windows Server and Exchange Server. The October 2026 Windows Server updates introduced a new default memory limit on the Endpoint Mapper service that proved too low for Exchange workloads. Microsoft has acknowledged the problem and offered a registry workaround, but has not released a permanent patch. The issue follows a history of problematic updates that have forced IT teams into firefighting mode.

Key Perspectives

Microsoft: The company acknowledges the bug, blames a default memory limit, provides a registry workaround, and advises against uninstalling the updates. It is investigating and will share more information when available. Affected IT administrators: Frustrated by having to spend weekends troubleshooting a problem caused by Microsoft’s untested patches. They expect updates to be stable, especially for critical infrastructure like email servers. Enterprise customers: Caught between an unstable patch and the security risk of skipping updates. The registry workaround is a stopgap, but not all organisations have the in-house expertise to apply it safely.

What to Watch

Whether Microsoft releases an out-of-band update to fix the default memory limit without requiring registry edits.
Any updates to Microsoft’s Release Health Dashboard for Windows Server 2025 and earlier versions.
Community reports of other workloads affected by the same Endpoint Mapper default, which could broaden the impact beyond Exchange.

Sources

Admin: 'I spent all weekend on my servers' after Microsoft breaks Exchange Server with October updates · www.theregister.com - Articles

Checked

12 claims in this story checked against 1 source: 8 supported.

Show each claim

SupportedMicrosoft breaks Exchange Server with October Windows Server updateswww.theregister.com - Articles: “Admin: 'I spent all weekend on my servers' after Microsoft breaks Exchange Server with October updates.”
Supportedforces admins into weekend fixeswww.theregister.com - Articles: “I spent all weekend on my servers because of this.”
SupportedRegistry edit workaround issued; Microsoft advises against uninstalling the updatewww.theregister.com - Articles: “Microsoft strongly advised that customers should not uninstall the October 2026 Windows Server update”
Partly supportedMicrosoft has acknowledged that its October 2026 Windows Server updates are destabilising Exchange Serverwww.theregister.com - Articles: “Microsoft has acknowledged that the October 2026 Windows Server updates may be destabilizing Exchange Server.”
Partly supportedcausing OWA connection glitches and email queues that grind to a haltwww.theregister.com - Articles: “The glitch...can hit Exchange Server OWA, which can throw up connection glitches or cause lengthy email queues, 'with email crawling to a halt.'”
SupportedThe bug, affecting Exchange running on Windows Server 2016, 2019, 2022 and 2025www.theregister.com - Articles: “The software giant says the bug can hit Exchange Servers running Windows Server 2016, 2019, 2022, and 2025.”
Supportedhas forced administrators into marathon weekend repair sessionswww.theregister.com - Articles: “I spent all weekend on my servers because of this.”
SupportedMicrosoft has confirmed that the October 2026 security updates for Windows Server may be interfering with Exchange Serverwww.theregister.com - Articles: “Microsoft has acknowledged that the October 2026 Windows Server updates may be destabilizing Exchange Server.”
SupportedThe glitch can hit Exchange Server OWA, causing connection errors or lengthy email queues, 'with email crawling to a halt,' Microsoft wrote.www.theregister.com - Articles: “The glitch...can hit Exchange Server OWA, which can throw up connection glitches or cause lengthy email queues, 'with email crawling to a halt.'”
Partly supportedRebooting the server temporarily alleviates the issue, but a permanent workaround requires a registry edit.www.theregister.com - Articles: “Rebooting the server might make the problem go away temporarily, but a more permanent workaround is a registry edit.”
Partly supportedThe destabilisation affects Exchange Server 2016, 2019, and the new Subscription Edition (SE).www.theregister.com - Articles: “The destabilization issue could impact Exchange Server 2016, 2019, and the new Subscription Edition (SE), says the Windows maker.”
SupportedMicrosoft stated, 'Not all Exchange servers will be impacted by installation of those updates equally; the severity and speed of impact varies based on Exchange server load. Some servers might never see a problem.'www.theregister.com - Articles: “Microsoft stated, "Not all Exchange servers will be impacted by installation of those updates equally; the severity and speed of impact varies based on Exchange server load. Some servers might never see a problem."”