Microsoft recently released the August monthly update KB5063878 for Windows 11 version 24H2. You can read more about the Windows 11 update KB5063878 by clicking here. They have now acknowledged and confirmed three issues after the installation of August update on devices.

The update KB5063878 fails to install with error code 0x80240069:

Microsoft has mentioned on its official Windows 11 page that Windows 11, version 24H2 (KB5063878), might fail to install with error code 0x80240069 when installed via Windows Server Update Services (WSUS). It has however claimed that  the problem with the Windows Update service has been resolved.

The August 12, 2025 Windows security update for Windows 11, version 24H2 (KB5063878), might fail to install with error code 0x80240069 when installed via Windows Server Update Services (WSUS). WSUS allows Servers with the WSUS role to defer, selectively approve, and schedule updates for specific devices or groups across an organization.

Home users are unlikely to experience this issue, as WSUS is designed for use across business and enterprise environments.

Resolution:

The problem with the Windows Update service has been resolved. If you experienced this issue, please refresh and re-sync with Windows Server Update Services to install the latest 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, it could be found in 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.

Windows 11 update fails to install with error ERROR_BAD_PATHNAME:

Microsoft has mentioned on its official Windows 11 page that Windows 11, version 24H2 (KB5063878), might fail to install 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. This issue is addressed using Known Issue Rollback (KIR) as per Microsoft and is resolved automatically for most home users and non-managed business devices.

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 (KB5058499) 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:

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.

Error events are logged for CertificateServicesClient:

Microsoft has mentioned on its official Windows 11 page that post installation of the updates including the August 2025 Windows security update, Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored.

Following installation of the July 2025 Windows non-security preview update (KB5062660) and later updates including the August 2025 Windows security update, Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored.

The issue only manifests as an entry in the Windows Event Viewer, with Error ID 57. The event shows the message “The “Microsoft Pluton Cryptographic Provider” provider was not loaded because initialization failed”.

Please note that although this event is logged in Event Viewer every time the device is restarted, it does not reflect an issue with any active Windows component. This event is related to a feature that is currently under active development. There is no impact to Windows processes associated to this event and no action is required to prevent or resolve this error.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

RELATED ARTICLESMORE FROM AUTHOR