When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works.

Microsoft asks you to ignore a Windows 11 Event Viewer error yet again

Microsoft has confirmed the presence of yet another bug in Event Viewer for Windows 11, version 24H2 that exists even after installing August's Patch Tuesday updates released today.

A Windows 11 logo as a window with some ladybugs crawling towards it

Back in July, Microsoft confirmed that Event Viewer is showing an error related to Windows Firewall following a Windows Update, but users should ignore it as it is related to a feature that is still under development. There was some back and forth on this topic as Microsoft claimed that the issue had been fixed in July's Patch Tuesday before admitting that it had made this announcement by mistake. Although that problem was eventually resolved by the end of July, it now seems like Windows users now have to face a similar issue.

Over on its Windows Release Health dashboard, Microsoft has begun tracking a new bug related to the Event Viewer. As history repeats itself, this software is now showing an error related to CertificateServicesClient (CertEnroll). The error ID for this event is 57, with the accompanying error message stating that "The 'Microsoft Pluton Cryptographic Provider' provider was not loaded because initialization failed".

This entry is logged to Event Viewer each time the device is restarted, but Microsoft says that customers can safely ignore it as no actual Windows component is impacted. Once again, Redmond has emphasized that this entry is being logged due to an upcoming feature that is still under development. As such, there is no impact on Windows processes and no action required from IT admins or end-users.

It is important to note that this bug affects Windows 11, version 24H2 only. It is present for customers who installed the KB5062660 non-security preview update for July and even the Patch Tuesday update for August 2025 which became available today. Microsoft has assured customers that it is working on a fix that will be released in an upcoming update, but has not provided concrete timelines yet. That said, it seems like there is nothing to worry about, so customers should carry about with their business as usual.

Chrome logo
Next Article

Perplexity wants to buy Chrome for $34.5 billion with its $18 billion piggy bank

A logo of Visual Studio 2022 on a light orange background
Previous Article

Say hello to GPT-5 in Visual Studio

2 Comments

Load the comments and join the conversation!

Read the comments, ask the editors questions, show respect and join the conversation.

Click here