Windows Server 2025 known issues and notifications

Find information on known issues and the servicing status for Windows Server 2025. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.

Current status as of November 6, 2024
 
Windows Server 2025 is now generally available. It delivers security advancements and new hybrid cloud capabilities in a high performing, AI-capable platform. Windows Server 2025 is Microsoft’s latest Long-Term Servicing Channel (LTSC) release for Windows Server. To download a free 180-day evaluation, visit the Microsoft Evaluation Center. 
 
Windows Server 2025 is offered as an Optional update for Windows Server 2022 and Window Server 2019 devices, if organizations want to do an in-place upgrade. We recommend you use these methods to deploy Windows Server feature updates as Windows Server 2025 is not automatically installed.
 
To learn more about Windows Server’s Lifecycle Policy, see the Windows Server 2025 lifecycle article.
See all messages >

Known issues

See open issues, content updated in the last 30 days, and information on safeguard holds. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge).

SummaryOriginating updateStatusLast updated
SQL Server linked server connections might remain open
Connections to external databases such as Oracle and PostgreSQL can accumulate over time
OS Build 26100.33650
KB5126646
2026-10-13
Confirmed
2026-11-11
15:37 PT
Users might be unable to sign in to OWA or send emails on Exchange Server
Issue reported on Exchange Server 2016, 2019, and Subscription Edition, affecting OWA sign-in and mail delivery.
OS Build 26100.33650
KB5126646
2026-10-13
Resolved
KB5131080
2026-11-10
10:27 PT
USB audio devices might fail to start or produce no sound
Some USB Audio Class 1.0 devices display Code 10 or fail in multichannel audio modes after installing the Sept. 8 update
OS Build 26100.33438
KB5122871
2026-09-08
Resolved
KB5131080
2026-11-10
10:27 PT

Issue details

November 2026

SQL Server linked server connections might remain open

StatusOriginating updateHistory
ConfirmedOS Build 26100.33650
KB5126646
2026-10-13
Last updated: 2026-11-11, 15:37 PT
Opened: 2026-11-11, 15:11 PT

After Windows updates released October 13, 2026 (KB5126646), 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 will address this issue with an out-of-band update that will be released in the next few days. We will update this documentation once the update is released.

Affected platforms:

  • ​Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • ​Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Back to top

Users might be unable to sign in to OWA or send emails on Exchange Server

StatusOriginating updateHistory
Resolved KB5131080OS Build 26100.33650
KB5126646
2026-10-13
Resolved: 2026-11-10, 10:00 PT
Opened: 2026-11-09, 19:07 PT

After installing the October 2026 Windows security update (KB5126646), 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 was resolved by Windows updates released November 10, 2026 (KB5131080), and updates released after that date. We recommend you install the latest update for your device as it contains important improvements and issue resolutions, including this one. 

If you install an update released November 10, 2026 (KB5131080) or later, you do not need to use a workaround for this issue. If you are using an update released before November 10, and have this issue, you have the option to apply the following workaround. 

Workaround: This issue can be temporarily mitigated by modifying the registry key as described in Exchange servers may become unstable after installation of October 2026 Windows updates.

The October 2026 update introduced a default limit on the amount of memory used by Endpoint Mapper when handling Endpoint Lookup calls. For workloads such as Exchange Server, the default limit of 512 simultaneous Endpoint Lookup calls might not be sufficient under heavy load. Administrators can use this registry setting to increase the maximum number of simultaneous Endpoint Lookup calls, which increases the amount of memory that Endpoint Mapper can use.

Affected platforms:

  • ​Client: None
  • ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016
Back to top

USB audio devices might fail to start or produce no sound

StatusOriginating updateHistory
Resolved KB5131080OS Build 26100.33438
KB5122871
2026-09-08
Resolved: 2026-11-10, 10:00 PT
Opened: 2026-11-09, 16:04 PT

After installing the September 8, 2026, Windows security update (KB5122871), 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. (*Note: This behavior is resolved in the out-of-band update released on September 14, 2026. See Resolution section below.)

This issue is limited to USB Audio Class 1.0 devices.

Resolution: The symptoms experienced on devices using 8-channel or 3D audio modes (last bullet point in the list of symptoms documented in this entry) are resolved in the out-of-band (OOB) update released on September 14, 2026, and updates released after this date. The remaining symptoms are resolved in the Windows security update released on November 10, 2026 (KB5131080) and later updates. We recommend you install the latest security update for your device as it contains important improvements and issue resolutions, including this one. 

If you are an IT administrator that contacted Microsoft Support for Business to obtain an immediate workaround, you do not need to use the Known Issue Rollback (KIR) or special group policy to resolve this issue.

Affected platforms:

  • ​Client: Windows 11, version 26H2; Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016
  • ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Back to top

Report a problem with Windows updates

To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app.

Need help with Windows updates?

Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.

For direct help with your home PC, use the Get Help app in Windows or contact Microsoft Support. Organizations can request immediate support through Support for business.

View this site in your language

This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.