Windows Server 2025 update history

Symptoms

We are aware of an issue affecting IT admins, where mounting an Active Directory (AD) or AD LDS database (DIT) with ntdsutil.exe can cause unintended format changes.

When an IT admin copies an 8 KB page-size DIT to a machine running Windows Server 2025, or upgrades to Windows Server 2025 “in-place” and mounts it using ntdsutil.exe, a bug in the tool modifies and upgrades the format versions in the DIT database header.  This modification does not happen to 32 KB page-sized DIT files. The upgraded format versions prevent AD or LDS from loading the database, leaving the directory service unable to start.

Workaround

This issue is addressed in KB5072033.

Symptoms

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

WUSA installs updates using the Windows Update Agent API, a method typically used in enterprise environments. It’s not commonly used in personal or home settings.

This issue does not occur when:

• Only one .msu file is present in the network share.

• The .msu file is stored locally on the device.

After installing an update using WUSA or by double-clicking the .msu file, and restarting Windows, you might still see a message on the Update History page in Settings indicating that a restart is required to complete the update. This is a temporary display issue and should resolve automatically.

Workaround

To work around this issue, save the .msu files locally on the device and install the update from that location.

If you’ve restarted Windows after installing an .msu file using WUSA, wait at least 15 minutes before checking the Update History page in Settings. After this short delay, the Settings app should correctly 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 administrators can resolve this issue on managed devices that have installed the affected update by deploying a special Group Policy. For information on deploying and configuring the special Group Policy, 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: The issue is under investigation, and additional information will be shared as soon as it becomes available.