Microsoft has asked customers this week to disregard incorrect CertificateServicesClient (CertEnroll) errors that appear after installing the July 2025 preview update and subsequent Windows 11 24H2 updates.

In recent months, Microsoft has addressed multiple similar issues affecting various Windows features that triggered erroneous warnings with no actual impact.

For instance, last month, Redmond advised users to turn a blind eye to Windows Firewall configuration errors that occurred after rebooting their computers following the installation of the June 2025 preview update.

In April, the company confirmed and fixed a known issue that caused invalid 0x80070643 failure errors after installing the April 2025 Windows Recovery Environment (WinRE) updates.

The same month, it also fixed a bug that was triggering incorrect BitLocker drive encryption errors on Windows 10 and Windows 11 devices due to a reporting issue.

When it acknowledged the issue in October, Microsoft stated that it only impacted managed Windows environments where drive encryption was enforced for the operating system and fixed drives.

More errors added to the ignore list

On Monday, the company updated the Windows release health dashboard once again to ask users to ignore another error event caused by recent updates, logged in Event Viewer with Error ID 57 and a message warning that “The ‘Microsoft Pluton Cryptographic Provider’ provider was not loaded because initialization failed.”

“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 company said.

“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.”

Microsoft stated that this known issue is caused by a feature that’s still under development and hasn’t yet been fully integrated into the operating system.

Just as it did when confirming other similar errors over the last few months, the company once again added that these errors have no impact on Windows processes and that users don’t need to take any action to prevent or resolve this issue.