Microsoft October 2026 Windows Server Updates Cause Issues in Exchange Server Environments

Microsoft October 2026 Windows Server Updates Cause Issues in Exchange Server Environments

Microsoft has confirmed that the October 2026 Windows Server security updates are causing email communication and user access issues in certain Microsoft Exchange Server environments.

Following the installation of these updates, administrators have reported several problems, particularly with Outlook on the Web (OWA) access, email delivery failures, and communication errors between Exchange services.

Microsoft has identified the issue as being related to a change in the Windows Server operating system and has provided a temporary workaround. However, as of October 19, 2026, the investigation remains ongoing, and a permanent fix has not yet been released.

For this reason, it is recommended to temporarily postpone the deployment of the affected Windows Server updates on servers hosting Microsoft Exchange until Microsoft releases a permanent fix and the updates can be safely deployed.

What Is Causing the Issue?

The root cause of the issue is related to a change in the Remote Procedure Call (RPC) infrastructure, which manages communication between applications and services within Windows Server.

With the October 2026 updates, the default limit for concurrent endpoint lookup requests handled by the RPC Endpoint Mapper component was set to 512.

However, this limit may be insufficient in Exchange Server environments with heavy workloads. As a result, communication between Exchange services may be disrupted, potentially causing email delivery failures and mailbox access problems.

The impact varies depending on the server workload and overall system activity. While some Exchange environments may continue operating without any noticeable issues, others may experience significant service disruptions.

Which Windows Server Updates Are Affected?

The following Windows Server security updates have been identified as being associated with the issue:

Operating SystemAffected Update
Windows Server 2025KB5126646
Windows Server 2022KB5126655
Windows Server 2019KB5126651
Windows Server 2016KB5126868

Exchange Server environments running on systems where these updates have been installed may experience various connectivity and service-related problems.

Important: The issue is not caused by Exchange Server security updates themselves. It originates from the Windows Server operating system updates.

Therefore, Windows Server security updates and Exchange Server security updates should be evaluated and managed separately.

What Issues May Occur in Exchange Server Environments?

Affected Exchange Server environments may experience the following symptoms:

  • OWA Access Issues: Users may be unable to sign in to Outlook on the Web or access their mailboxes through a web browser.
  • Email Delivery Failures: Emails sent through Outlook may remain in the Outbox and fail to reach their recipients.
  • Mail Flow Disruptions: Messages may accumulate in Exchange transport queues, resulting in delayed or interrupted email delivery.
  • Mailbox Connectivity Errors: Users may be unable to access their mailboxes even when Exchange services appear to be running normally.
  • DAG Communication Issues: Database Availability Group (DAG) environments may experience connectivity and availability problems.

Affected servers may also generate Event ID 1006 in Windows Event Viewer, along with the following error message:

MapiExceptionMdbOffline (hr=0x80004005, ec=1142)

In some cases, restarting the server may temporarily restore normal operation. However, the same issues may reappear as the server workload increases.

Microsoft’s Recommended Temporary Workaround

Microsoft has recommended temporarily increasing the RPC Endpoint Mapper limit on affected Exchange Server systems.

To apply this workaround, administrators can run the following command from an elevated Command Prompt:

reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f

This registry modification increases the configured limit for concurrent endpoint lookup requests, helping reduce communication issues between Exchange services.

After applying the change, the server must be restarted, and Exchange services should be checked to confirm that they are operating correctly.

However, it is important to emphasize that this registry modification is a temporary workaround rather than a permanent solution.

Before making registry changes in production environments, administrators should ensure that appropriate backups are available and that the changes are performed during a planned maintenance window.

Recommended Actions for System Administrators

To minimize the risk of service disruptions, Exchange Server administrators should carefully manage the deployment of the affected Windows Server updates.

For servers that have not yet been updated:

Temporarily postpone the installation of the affected Windows Server updates until Microsoft provides a permanent resolution or the temporary workaround has been validated.

Since these updates also contain important security fixes, any postponement should be based on an organizational risk assessment and kept as short as reasonably possible.

For servers where the updates have already been installed:

Rather than immediately uninstalling the updates, administrators should evaluate Microsoft’s recommended registry-based workaround.

Affected servers should be monitored closely to ensure that Exchange services and email communication are functioning properly.

For Exchange environment monitoring:

Administrators should regularly check OWA accessibility, inbound and outbound email delivery, transport queues, Exchange services, and Windows event logs.

In environments using Database Availability Groups, database availability and replication health should also be monitored.

For future updates:

Microsoft’s official announcements should be monitored closely. Once a permanent fix becomes available, it should first be validated in a test environment before being deployed to production systems during a scheduled maintenance window.