August 12, 2025—KB5063878 (OS Build 26100.4946)

Symptoms

After installing the July 2025 Windows non-security preview update (KB5062600) or a later update, including the August 2025 Windows security update, you might see the following error in Event Viewer related to CertificateServicesClient (CertEnroll):

The "Microsoft Pluton Cryptographic Provider" provider was not loaded because initialization failed.

This event appears with Error ID 57 and is logged every time the device restarts. It does not indicate a problem with any active Windows component. The event is related to a feature that is currently in development.

There is no impact to Windows functionality, and no action is required.

Workaround

This issue is addressed in KB5064081.

Symptoms

The August 2025 security update (KB5063878) might fail to install with error code 0x80240069 when deployed through Windows Server Update Services (WSUS). WSUS enables servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.

This issue is unlikely to affect home users, as WSUS is intended for use in business and enterprise environments.

Workaround

The issue affecting the Windows Update service for devices managed through Windows Server Update Services (WSUS) has been resolved. If you experienced this problem, refresh, and re-sync with WSUS to install this update.

A Group Policy had previously been released using Known Issue Rollback (KIR) to work around this issue. If you installed the special Group Policy, you could find it in Group Policy Management Editor under: Computer Configuration > Administrative Templates > Windows 11 24H2 and Windows Server 2025 KB5063878 250814_00551 Known Issue Rollback

Organizations no longer need to install and configure this Group Policy to address this issue.

Symptoms

After installing the August 2025 Windows security update (KB5063878), you might experience delays or uneven audio and video performance when using Network Device Interface (NDI) to stream or transfer feeds between PCs.

This issue affects streaming apps such as OBS Studio (Open Broadcaster Software) and NDI Tools, especially when Display Capture is enabled on the source PC. The problem can even occur under low-bandwidth conditions.

Workaround

To work around the issue, NDI recommends manually changing the NDI Receive Mode to use TCP or UDP instead of RUDP. For steps to do this, see the NDI support site: Traffic Drops After Windows Update.

The issue is under investigation, and additional information will be shared as soon as it becomes available.

Symptoms

A security improvement was included in the August 2025 Windows security update 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.

After installing the update, standard users might see a User Account Control (UAC) prompt in several scenarios. 

• Running MSI repair commands (such as msiexec /fu).

• Opening Autodesk apps, 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 apps that configure per user.

• Running Windows Installer during Active Setup.

• Deploying packages through 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.

Workaround

The following workarounds are available:

• ​​​​​​​Run the app as an administrator (right-click the app from Start or Search, then select Run as administrator).

• If standard users can’t run apps as administrators, IT admins can apply a special Group Policy using Known Issue Rollback (KIR) to fix the issue on Windows Server 2025, Windows Server 2022, Windows 11 (versions 22H2, 23H2, 24H2), and Windows 10 (versions 21H2, 22H2). To apply this fix, contact Microsoft Support for business. Avoid using other workarounds like disabling related features.

We are working to address this issue by allowing IT admins to permit specific apps to perform MSI repair operations without UAC prompts. This improvement will be released in a future Windows update, and details will be provided as they become available.