This non-security out-of-band (OOB) update for Windows Server 2025 (KB5134137) is cumulative. It includes updates from previous releases, along with additional non-security improvements.
Who should install this update
This out-of-band (OOB) update is intended for devices that do not receive current certificate trust list (CTL) updates, including updates to the list of untrusted certificates. Examples include devices in disconnected environments, devices that cannot access Microsoft’s certificate-update service and devices where automatic CTL updates are disabled.
Improvements
This update contains fixes and quality improvements from KB5126646 (released October 13, 2026). The following summary outlines key issues addressed by this update. The bold text within the brackets indicates the item or area of the change.
- [Certificates] This update includes an updated trusted root certificate payload in the Windows cumulative update for devices that cannot access Microsoft’s certificate-update service and devices where automatic certificate trust list (CTL) updates are disabled. To learn more, see Certificates and trust in Windows.
For more information about the Windows certificate trust changes related to eMudhra, see Microsoft’s response to compromised eMudhra certificate authority keys.
If you've already installed previous updates, your device will download and install only the new updates included in this package.
Note: Devices enrolled in hotpatch updates that install this update will not receive hotpatch updates until after they install the January 2027 baseline update.
Windows Server 2025 servicing stack update (KB5126645) - 26100.33634
This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. To learn more about SSUs, see Servicing stack updates.
Known issues in this update
SQL Server linked server connections might remain open
Symptoms
After Windows updates released October 13, 2026, and later are installed on server devices, connections created by SQL Server linked server queries might remain open after the queries complete. As additional queries are performed, connections to external databases can accumulate instead of closing as expected. This can slow or degrade server performance after prolonged run time.
This issue affects SQL Server linked server queries that use OLE DB providers to connect to external databases. Oracle and PostgreSQL connections are among those known to be affected. In affected environments, administrators might observe an increasing number of open connections to external databases, even when the associated SQL Server linked server queries are no longer running.
If idle connections can be identified, it is possible to manually close them in order to temporarily relieve server load. It is also possible to temporarily restore system stability by restarting the SQL service. However, these steps can also interrupt active queries or transactions, and the problem can resurface again after sufficient operation time.
Workaround:
A mitigation is available for affected enterprise devices. To apply this mitigation in your organization, contact Microsoft Support for business.
Next steps:
We are working on a resolution and will provide an update in an upcoming release. We will update this documentation when the resolution is available
Users might be unable to sign in to OWA or send emails on Exchange Server
Symptoms:
After installing this update, some on-premises Exchange servers might experience issues accessing or sending email. Users might be unable to sign in to Outlook on the web (OWA), or email messages sent from Outlook might remain in the Outbox and not be delivered. Additionally, Exchange might experience issues accessing mailboxes during mailbox replication.
In some affected configurations, Exchange Server OWA might fail with an error MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142) with Event ID 1006 logged in the application log. Another reported symptom is growing email queues. Installing the October 2026 Exchange server security updates isn’t required for these issues to occur.
Resolution
This issue is resolved in Windows updates released on and after November 10, 2026 such as (KB5131080). We recommend you install the latest Windows update for your device as it contains important improvements and issue resolutions, including this one.
USB Audio Class 1.0 devices with error Code 10 or no output
Symptoms
After installing the September 8, 2026, Windows security update, some USB Audio Class 1.0 devices might fail to start or produce audio. Affected devices might experience one or more of the following symptoms:
- The device displays an error in Device Manager: "This device cannot start (Code 10).”
- No audio output.
- Volume controls are unresponsive or remain at zero.
- Sound settings are unresponsive or unavailable.
- Some devices might function in standard stereo configurations but fail when using multichannel audio features, including 8-channel or 3D audio modes. Some customers have reported that they're able to restore audio in these cases by switching to 2-channel mode.
This issue is limited to USB Audio Class 1.0 devices.
Resolution
The symptoms experienced on devices using 8-channel or 3D audio modes are addressed in the out-of-band (OOB) update released on September 14, 2026, (KB5129235). The remaining symptoms are addressed in (KB5131080).
Windows Server Update Services (WSUS) does not display error details
After installing KB5070881 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287.
How to get this update
Before you install this update
- Servicing Stack Update (SSU): You must have the latest SSU installed to install this update.
Deployment
If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.
Note
The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.
To ensure the boot.stl file is included as part of the installation media, do one of the following:
- Use the Update WinPE script to update an existing Windows image. (Recommended)
- Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.
For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.
Install this update
To install this update, use one of the following Windows and Microsoft release channels.
| Available | Next Step |
|---|---|
|
This update is available from the Microsoft Update Catalog. |
File information
A list of the files that are included in this update are provided in a CSV (Comma delimited) (*.csv) file. The file can be opened in a text editor such as Notepad or in Microsoft Excel.
Note The English (United States) version of this software update might contain files for additional languages.
Download the file information for out-of-band update KB5134137.
Download the file information for SSU (KB5126645) - version 26100.33634.
Change log
| Change date | Change description |
|---|---|
| November 17, 2026 | Added new known issue "SQL Server linked server connections might remain open". |
| November 10, 2026 | Known issues resolved - "Users might be unable to sign in to OWA" and "USB Audio Class 1.0 devices with error Code 10 or no output." |
| October 27, 2026 | Added a note clarifying that hotpatch-enrolled devices that install this update will not receive hotpatch updates until after installing the January 2027 baseline update. |
| October 26, 2026 | Updated the release note to link to additional information about the Windows certificate trust changes related to eMudhra. |