Futureweb

Security

October's Windows Server updates, not the Exchange update, are what Microsoft ties to the outage

Microsoft says the October 13 Windows Server updates can block Outlook on the web on some Exchange servers. It says the Exchange update is not the cause.

The short version

Microsoft's release-health page says the October 13 Windows Server security updates can leave some on-premises Exchange servers unable to sign in to Outlook on the web or to deliver mail. It says installing the October Exchange security updates is not required for the failure, and it says the Windows updates should stay installed while Microsoft investigates.

The updates the health page names

Microsoft's Windows Server release-health page says that after the October 2026 security update, some on-premises Exchange servers may fail at sign-in and at sending mail. For Windows Server 2025 the originating update is KB5126646, opened on the health page on October 16, 2026, with a status of mitigated. The affected-platform line lists Windows Server 2025, 2022, 2019, and 2016, and no client release. The Exchange team's post the same week names KB5126646, KB5126655, KB5126651, and KB5126868, and it says Exchange 2016, Exchange 2019, and Subscription Edition are the servers in scope.the advisory is the story.

The symptoms, in Microsoft's words

The health page says users might be unable to sign in to Outlook on the web, that messages might remain in the Outbox, and that Exchange might fail to reach mailboxes during replication. It says some servers log event 1006 and an offline-database error when Outlook on the web cannot connect. The Exchange team adds growing queues and reports of cluster members missing quorum. A reboot, the team says, can look like a cure and then wear off. Not every server is affected. Load decides the speed.the security desk.

The Exchange update is the update Microsoft sets aside

Both pages say the trouble is not the October Exchange security update and that installing that update is not what triggers the reports. Any Exchange version on an affected Windows Server build can be in scope. Separating the two October packages is the point of the advisory. An administrator who removes the wrong package is outside the instruction Microsoft printed, which is to leave the Windows updates in place.Futureweb.

A cap, described without a procedure

The health page says the October update introduced a default limit on memory the Endpoint Mapper may use for Endpoint Lookup calls, and that 512 simultaneous calls may be too few for Exchange under load. Raising that ceiling is the mitigation Microsoft points to, on the Exchange team's post, with a further mitigation available through support. The health page says Microsoft is still investigating. This brief names the products, the update identifiers, the error, and the cap. It does not print the configuration change.a different October Windows record.

October 19 is the wire's confirmation

BleepingComputer, on October 19, reports Microsoft's confirmation that the Windows Server updates are tied to the sign-in and mail-flow failures, and it points at the same health note and the same Exchange post. The article is a second account of Microsoft's pages. Where it repeats a configuration change, this brief does not follow it onto the page. A vendor login copied from a contractor's file site is a different October incident.the assessment-file notice.

What this page will not hand an operator

It will not print a command, a registry path, a value name, or a number to type. It will not say every Exchange server will fail. It will not advise uninstalling a security update Microsoft said to keep. The primary instructions stay on Microsoft's health page and the Exchange team's post. The dependency here is which update is in scope, and which update is not. Asked directly, Does Microsoft blame the October Exchange security update? No. Both the health page and the Exchange team say these reports are not caused by the October Exchange updates, and that those Exchange updates do not have to be installed for the Windows updates to produce the symptoms.

What a fix would change

A health-page status that moves from mitigated to resolved, with a later update that removes the need for the temporary change, would close the incident. A statement that a named Exchange build is immune would narrow the scope. Until then, the record is an October 13 Windows update, an October 16 advisory, and an October 19 retelling. Asked directly, What symptoms does the release-health page list? Users may be unable to sign in to Outlook on the web, messages may sit in the Outbox, and mailbox replication may fail. In some cases the page cites an offline-database error and event 1006 in the application log. A reboot may clear the trouble only for a while.

Another October Windows brief stays a different fault

This paper already filed a separate October Windows note about an older authentication fallback. That record has its own update and its own workaround, which that page also refuses to print as a recipe. The Exchange failures here are the Endpoint Mapper cap Microsoft describes. The two October documents should not be collapsed into one patch. Asked directly, Which Windows updates does the Exchange team name? KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016. The team says Exchange 2016, Exchange 2019, and the Subscription Edition can be affected when they run on those systems.

What stays on the record

KB5126646, KB5126655, KB5126651, and KB5126868. Exchange 2016, 2019, and Subscription Edition on those server releases. Sign-in, queues, and replication as the symptoms Microsoft lists. A default of 512 simultaneous lookup calls. A direction to keep the Windows updates installed. No procedure on this page. The short answer this page will stand on is this: Microsoft's release-health page says the October 13 Windows Server security updates can leave some on-premises Exchange servers unable to sign in to Outlook on the web or to deliver mail. It says installing the October Exchange security updates is not required for the failure, and it says the Windows updates should stay installed while Microsoft investigates.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Windows Server 2025 release health
  2. Exchange team, October 16, 2026
  3. BleepingComputer

Questions

Which Windows updates does the Exchange team name?

KB5126646 for Windows Server 2025, KB5126655 for Windows Server 2022, KB5126651 for Windows Server 2019, and KB5126868 for Windows Server 2016. The team says Exchange 2016, Exchange 2019, and the Subscription Edition can be affected when they run on those systems.

What symptoms does the release-health page list?

Users may be unable to sign in to Outlook on the web, messages may sit in the Outbox, and mailbox replication may fail. In some cases the page cites an offline-database error and event 1006 in the application log. A reboot may clear the trouble only for a while.

Does Microsoft blame the October Exchange security update?

No. Both the health page and the Exchange team say these reports are not caused by the October Exchange updates, and that those Exchange updates do not have to be installed for the Windows updates to produce the symptoms.

What does Microsoft say to do with the Windows updates?

Do not uninstall them. The health page calls the issue mitigated and says a temporary mitigation is a configuration change described on the Exchange team's post, plus a further option through Microsoft support. This page does not reprint that change.

What limit does the health page describe?

A default cap of 512 simultaneous Endpoint Lookup calls in the Endpoint Mapper, which the page says may be too low for Exchange under heavy load. The team adds that severity depends on load and that some servers may never show the problem.