- Microsoft says the October 2026 Windows update (KB5126646) can disrupt OWA sign-in and mail delivery on some on-premises Exchange servers under heavy load.
- A new default cap of 512 simultaneous lookups is the stated cause. Microsoft has a registry workaround and is still investigating a fix.
- Check which Exchange servers got the update, watch mail queues, and decide who owns the registry change and the reboot.
A new default limit that busy mail servers can hit
In October, a Windows security update added a default limit that began disrupting some Exchange customers. This shows, in WebPulse's view, that a patch can behave as intended and still hurt a workload it was not built around.
Microsoft's Windows release health page lists the problem as a known issue. It is tied to KB5126646, the October 2026 Windows security update. On some on-premises Exchange servers, mail stops moving normally.
What users and administrators see
Microsoft names several symptoms. Some users cannot log in to the web version of Outlook, known as OWA. Messages sent from the Outlook app can sit in the Outbox and never go out. Exchange can also struggle to reach mailboxes while it copies them between servers.
Microsoft adds that some setups show a specific OWA error: "MapiExceptionMdbOffline: Unable to make connection to the server." Event ID 1006 appears in the application log. Email queues may also grow.
These are everyday problems for real people. An employee watches a message that will not send. An administrator sees queues swell on a mail system that looks healthy but is not delivering.
How a new default limit causes it
Microsoft says the October update added a default cap on memory use by Endpoint Mapper. This Windows component helps programs on a server find the services they need. The cap allows 512 lookups at the same time.
Microsoft says that number "might not be sufficient under heavy load" for workloads like Exchange. The page does not explain why the cap was added.
That helps explain why the damage is uneven. A separate Microsoft blog, quoted by BleepingComputer, says "the severity and speed of impact varies based on Exchange server load." Microsoft also says some servers may see no problem at all.
This is not an Exchange patch problem
Microsoft states that the October 2026 Exchange security updates are not needed for the issue to appear. BleepingComputer reports that Microsoft urges customers not to remove those Exchange updates.
The Microsoft blog, as quoted by BleepingComputer, says any Exchange version on affected Windows versions could be hit. BleepingComputer describes those as Windows Server 2019 and later. Teams that patch Windows and Exchange on separate schedules should check both.
The workaround and its limits
Microsoft's stopgap is a registry change. It raises the number of lookups that can run at once, so Endpoint Mapper can use more memory. BleepingComputer reports that an administrator runs the command in an elevated Command Prompt and then reboots the server.
BleepingComputer adds that customers should watch the environment after the restart. If the problem returns, they should raise the limit again. Microsoft also offers another mitigation through Microsoft Support. It says it is investigating and will share more later.
This fix is manual, so someone must own it. It also needs a reboot of a mail server, and that is a scheduling decision.
Why load-dependent failures are hard to catch
This section is WebPulse's interpretation, not a Microsoft finding. A limit that bites only at high load can pass a quiet test server. It shows up in production at the busiest moments. A pilot group on a lightly used machine can look fine while the main mail server struggles.
The same Microsoft page lists a September issue. After the September 2026 update (KB5122871), some Remote Desktop Services environments became unstable. Microsoft fixed that with an out-of-band update (KB5129235) on September 14. Two months do not make a trend. They do show that a monthly update is not a risk-free step.
Exchange owners also face a second deadline. BleepingComputer reports that Microsoft's July announcement made this month the end of paid extended security updates for Exchange 2016 and 2019. That followed a six-month extension announced in April 2026.
Questions to put to your team
Ask which Exchange servers run on Windows versions that received KB5126646. Ask which of them are already patched. Ask who watches mail queue length and OWA sign-in errors, and who gets paged.
Ask who owns the registry change if it is needed, and how the reboot will be scheduled. Ask whether patch testing ever uses a server under production-like load. Finally, ask what the plan is for Exchange 2016 and 2019 now that extended updates end.
A patch trades one risk for another: the flaw it closes against the outage it may cause. Good teams measure both.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Microsoft.
