Windows Server Update Breaks Exchange: What to Do Now

In short: Microsoft has confirmed that the October 2026 Windows Server security updates can make on-premises Exchange servers unstable under heavy load. Users may be unable to sign in to Outlook on the web and mail can get stuck. Microsoft has shared a registry workaround, advises against uninstalling the updates, and says a fix is in progress.

If your company still runs its own Exchange server, the past week may have brought complaints about Outlook on the web refusing sign-ins or emails sitting in the Outbox. The cause is not your mail server software, and it is not a cyber attack. It is a change in this month's Windows Server update.

What Happened

On 19 October 2026, BleepingComputer, Petri and The Register reported that Microsoft had acknowledged problems with Exchange Server after the October 2026 Windows Server updates were installed. Microsoft documented the issue on its Windows release health dashboard and in a post by the Exchange team titled "Exchange servers may become unstable after installation of October 2026 Windows updates", last updated on 20 October 2026.

According to Microsoft, as quoted in these reports, the October update added a default limit on the memory that the Windows Endpoint Mapper service uses for Endpoint Lookup calls. The default of 512 simultaneous calls may not be enough for Exchange under heavy load. Microsoft has said the problem is not caused by the October 2026 Exchange Server security updates.

Who Is Affected

The issue affects organisations running Exchange Server on premises, on Windows Server versions that received the October 2026 update. Microsoft is quoted as saying that any version of Exchange running on an impacted version of Windows could be affected, which covers Exchange Server 2016, 2019 and Subscription Edition.

Reports differ slightly on the Windows Server versions. BleepingComputer, citing the release health dashboard, lists Windows Server 2019 and later. Petri and The Register list Windows Server 2016, 2019, 2022 and 2025. Check Microsoft's release health page for the list that applies to your build.

Companies using Microsoft 365 or Exchange Online are not running their own Exchange servers, so this specific problem does not apply to their mailboxes. Hybrid setups that keep an on-premises Exchange server for management or mail routing should still check that server.

What It Means for Indian Businesses and Departments

Many Indian manufacturers, hospitals, educational institutions and government offices still run Exchange on their own servers, often because of data location policies or older licences. For them, the risk is practical: email stops flowing during working hours, and the helpdesk is flooded with calls. Because the problem appears under load, it may show up on a busy Monday morning rather than right after patching.

The reports list these symptoms:

• Users cannot sign in to Outlook on the web (OWA).
• Sent emails stay in the Outbox, or mail queues keep growing.
• Mailbox replication or database availability group problems.
• On some servers, the error "MapiExceptionMdbOffline" with Event ID 1006 in the application log.

Some servers may never be affected. Severity depends on the load on each server.

What to Do Now

1. Confirm whether you are exposed: list every server running Exchange, its Windows Server version and whether the October 2026 Windows update is installed.
2. Do not uninstall the update: Microsoft advises against removing the October Windows Server updates, since they also fix security flaws, including an actively exploited one reported this month.
3. Watch for the symptoms: monitor OWA sign-ins, mail queues and the application log for Event ID 1006, and brief your helpdesk on what to look for.
4. Apply Microsoft's workaround if needed: as reported by BleepingComputer, Microsoft's temporary fix is to raise the Endpoint Mapper limit with the registry value EpmapSavedContextCap under HKLM\SOFTWARE\Microsoft\Rpc and then restart the server. Read Microsoft's own post first, back up the registry, and test on one server before rolling it out.
5. Plan for a reboot window: a restart can clear the problem for a while, so agree a quick restart procedure with users while you prepare the workaround.
6. Track Microsoft's permanent fix: check the release health dashboard and Exchange team blog, and plan to apply the fix through your normal patch cycle once it is released.
7. Review your Exchange version: BleepingComputer notes that Microsoft said in July that extended security updates for Exchange 2016 and 2019 would end in October 2026. If you still run these versions, plan an upgrade or a move to a supported platform.

This incident is a good reminder to test monthly updates on a small group of servers before the full rollout. Our guide to a practical patch management process explains how to set that up, and our summary of Microsoft's October 2026 Patch Tuesday covers the security fixes in this month's release.

Frequently Asked Questions

Is this a security breach?

No. Based on Microsoft's statements, this is a stability problem caused by a change in the Windows update, not an attack. Treat it as an operational issue, but keep the security updates installed.

Should we roll back the October Windows update?

Microsoft advises against uninstalling it. Rolling back would remove this month's security fixes. Use the registry workaround and restarts instead, and wait for the permanent fix.

Does this affect Microsoft 365 users?

Mailboxes hosted in Exchange Online are not running on your servers, so this issue does not apply to them. Organisations with a hybrid setup should still check any on-premises Exchange server they keep.

How Affix Center Can Help

Affix Center supports email servers, Windows Server environments and patching for Indian companies and public bodies. Our IT operations team can check whether your Exchange servers are exposed, apply and test Microsoft's workaround, and set up a safer monthly patch routine. If you are thinking about moving off ageing on-premises Exchange, our cloud team can help plan the migration. Contact our team for help.