A heads-up not directly related to the October Exchange SUs, but important if you run Exchange on-premises: Reports indicate that last Tuesday’s Windows Server patches could break Exchange functionality.
The Windows Server updates that might cause issues are:
- KB5126646 (Windows Server 2025)
- KB5126655 (Windows Server 2022)
- KB5126651 (Windows Server 2019)
- KB5126868 (Windows Server 2016)
Reported issues include Outlook Web Access (OWA) failures, mail flow disruptions, and growing mail queues. Also, the following event might be logged in the Application event log:
Source: MSExchange Replication Service
Event ID: 1006
Description: The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: <Mailbox DB>
Error: MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142).
- .
After installing the Windows Server update, the Exchange Back End website (the one listening on 0.0.0.0:444) appears to lose its binding to the WMSVC-SHA2-<Server Name> certificate. This self-signed WMSVC certificate is used by the Web Management service to enable remote management of the web server and its associated web sites and applications, e.g., Exchange Server.
You could rebind this certificate to WMSvc (port 8172) using the following procedure, provided you have the Web Administration PowerShell module installed:
Import-Module WebAdministration$cert= Get-ChildItem Cert:\LocalMachine\My | Where { $_.Subject -eq ('CN=WMSvc-SHA2-{0}') -f $ENV:COMPUTERNAME}Remove-Item -Path IIS:\SslBindings\0.0.0.0!8172New-Item -Path IIS:\SslBindings\0.0.0.0!8172 -Value $cert -ForceRestart-Service WMSvc
Microsoft is investigating the issue.

