[German]With the preview update KB5062660 for Windows 11 24H2 released at the end of July 2025, another issues has crept in, as Microsoft confirmed on August 12, 2025. Once the update is installed, event management is flooded with CertificateServicesClient entries (ID 57). Here are a few information, what's up.
Advertising
Preview update generates CertificateServicesClient events
With the preview update KB5062660 from July 22, 2025, Microsoft has not only introduced AI features such as Recall (see Windows 10/11: Preview Updates July 22, 2025)). On August 12, 2025, Microsoft published the support article Error events are logged for CertificateServicesClient in the Known Issues section of the Windows 11 24H2 Release Health Dashboard.
The article states that after installing the Windows Preview Update from July 22, 2025 (KB5062660) and later updates, including the August 2025 security update, the Windows 11 24H2 Event Viewer may display an error related to CertificateServicesClient (CertEnroll). While this is somewhat inconvenient, Microsoft's reassuring message is that although the entry is there, it can be ignored.
The issue only appears as an entry in the Windows event log with error ID 57. The event contains the message:
The provider "Microsoft Pluton Cryptographic Provider" was not loaded because initialization failed.
Although this event is logged in the event log every time the device is restarted, it does not represent a problem with an active Windows component. This event is related to a feature that is currently under active development. The error message has no impact on Windows processes, and no action is required to prevent or fix this error, according to Microsoft. Work is currently underway to fix this error with one of the next updates.
The old case with the firewall
The above wording about the "unfinished feature" sounded familiar, so I looked into it. In the blog post Windows 11 24H2: June 2025 Preview Update KB5060829 triggers Firewall Events , I reported that after installing the preview update in question, administrators suddenly found entries triggered by Windows Firewall for Advanced Security in the Windows Event Viewer. Microsoft's advice at the time was that these event entries with warnings could be ignored. According to Microsoft, the entries originate from a built-in feature that has not yet been fully implemented.
Advertising
Advertising
