Microsoft Acknowledges CertificateServicesClient Error in Windows 11 24H2

In a surprising turn of events following the misleading Windows Firewall notification in June 2025, the Event Viewer has raised concerns once again. The latest issue involves error codes linked to the CertificateServicesClient for the Windows 11 24H2 build. Initial reports by Windows Latest indicate that Microsoft has acknowledged this technical glitch.

Microsoft’s support documentation reveals that after the installation of the July 2025 non-security preview update and subsequent updates, including the August 2025 security update, users may encounter an error associated with the CertificateServicesClient (CertEnroll).As detailed in their report, the company noted:

“Following installation of the July 2025 Windows non-security preview update and later updates including the August 2025 Windows security update, Event Viewer may display an error related to CertificateServicesClient (CertEnroll).”

While this issue does not disrupt any active applications, users may notice an entry in the Event Viewer logs showcasing the Error ID 57. Upon reviewing the log, the message reads: “The ‘Microsoft Pluton Cryptographic Provider’ provider was not loaded because initialization failed.”

The CertificateServicesClient function is essential for managing digital certificates in Windows, while the CertEnroll component plays a key role in renewing these certificates. Should the utility indeed face a malfunction, it could lead to complications while accessing networks, websites, or online services.

The occurrence of the “CertificateServicesClient” error in the Event Viewer is largely perceived as a false positive, notably affecting those who installed July 2025’s optional update. Microsoft officially recognized this bug on August 11, yet due to Patch Tuesday following closely on August 12, there simply wasn’t sufficient time to rectify the problem. Consequently, this matter has rolled over into the mandatory security update, thereby impacting a broader range of devices beyond those who opted into the previous update.

Additionally, part of the rationale for Microsoft’s decision to delay addressing this issue could stem from its perceived harmlessness, allowing them to prioritize other pressing matters.

Similar to the Firewall miscommunication that arose with the June update, this latest error can be attributed to an unannounced feature within the OS, and it does not compromise the functionality of any existing features. While this explanation might be reassuring, it seems users may need to develop a tolerance for these seemingly innocuous alerts.

Other Challenges Impacting Windows 11 24H2

In addition to the CertificateServicesClient error, users have reported another issue affecting the VR gaming experience on Windows 11 24H2. After multiple update reinstalls, some have encountered persistent BSOD (Blue Screen of Death) events. Numerous anti-cheat engines are malfunctioning as a result of this error, which is understandably frustrating for competitive gamers, as evidenced by discussions within the community on platforms like Reddit.

Personally, I also experienced a sudden BSOD linked to the Windows 11 KB5062660 (July optional), though it did not become a recurrent issue for me. Generally, if recent updates are negatively affecting your PC and causing frequent BSODs, it’s advisable to temporarily pause these updates for a week or two, waiting for a more stable patch before installation.

Moreover, before these recent false positives came to light, users reported issues with the SgrmBroker service, which failed to start, resulting in unnecessary entries being logged in Event Viewer. Microsoft has since clarified that this feature was slated for deprecation and does not interfere with any other system functionalities.

Lastly, it’s important to highlight that the August 2025 Update for Windows 11 is also not without its challenges, including various installation errors that users have begun to encounter.

Source & Images