{"id":892,"date":"2026-10-27T22:58:20","date_gmt":"2026-10-27T22:58:20","guid":{"rendered":"https:\/\/managedt.com\/blog\/microsoft-october-windows-server-updates-exchange-sign-in-mail-flow\/"},"modified":"2026-10-27T22:58:21","modified_gmt":"2026-10-27T22:58:21","slug":"microsoft-october-windows-server-updates-exchange-sign-in-mail-flow","status":"publish","type":"post","link":"https:\/\/managedt.com\/blog\/microsoft-october-windows-server-updates-exchange-sign-in-mail-flow\/","title":{"rendered":"Microsoft: October Windows Server updates break Exchange sign-in, mail flow"},"content":{"rendered":"
Updated October 27, 2026 at 6:57 PM ET<\/em><\/div>\n

Small businesses running on-premises Exchange can protect email access after Microsoft confirmed that the October 2026 Windows Server security update may prevent Outlook on the web sign-in, leave sent messages in the Outbox and interrupt mailbox replication. Microsoft has issued a temporary registry-based workaround while its developers prepare a permanent fix.<\/p>\n

What happened<\/h2>\n

Microsoft confirmed in its [Windows Server release health dashboard](https:\/\/learn.microsoft.com\/en-us\/windows\/release-health\/status-windows-server-2022) that the October 2026 Windows security update, KB5126655, can cause sign-in and mail delivery problems on some on-premises Exchange servers. The company said Exchange installations running on affected Windows Server versions may experience growing email queues, mailbox replication errors and an OWA connection failure. Microsoft has marked the issue as mitigated while it works on a permanent fix.<\/p>\n

Are you affected?<\/h2>\n

The Windows Server 2022 release health page lists Exchange Server 2016, Exchange Server 2019 and Exchange Subscription Edition as affected. Microsoft also stated that any Exchange version running on an impacted Windows Server version could be affected, with the severity and speed of impact varying according to server load. Some servers may never experience the problem.<\/p>\n

Check the Exchange servers for growing email queues, messages remaining in the Outlook Outbox, mailbox replication issues and failures to access mailboxes. Administrators can also check the Windows application log for Event ID 1006 and the error message "MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142)" when OWA fails.<\/p>\n

The October update introduced a default limit of 512 simultaneous Endpoint Lookup calls handled by Endpoint Mapper. Microsoft said that limit might be insufficient for Exchange Server under heavy load because it restricts the memory available to that service.<\/p>\n

What to do now<\/h2>\n
    \n
  1. Do not uninstall the October 2026 Exchange server security updates. Microsoft said the reported issues are not related to installing those Exchange updates, and the problem can also occur without them.<\/li>\n
  2. Confirm whether the affected Exchange servers have the Windows Server October 2026 security update KB5126655 installed and check for the signs listed above.<\/li>\n
  3. Apply Microsoft’s temporary workaround on each affected Exchange Server. Open an elevated Command Prompt and run this command: reg add "HKLM\\SOFTWARE\\Microsoft\\Rpc" \/v EpmapSavedContextCap \/t REG_DWORD \/d 65536 \/f<\/code><\/li>\n
  4. Reboot the Exchange Server after changing the registry setting.<\/li>\n
  5. Monitor the Exchange environment after the restart. Microsoft advises increasing the Endpoint Mapper memory limit again if the issue reappears.<\/li>\n<\/ol>\n

    What caused the problem?<\/h2>\n

    The Windows update added a default memory limit for Endpoint Mapper while it handles Endpoint Lookup calls. With a ceiling of 512 simultaneous calls, the service may lack enough capacity for Exchange Server workloads during periods of heavy demand. Raising the limit through the registry allows Endpoint Mapper to use more memory.<\/p>\n

    Microsoft has stated that the problem is not tied to the October 2026 Exchange server security updates. It affects Exchange servers based on their Windows Server versions and operational load, which is why some systems may show no symptoms at all.<\/p>\n

    Exchange 2016 and 2019 support changes<\/h2>\n

    Microsoft also announced that it will stop shipping extended security updates for Exchange 2016 and Exchange 2019 in October 2026. The change follows a six-month extension announced in April 2026 as part of the original Extended Security Update program.<\/p>\n

    FAQ<\/h2>\n

    Which Microsoft update can cause Exchange OWA sign-in and mail delivery issues?<\/h3>\n

    The October 2026 Windows security update KB5126655 can cause OWA sign-in failures, undelivered messages and mailbox replication issues on affected on-premises Exchange servers.<\/p>\n

    Which Exchange Server versions are affected?<\/h3>\n

    Microsoft’s release health page lists Exchange Server 2016, Exchange Server 2019 and Exchange Subscription Edition. Microsoft also said any Exchange version running on an impacted Windows Server version could be affected, depending on server load.<\/p>\n

    How can administrators temporarily fix the Exchange mail flow problem?<\/h3>\n

    Microsoft recommends adding the EpmapSavedContextCap registry value with a data value of 65536 from a Command Prompt with administrator privileges and then rebooting the Exchange Server. Administrators should monitor the environment afterward and raise the limit again if the issue returns.<\/p>\n