Event 2545 "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider"

Anonymous
2022-10-27T22:53:43+00:00

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.

0 comments

72 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-13T13:01:00+00:00

    I confirm the same problem. USB mouse stopped working and notebook freezes (DEll XPS) Windows 10 22H2, Enterprise.

    I've replaced mouse with the very old PS/2 mouse - no problems.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-01-11T02:33:27+00:00

    my mouse just stopped working.
    i restarted, looked at the events and i have this.

    first occurence is from nov 9 2022.

    i bought the mouse nov 7 2022.

    usb mouse, used ps/2 before.

    still on 21H2.

    I confirm, I have the same problem on my laptop. 2 out of 3 usb ports work, but devices connected to them do not respond in any way

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-01-09T15:07:03+00:00

    Same here. Win 10 Pro. The system froze, rebooted, and found this to be the reported error before the kernel panic.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-01-04T15:51:19+00:00

    "... dont care ..."

    surely, but

    isnt their current policy, to release updates only twice a year?

    this was the winter break 2022 update. maybe wait for the summer break 2023, for something to happen ;)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. 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

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments