Opens in a new tab

Microsoft Fixes Exchange Sign-In Issues After Windows Server Updates

  • Home
  • Blog
  • Microsoft Fixes Exchange Sign-In Issues After Windows Server Updates
Microsoft Exchange sign-in issues fixed on Windows Server hardware
Updated November 12, 2026 at 3:46 PM ET

Quick Answer

On-premises organizations can apply these updates to affected servers, while a registry workaround remains available for systems that cannot be patched immediately.

What Happened

Microsoft’s Exchange Team confirmed on November 10 that November 2026 Windows Server updates address instability affecting on-premises Exchange Server. Earlier, Microsoft linked the problem to October cumulative updates that introduced a default memory limit for the Windows RPC Endpoint Mapper, which handles Endpoint Lookup calls.

The resulting symptoms included failures to sign in to Outlook on the web, outgoing messages remaining in the Outbox, growing Exchange queues, mailbox replication problems, and DAG members failing to reach quorum. Microsoft’s Exchange Team also said a server reboot could temporarily resolve the symptoms.

CrowdStrike-related IT outages began on July 19, 2024, when CrowdStrike distributed a faulty update to its Falcon Sensor security software. The update caused widespread problems with Microsoft Windows computers running the software.

The disruption affected daily life, businesses, and governments around the world. Numerous industries were affected, including airlines, airports, banks, hotels, hospitals, manufacturing, stock markets, broadcasting, gas stations, retail stores, and governmental services.

Worldwide financial damage was estimated at tens of billions of dollars.

Are You Affected?

Microsoft identifies Windows Server 2016, 2019, 2022, and 2025 as affected platforms, with Exchange Server 2016, 2019, and Subscription Edition reported as affected Exchange versions. The October 2026 updates associated with the issue are KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016.

Glowing envelope travels through blue beam toward server rack

Affected systems may show the error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) and log Event ID 1006 in the Application Log. Other signs include mail queues growing during the day, OWA sign-in failures, messages remaining in the Outbox, and issues reaching mailboxes during replication.

Microsoft says impact varied by Exchange server load. Some servers degraded quickly, some slowly, and some did not experience a problem.

What to Do Now

  1. Microsoft recommends the November 2026 update or a newer release.
  2. After the restart, monitor the Exchange environment and follow Microsoft’s guidance if the problem recurs.
  3. Inventory Exchange servers with the Exchange Server Health Checker script to identify systems that are behind on cumulative updates, security updates, or manual actions. Reboot after setup and confirm that Exchange services started correctly.

Organizations that created the EpmapSavedContextCap registry key can leave it in place after installing the November 2026 Windows Server updates.

How the October Updates Caused the Failure

The October 2026 Windows Server updates added a default limit on how much memory the Endpoint Mapper could use while handling Endpoint Lookup calls. Under Exchange workloads, additional RPC contexts accumulated until the limit was reached, after which failures could appear gradually.

The Exchange Server version did not determine whether a server was affected. Microsoft said any Exchange version running on an impacted Windows Server version could experience the failures, and the issue could occur even when the October 2026 Exchange Server security updates were not installed.

What About the November Exchange Server Security Update?

Microsoft’s November 2026 Exchange Server security update covers Exchange Server Subscription Edition. Microsoft says security updates are cumulative, so administrators running a supported cumulative update can install the latest security update without first installing every earlier security or hotfix update in sequence.

Server rack shielded by glowing blue energy shield

If an organization uses Exchange in a hybrid configuration, the update is still required on on-premises Exchange servers even when they are used only for management purposes.

Exchange Server 2016 and 2019 are out of support, and Microsoft says those versions are no longer tested for vulnerabilities. Microsoft advises organizations still using Exchange Server 2016 or 2019 to upgrade immediately.

What the Evidence Shows

  • Microsoft reports Windows Server 2016, 2019, 2022, and 2025 as affected, with Exchange Server 2016, 2019, and Subscription Edition reported as affected Exchange versions.
  • Microsoft’s release-health information identifies the October triggering updates as KB5126646, KB5126655, KB5126651, and KB5126868.
  • The Microsoft Security Response Center assigned CVE-2026-77910 an important severity rating, a base score of 8.8, and a temporal score of 7.7. The vulnerability affects Exchange Server and has a CVSS 3.1 attack vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Key Considerations

  • The update requirement applies to on-premises Exchange servers, including management-only servers and Exchange Management Tools systems.
  • The impact varies with server load, so a server may appear healthy immediately after the October update and develop symptoms later.
  • The registry workaround is temporary. Microsoft says it is unnecessary after the November 2026 Windows Server update or a newer update is installed.

FAQ

Which Windows Server and Exchange Server Versions Were Affected?

Microsoft lists Windows Server 2016, 2019, 2022, and 2025 as affected. Exchange Server 2016, 2019, and Subscription Edition were reported as affected Exchange versions, although any Exchange version running on an impacted Windows Server version could be affected.

What Caused the Exchange Server Failures?

The October 2026 Windows Server updates introduced a default memory limit for the RPC Endpoint Mapper when handling Endpoint Lookup calls. Microsoft said the resulting pressure on that service could disrupt Exchange communications under affected workloads.

Should Administrators Uninstall the October 2026 Exchange Server Security Updates?

No. Microsoft says the Outlook on the web issue was not linked to the October 2026 Exchange Server security updates and urges customers not to uninstall them.

Can the Registry Key Remain After Installing the November 2026 Windows Server Update?

Yes. Microsoft says administrators can leave the EpmapSavedContextCap key in place, but it is no longer required after installing the November 2026 Windows Server update or a newer version.

This article reports on publicly available information from the sources listed below. We have no reason to believe it is inaccurate, but we have not independently verified every claim, and details may change as the story develops.

Sources

← All Articles