Same 2545. Fresh install of windows 10 pro. Good to know I'm not alone.
Event 2545 "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider"
Hello all! I was wondering if anyone else has noticed Event 2545 errors concerning Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider in your Event Log. I have been getting them since installing the last cumulative updates KB4023057, KB5018482 and KB5018202 on the 26th at 3:00 A.M.. I have had six of these errors since then. I have filed a report through the Feedback Hub. Can anyone shed a light on these and should I be concerned. My computer is running fine.
Respectfully
Level: Error
Keywords:
User: SYSTEM
Computer: DESKTOP-
Description:
MDM Declared Configuration: Function (checkNewInstanceData) operation (Read isNewInstanceData) failed with
(The parameter is incorrect.)
Event Xml:
<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-10-27T21:29:22.1840650Z" />
<EventRecordID>958</EventRecordID>
<Correlation />
<Execution ProcessID="3424" ThreadID="6376" />
<Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel>
<Computer>DESKTOP- </Computer>
<Security UserID=" " />
</System>
<EventData>
<Data Name="Message1">checkNewInstanceData</Data>
<Data Name="Message2">Read isNewInstanceData</Data>
<Data Name="HRESULT">0x80070057</Data>
</EventData>
</Event>
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
72 answers
Sort by: Most helpful
-
Anonymous
2023-03-17T04:09:21+00:00 -
Anonymous
2023-01-03T18:29:47+00:00 I disabled MDM thru the Task Scheduler-Microsoft-Windows-EnterpriseMgmt, right click on MDMMaintenenceTask, as the referenced post detailed. As the fault has occurred daily, shortly after boot up, checked the following day, and the Event Error 2545 was once again present with the same descriptor as previously displayed on each daily recorded event error, "MDM Declared Configuration: Function (checkNewInstanceData) operation (Read isNewInstanceData) failed with (The parameter is incorrect.)" (Note: I renbled the MDM after finding this still an existing problem) Still looking for a fix.
I had tried that as well Andy to no avail. MS are the ones that will have to fix this but it seems they do not care about it.
Respectfully
-
Anonymous
2022-12-27T20:13:19+00:00 Helped me to disable Mobile Device Management in gpedit.msc.
https://www.dslreports.com/forum/r33542172-WIN10-Event-2545-errors-since-November-updates
-
Anonymous
2023-04-17T13:07:02+00:00 "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" Yeah, same error ID 2545, it keep happen once a day, everyday from 2 november 2022, for me at least.
-
Anonymous
2022-11-10T07:51:43+00:00 I see this error report after booting up too, within 1 hour at the latest, reproducible and not limited to once a day.
However, I'm on 21H2 and don't even have your KB updates that supposedly cause this. It started on the 9th of November after the infamous monthly patch Tuesday where I got KB5019959, KB5020687, and KB890830.
In event viewer, I looked at Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider and noticed that the error under Admin always happens between Information events under Operational, specifically after "DcSvc: Service status updated. Current state:" (0x2) and (0x4) yet before (0x3) and (0x1).
No other errors or warnings under either list of logs.
Thank you for your input about this problem. What you found is quite interesting. Please file a bug report in the Feedback Hub if you had not done so already. The more bug reports about this the better chance to getting this taken care of or some kind of explanation.
Respectfully