Event ID 2545 Now Logged At Start After Updating Win10

Yesterday I updated my PC with KB5019959 and NET update KB5020687.

I started getting "DeviceManagement-Enterprise-Diagnostics-Provider" Event ID 2545 error logged every time I start my desktop.

Anyone know how to fix this?

I found this on a MS forum, but no solution.
https://answers.microsoft.com/en-us/...9-58fd1f8a716e

Post #22 in this TenForums thread has same issue, but no solution.
KB5018482 Windows 10 19042.2193, 19043.2193, 19044.2193

XML View of the logged error

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider" Guid="{3da494e4-0fe2-415c-b895-fb5265c5c83b}" />
<EventID>2545</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2022-12-09T22:23:43.6928858Z" />
<EventRecordID>2323</EventRecordID>
<Correlation />
<Execution ProcessID="5468" ThreadID="5300" />
<Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel>
<Computer>DESKTOP-</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="Message1">checkNewInstanceData</Data>
<Data Name="Message2">Read isNewInstanceData</Data>
<Data Name="HRESULT">0x80070057</Data>
</EventData>
</Event>

Ghot said:

@idahosurge

For a problem like this (concerning updates), it would help to know the exact Windows version.
Just type Winver in the Taskbar search box and post a screen shot.


Also, the latest update is: KB5020030 Windows 10 19042.2311, 19043.2311, 19044.2311, 19045.2311


And, if you haven't already, it might be time to move to 22H2.

Hi Ghot, below is the Win10 version

idahosurge said:

Hi Ghot, below is the Win10 version

I've got the same 2545 issue and Windows 10 Pro version and build as well... I've not found any solution by now.
(thanks for opening this post!)

Joe

Hi Denis.

Try3 said:

Are you experiencing a problem that has functional symptoms or are you only asking about the existence of this Event log entry?

No, I'm not: no functional symptoms so far.

Try3 said:

An entry in an Event log that is not reflected in any functional symptoms is not, of itself, a problem that needs fixing.

I see but maybe MS could have marked them as "warning"...

Try3 said:

It's really the other way around - an observed fault symptom might be reflected in Event log entries that can assist in fault rectification.


All the best,
Denis

Yes Denis, you're absolutely correct but I think there is something pathological, I speak for myself, in seeing alarms everywhere or in a mania for order (even just an error reported in the event log becomes a very serious fact)!

Thanks for your asnwer, see you!