Known update issues

Exchange Server: unstable after October 2026 Windows Server updates (ec=1142)

WorkaroundKnown issueFix scriptUpdated 1 Nov 2026

Summary

Since the October 13, 2026 updates, Exchange servers running on affected Windows Server versions may become unstable after some time. Microsoft states this is not an Exchange update issue. A registry workaround (EpmapSavedContextCap) is available; no follow-up fix is imminent.

Symptoms

OWA may fail with MapiExceptionMdbOffline: Unable to make connection to the server (hr=0x80004005, ec=1142), event ID 1006 in the Application log.
Mail queues grow during the day and mail delivery nearly stops.
DAG (database availability group) members may be unable to reach quorum.
A server reboot may resolve the issues temporarily.

Affected

Exchange Server 2016, 2019 and Subscription Edition (SE) on affected Windows Server versions
KB5126646 (Windows Server 2025)
KB5126655 (Windows Server 2022)
KB5126651 (Windows Server 2019)
KB5126868 (Windows Server 2016)
Impact and speed vary with Exchange server load; some servers may never be affected.

Workaround

Do not uninstall the October 2026 Windows Server updates.
In an elevated Command Prompt on the Exchange server, run: reg add "HKLM\SOFTWARE\Microsoft\Rpc" /v EpmapSavedContextCap /t REG_DWORD /d 65536 /f
Reboot the server.
Monitor the environment. If the issue recurs, raise the limit (Microsoft has not seen cases where this was needed).
The value can also be created before installing the updates; it is only read once the updates are installed.

Fix

Not fixed yet. Microsoft says there is no imminent follow-up release from Windows or Exchange; both teams are still analysing the issue.

Recommendation

Install the October 2026 Windows Server updates, as they carry a significant security payload, and set the EpmapSavedContextCap value on all Exchange servers. Do not wait for a new release. Monitor queues, OWA and DAG health after the reboot.

Fix script (PowerShell)

Exchange Server: unstable after October 2026 Windows Server updates (ec=1142)

What it does: Prevents Exchange servers from becoming unstable (OWA MapiExceptionMdbOffline ec=1142, growing mail queues, DAG quorum problems) after the October 2026 Windows Server updates. It sets the RPC limit value recommended by Microsoft.
How it does it: Sets HKLM\SOFTWARE\Microsoft\Rpc\EpmapSavedContextCap to DWORD 65536. The script backs up the current value first, runs as a dry run by default, and -Undo restores the previous state. A reboot is required.

What exactly happens?

First checks whether the device is affected – the vendor states no checkable condition, so "UNCLEAR" and the normal confirmation.
Before any change it backs up the previous state to %ProgramData%\ITSB\Fixes (the backup is verified; no backup, no change).
Sets the registry value HKLM\SOFTWARE\Microsoft\Rpc\EpmapSavedContextCap to 65536 (DWord).
Afterwards it verifies every change; on an error it restores the previous state automatically.

How to use the script – step by step

Download: on the entry page, read the terms and conditions (section "Free scripts") and the disclaimer, tick "I accept" and click "Download script". The file is saved in your "Downloads" folder.
Open PowerShell as administrator: press the Start key, type "PowerShell", right-click "Windows PowerShell", choose "Run as administrator" and confirm the prompt with "Yes".
Change to the Downloads folder (type or paste the command, then press Enter):
```
cd "$env:USERPROFILE\Downloads"
```
Compare the checksum: the command shows a long string. It must be exactly the same as "SHA-256" on the entry page (0BC188342581C24292916EE5FEC017AE0AD2B7F900A57E66F7200A95FEE1621A). If it differs, delete the file and do not run it.
```
(Get-FileHash .\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1 -Algorithm SHA256).Hash
```
Unblock the file (Windows marks downloaded files). Alternatively in Explorer: right-click the file › Properties › tick "Unblock" at the bottom › OK.
```
Unblock-File .\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1
```
Allow scripts for this PowerShell window only. This only applies until you close the window – the computer's setting stays unchanged. If PowerShell asks, confirm with "Y".
```
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
```
Run the script. It first checks whether this device is affected and then shows exactly what it would change – nothing is changed yet.
```
.\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1
```
Answer the questions: type "Y" (yes) or "N" (no), then press Enter. "Apply changes now?" – Y changes (everything is backed up first), N cancels without changes. "Continue anyway?" only appears if the device does not seem affected or the solution is already installed – then usually N.
Afterwards, restart the device.
To undo: repeat steps 2, 3, 6 and 7. The script asks "Restore previous configuration?" – "Y" restores exactly the state before the first change.
Download without a browser (RMM, software distribution): the address needs "&agb=1". This means the person deploying the script accepts the terms and conditions (section "Free scripts") and the disclaimer on behalf of their organisation.
```
Invoke-WebRequest "https://www.it-sb.ch/ki-api/?a=dl&f=ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1&agb=1" -OutFile ".\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1"
```

For many devices without prompts (RMM, scheduled task, Intune as a Win32 app with this command line; Intune platform scripts pass no parameters and therefore only check): check only, apply, restore. Exit codes: 0 = done or nothing to do, 1 = error, 2 = no backup to restore, 3 = cancelled, 4 = not affected. Run it as SYSTEM or administrator in 64-bit PowerShell.

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1 -Check

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1 -Apply

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1 -Undo

File: ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1 · requires administrator rights
Version: 3 · Date 1 Nov 2026 · 49 KB
SHA-256: 0BC188342581C24292916EE5FEC017AE0AD2B7F900A57E66F7200A95FEE1621A
Downloads: 0
Source of the workaround: techcommunity.microsoft.com

Use at your own risk – no warranty, no liability if anything does not work or is wrong. Test before use and make a backup. Our terms and conditions (free scripts) apply. Generated automatically from the vendor’s statement and checked (rules, second AI review).

Download without a browser (RMM, software distribution): address with "&agb=1" – this means the person deploying the script accepts the terms on behalf of their organisation: https://www.it-sb.ch/ki-api/?a=dl&f=ITSB-Fix-exchange-servers-unstable-after-october-2026-windows-server--v3.ps1&agb=1

Reports from the community and trade media

Reports from forums, Q&A sites, Reddit and trade media – linked only, without the names of the authors; the vendor’s statement is authoritative.

Exchange servers may become unstable after installation of October 2026 Windows updates Vendor · techcommunity.microsoft.com, 20 Oct 2026
Windows Server 2025 release health status Vendor · learn.microsoft.com, 16 Oct 2026
Windows Server updates cause Exchange servers to become unstable News · techzine.eu, 19 Oct 2026
Windows Server Exchange email workaround News · techrepublic.com, 20 Oct 2026
Exchange's last ESU patch is out and a Windows update is knocking servers over News · dev.to, 27 Oct 2026

Sources

Exchange Team Blog: Exchange servers may become unstable after installation of October 2026 Windows updates Vendor · techcommunity.microsoft.com

Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 15:37.

Where the information comes from

We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:

Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online

Summary and translation with AI (Claude by Anthropic) – without any data of visitors.

Affected? We can help.

We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.

Get in touch RSS feed