Microsoft has recently advised its users to disregard certain CertificateServicesClient (CertEnroll) errors that have emerged following the installation of the July 2025 preview update and subsequent Windows 11 24H2 updates. This guidance comes as part of the company’s ongoing efforts to address various issues that have surfaced in recent months, which have led to erroneous warnings without any real impact on system functionality.
In a similar vein, last month, Microsoft encouraged users to overlook Windows Firewall configuration errors that appeared after rebooting their systems post-installation of the June 2025 preview update. Earlier in April, the tech giant confirmed and rectified a known issue that resulted in invalid 0x80070643 failure errors after users applied the April 2025 Windows Recovery Environment (WinRE) updates. Additionally, that same month, a bug that erroneously triggered BitLocker drive encryption errors on both Windows 10 and Windows 11 devices was also addressed.
When the company acknowledged this particular issue in October, it clarified that it primarily affected managed Windows environments where drive encryption was enforced for both the operating system and fixed drives.
More errors added to the ignore list
This past Monday, Microsoft updated its Windows release health dashboard, reiterating its request for users to ignore yet another error event linked to recent updates. This error, logged in Event Viewer with Error ID 57, indicates that “The ‘Microsoft Pluton Cryptographic Provider’ provider was not loaded because initialization failed.”
The company explained, “Following installation of the July 2025 Windows non-security preview update (KB5062660) and subsequent updates, including the August 2025 Windows security update, Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored.” They emphasized that although this event is logged every time the device restarts, it does not signify any issues with active Windows components.
Microsoft further clarified that this known issue stems from a feature still under development and not yet fully integrated into the operating system. As with previous similar errors, the company reassured users that these notifications do not affect Windows processes, and no action is required on their part to prevent or resolve the matter.
