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

October 2025

IIS websites might fail to load

After further investigation, we concluded that this issue was not applicable to Windows Server 2025. It affects only Windows 11, version 25H2 and 24H2.

This issue can be disregarded by Windows Server users.

To learn about the impact of this issue for Windows 11, select from the links below:

• ​Windows 11, version 25H2
• ​Windows 11, version 24H2

The issue mentioned below was published prior to this finding and November 14, 2025 edits:

Following installation of Windows updates releases on or after September 29, server-side applications that rely on HTTP.sys may experience issues with incoming connections. As a result, IIS websites might fail to load, displaying a message such as "Connection reset - error (ERR_CONNECTION_RESET)", or similar error. This includes websites hosted on http://localhost/, and other IIS connections.

Affected platforms:

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

Directory synchronization fails for AD groups exceeding 10,000 members

Applications that use the Active Directory directory synchronization (DirSync) control for on-premises Active Directory Domain Services (AD DS), such as when using Microsoft Entra Connect Sync, can result in incomplete synchronization of large AD groups exceeding 10,000 members. This issue occurs only on Windows Server 2025 after installing the September 2025 Windows security update (KB5065426), or later updates.

Resolution: This issue was resolved by Windows updates released November 11, 2025, KB5068861, 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 have installed updates released on or after November 11, 2025, (KB5068861), you do not need to use a Known Issue Rollback (KIR) or a special Group Policy to resolve this issue.

If you are using an update released before November 11, 2025, and have this issue, your IT administrator can resolve it by installing and configuring the special Group Policy listed below.

Group Policy downloads with Group Policy name:  

• ​Download for Windows 11, Versions 24H2 and 25H2 and Windows Server 2025 -- Windows 11 24H2, Windows 11 25H2 and Windows Server 2025 KB5066835 251016_21401 Known Issue Rollback

The special Group Policy can be found in Computer Configuration -> Administrative Templates -> Windows 11 24H2, Windows 11 25H2 and Windows Server 2025 KB5066835 251016_21401 Known Issue Rollback. After installing the group policy, configure the KB5066835 251016_21401 Known Issue Rollback value to Disabled and restart Windows Server 2025 to apply the group policy setting. (Windows 11 is out of scope of this notification and guidance.) For information on deploying and configuring this special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.  

Alternatively, affected customers can apply the following registry key as a workaround to disable the feature change.

Warning: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. For more information, see Windows registry for advanced users.

Path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides

Name: 2362988687

Type: REG_DWORD

Value: 0

Affected platforms:

• ​Client: None
• ​Server: Windows Server 2025

September 2025

Non-admins might receive unexpected UAC prompts when doing MSI repair operations

(Updated 11/26/25: Additional improvements were added to the Resolution section.)

A security improvement was included in the August 2025 Windows security update (KB5063878) and later updates to enforce the requirement that User Account Control (UAC) prompt for administrator credentials when performing Windows Installer (MSI) repair and related operations. This improvement addressed security vulnerability CVE-2025-50173.

As a result, after installing the August 2025 Windows security update and later updates, UAC prompts for administrator rights can appear for standard users in the following scenarios:

• ​Running MSI repair commands (such as msiexec /fu).
• ​Launching Autodesk applications, including some versions of AutoCAD, Civil 3D and Inventor CAM, or when installing an MSI file after a user signs into the app for the first time.
• ​Installing applications that configure themselves per user.
• ​Running Windows Installer during Active Setup.
• ​Deploying packages via Manager Configuration Manager (ConfigMgr) that rely on user-specific "advertising" configurations.
• ​Enabling Secure Desktop.

If a standard user runs an app that initiates an MSI repair operation without displaying UI, it will fail with an error message. For example, installing and running Office Professional Plus 2010 as a standard user will fail with Error 1730 during the configuration process.

Resolution:

After installing the September 2025 Windows security update (KB5065426) or later updates, UAC prompts will only be required during MSI repair operations if the target MSI file contains an elevated custom action. This requirement is further refined after installing Windows updates released on and after November 11, 2025, so that UAC prompts will only be required if the elevated custom actions are executed during the repair flow.

Installing the latest Windows updates will resolve this issue for apps that do not execute such elevated custom actions, such as Autodesk AutoCAD.

Since UAC prompts will still be required for apps that perform custom actions, after installing the September 2025 update, IT admins will have access to a workaround to disable UAC prompts for specific apps by adding MSI files to an allowlist. For details, see the KB article: Unexpected UAC prompts when running MSI repair operations after installing the August 2025 Windows security update.

A Group Policy had previously been made available from Microsoft’s Support for business using Known Issue Rollback (KIR) to work around this issue. Organizations no longer need to install and configure this Group Policy to address this issue.

Affected platforms:

• ​Client: Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 11, version 22H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB

• ​Server: Windows Server 2025; Windows Server 2022; Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2; Windows Server 2008 SP2

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.