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.

• 

  What is new in Windows Server 2025

  Check its advanced features and innovations

• 

  Get Windows Server known issues in Graph API

  Data is available for supported Windows Server versions

Known issues

Issue details

January 2026

Apps might become unresponsive when saving files to cloud-backed storage

After installing Windows updates released on or after January 13, 2026 (KB5073379), some applications might become unresponsive or experience unexpected errors when opening files from or saving files to cloud-backed storage, such as OneDrive or Dropbox.

For example, in some configurations of Outlook that store PST files on OneDrive, Outlook might become unresponsive and fail to reopen unless its process is terminated in Task Manager, or the system is restarted. In addition, sent emails might not appear in the Sent Items folder, and previously downloaded emails might be downloaded again. The affected Outlook configurations primarily involve classic Outlook, which is commonly tied to enterprise licensing and is not included with most home installations of Windows. To check your Outlook configuration, see Feature comparison between new Outlook and classic Outlook.

Resolution:

This issue is resolved in the out-of-band (OOB) update KB5078135, released on January 24, 2026, and available via the Microsoft Update Catalog, as well as in updates released after this date. We recommend installing the latest update for your device, as it contains important improvements and issue resolutions, including this one.

Note: To download updates from the Microsoft Update Catalog, follow the steps described on this article.

For devices that have not yet installed the OOB update, there is an optional workaround for Outlook-specific scenarios. Moving the Outlook PST files out of OneDrive should resolve this issue. For guidance, please see documentation at How to remove an Outlook .pst data file from OneDrive. In addition, email accounts can still be accessed via webmail, if supported by your email provider.  

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019
• ​Server: Windows Server 2025; Windows Server, version 23H2; Windows Server 2022; Windows Server 2019

Connection and authentication failures in Azure Virtual Desktop and Windows 365

After installing the January 2026 Windows security update (KB5073379), credential prompt failures might occur in some remote connection applications. This includes remote desktop connections using the Windows App on Windows client devices, on Azure Virtual Desktop and Windows 365. The Windows App is affected by this issue on specific Windows builds and can experience sign-in failures.

Other remote connections and related applications may be similarly impacted.

Resolution: To address this issue, an out-of-band (OOB) update was released January 17, 2026, in the Microsoft Update Catalog. It can be found as KB5077793.

If you have not yet deployed the January 2026 Windows security update and your IT environment includes the affected applications and features, we recommend applying this OOB update instead. For additional guidance, see How to download updates from the Microsoft Update Catalog. As always, we recommend you install the latest update for your device as it contains important improvements and issue resolutions including this one. 

If the OOB is not installed, one of the following connection options can be used as a temporary workaround:

• ​Use the Remote Desktop client for Windows to connect to Azure Virtual Desktop here (/previous-versions/remote-desktop-client/whats-new-windows?tabs=windows-msrdc-msi)
• ​Connect using the Windows App Web Client at windows.cloud.microsoft

Affected platforms:

• ​Client: 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
• ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019

August 2025

Updates installed via WUSA might fail if installed from a shared folder

Windows updates installed using the Windows Update Standalone Installer (WUSA) might fail with error ERROR_BAD_PATHNAME, when the update is installed using WUSA or double-clicking a .msu file from a network share that contains multiple .msu files. These issues might occur on devices that installed updates released May 28, 2025 (KB5060842) and later.

WUSA is a method of installing updates using the Windows Update Agent API which is typically only employed in enterprise environments. It is not common in personal or home settings. 

Please note that this issue does not occur when there is only one .msu file in the network share or when the .msu files are stored locally on the device. In addition, after installing an .msu file by double-clicking or using WUSA and restarting Windows, you might notice that the Update History page in Settings continues to indicate that a restart is required to complete the update. This is temporary and should be resolved on its own.

Workaround: To work around this issue, save the .msu files locally on the device and install the update from this location. Also, if you've restarted Windows after installing an .msu file via WUSA, please wait 15 minutes or more before checking the Update History page in Settings. After this short delay, the Settings app should properly indicate if the update installed successfully.

Mitigation: This issue is addressed using Known Issue Rollback (KIR) and is resolved automatically for most home users and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.

IT admins can resolve this issue for managed devices which have installed the affected update and encountered this issue. It can be fixed by installing and configuring the Group policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. The special Group Policy can be found in Computer Configuration > Administrative Templates > [Group Policy name].

Group Policy downloads with Group Policy name:

• ​Download for Windows 11, version 24H2 and Windows Server, version 2025 - Windows 11 24H2 and Windows Server 2025 KB5062660 250806_17201 Known Issue Rollback.msi

Next steps: We are working on releasing a resolution for this issue in a future Windows update. We will provide an update when more information is available.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2
• ​Server: Windows Server 2025

November 2024

Windows Server 2022 and Server 2019 unexpectedly upgraded to Windows Server 2025

Windows Server 2025 is intended to be offered as an Optional upgrade in Windows Update settings for devices running Windows Server 2019 and Windows Server 2022. Two scenarios were observed in certain environments:

• ​Some devices upgraded automatically to Windows Server 2025 (KB5044284). This was observed in environments that use third-party products to manage the update of clients and servers. Please verify whether third-party update software in your environment is configured not to deploy feature updates. This scenario has been mitigated.

• ​An upgrade to Windows Server 2025 was offered via a message in a banner displayed on the device’s Windows Update page, under Settings. This message is intended for organizations that want to execute an in-place upgrade. This scenario has already been resolved.

The Windows Server 2025 feature update was released as an Optional update under the Upgrade Classification: “DeploymentAction=OptionalInstallation”. Feature update metadata must be interpreted as Optional and not Recommended by patch management tools.

We advise organizations to use Microsoft-recommended methods to deploy Windows Server feature updates.

Next steps: Microsoft is working with third-party providers to streamline best practices and recommended procedures. As an interim measure, Microsoft has also temporarily paused the upgrade offer via the Windows Update settings panel. We estimate it will be available in the first half of 2025. All other upgrading methods to install Windows Server 2025 are still available through the usual channels.

Once the offer via Windows Update resumes, IT administrators will be able to control the feature update offer banner by setting the target version to “hold” in the Group Policy “Select the target Feature Update version.” To learn how to manage feature updates via this group policy, see Manage Feature Updates with Group Policy on Windows Server.

Note: The Windows Server 2025 feature update was made available on November 1, 2024, as KB5044284, which was the same KB number used for Windows 11, version 24H2. This is the KB numbering for both client and server Windows updates. Future updates released for Windows Server 2025 and Windows 11, version 24H2 will share the same KB numbers, but will have different release note sites and links. 

Affected platforms:

• ​Client: None
• ​Server: Windows Server 2025; Windows Server 2022; Windows Server 2019 

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.