Latest Windows patches cause false alarm error to appear in event viewer
(2025/08/13)
- Reference: 1755105306
- News link: https://www.theregister.co.uk/2025/08/13/microsoft_lets_more_development_code/
- Source link:
Microsoft is having difficulty keeping development code out of the Windows event log after another message that users are advised to ignore turned up in the... event log.
The [1]problem can crop up after a user installs the July 2025 Windows non-security preview update or the August 2025 Windows security update. According to Microsoft, "Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored."
Oh, good.
[2]
The issue only shows up in the Event Viewer with error ID 57 and the text, "The 'Microsoft Pluton Cryptographic Provider' provider was not loaded because initialization failed." Microsoft said, "This event is related to a feature that is currently under active development."
[3]German security researchers say 'Windows Hell No' to Microsoft biometrics for biz
[4]Tested: Microsoft Recall can still capture credit cards and passwords, a treasure trove for crooks
[5]Ex-White House cyber, counter-terrorism guru: Microsoft considers security an annoyance, not a necessity
[6]Security? We've heard of it: How Microsoft plans to better defend Windows
[7]Pluton is the name given by Microsoft to a processor security architecture.
The problem affects Windows 11 24H2 and logs every time an affected device restarts. The CertificateServicesClient is a Windows component that deals with certificate enrolment and renewal. Administrators are therefore on the lookout for issues, and seeing several machines complaining about the component could be alarming.
[8]
[9]
In addition to issuing the instruction to ignore the message, Microsoft said, "We are working on a resolution and will provide an update in an upcoming release."
This isn't the first time the company has accidentally let some development code [10]leak into into production versions of Windows. A June update left the Windows Firewall complaining about a mystery piece of "under development" code.
[11]
However, since dodging updates such as August's patches isn't a good idea (August's emission was quite the [12]smorgasbord of fixes ), it seems inevitable that several Windows users are going to be on the receiving end of the event log message.
Microsoft said, "There is no impact to Windows processes associated to this event and no action is required to prevent or resolve this error."
So that's ok then, move along please, as there's nothing to see here. ®
Get our [13]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24H2#2877msgdesc
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2025/08/07/windows_hello_hell_no/
[4] https://www.theregister.com/2025/08/01/microsoft_recall_captures_credit_card_info/
[5] https://www.theregister.com/2025/08/08/exwhite_house_cyber_and_counterterrorism/
[6] https://www.theregister.com/2024/11/25/microsoft_talks_up_beefier_windows/
[7] https://www.theregister.com/2020/11/17/microsoft_pluton_cpu_hardware_security/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[10] https://www.theregister.com/2025/07/03/microsoft_windows_firewall_error/
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://www.theregister.com/2025/08/12/august_patch_tuesday/
[13] https://whitepapers.theregister.com/
The [1]problem can crop up after a user installs the July 2025 Windows non-security preview update or the August 2025 Windows security update. According to Microsoft, "Event Viewer may display an error related to CertificateServicesClient (CertEnroll) which can be safely ignored."
Oh, good.
[2]
The issue only shows up in the Event Viewer with error ID 57 and the text, "The 'Microsoft Pluton Cryptographic Provider' provider was not loaded because initialization failed." Microsoft said, "This event is related to a feature that is currently under active development."
[3]German security researchers say 'Windows Hell No' to Microsoft biometrics for biz
[4]Tested: Microsoft Recall can still capture credit cards and passwords, a treasure trove for crooks
[5]Ex-White House cyber, counter-terrorism guru: Microsoft considers security an annoyance, not a necessity
[6]Security? We've heard of it: How Microsoft plans to better defend Windows
[7]Pluton is the name given by Microsoft to a processor security architecture.
The problem affects Windows 11 24H2 and logs every time an affected device restarts. The CertificateServicesClient is a Windows component that deals with certificate enrolment and renewal. Administrators are therefore on the lookout for issues, and seeing several machines complaining about the component could be alarming.
[8]
[9]
In addition to issuing the instruction to ignore the message, Microsoft said, "We are working on a resolution and will provide an update in an upcoming release."
This isn't the first time the company has accidentally let some development code [10]leak into into production versions of Windows. A June update left the Windows Firewall complaining about a mystery piece of "under development" code.
[11]
However, since dodging updates such as August's patches isn't a good idea (August's emission was quite the [12]smorgasbord of fixes ), it seems inevitable that several Windows users are going to be on the receiving end of the event log message.
Microsoft said, "There is no impact to Windows processes associated to this event and no action is required to prevent or resolve this error."
So that's ok then, move along please, as there's nothing to see here. ®
Get our [13]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-24H2#2877msgdesc
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://www.theregister.com/2025/08/07/windows_hello_hell_no/
[4] https://www.theregister.com/2025/08/01/microsoft_recall_captures_credit_card_info/
[5] https://www.theregister.com/2025/08/08/exwhite_house_cyber_and_counterterrorism/
[6] https://www.theregister.com/2024/11/25/microsoft_talks_up_beefier_windows/
[7] https://www.theregister.com/2020/11/17/microsoft_pluton_cpu_hardware_security/
[8] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[10] https://www.theregister.com/2025/07/03/microsoft_windows_firewall_error/
[11] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aJ0K9d7OWsXPNMCfV7KAoAAAAQM&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[12] https://www.theregister.com/2025/08/12/august_patch_tuesday/
[13] https://whitepapers.theregister.com/
Re: Boundary issues
kmorwath
Those who aren't rookie are fired by Nadella everytime he needs to fatten the quarterly result and increase his bonuses.
Proper build processes? He may have heard of them, but since he found they don't bring more money, he's not interested - shareholders wouldn't approve it.
Re: Boundary issues
Tom Chiverton 1
It's probably run by an AI
Re: Boundary issues
Paul Herber
More likely to be just Al, not AI.
Al all alone. Always. Alive, Alliterative.
Let's the games begin!
ecofeco
I can see the circus in the admin offices now.
I know there is nothing I love more than explaining an issue does not really exist, that it's an M$ problem and there is nothing to be done until M$ fixes it, to someone who has not read the news yet.
Anonymous Coward
This has been going well before the last updates were released and they still haven't fixed it.
That's a shame
Dan 55
The event viewer had just enough entries and no more to accurately pinpoint problems before this happened. It's ruined for me now.
Boundary issues
Thinking Microsoft might have some boundary issues. Not having flags on code approved for Production - or the build process ignoring those flags - sounds like a rookie mistake.