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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-07-13T18:05:54+00:00

    Started moving my pc's over to Windows 11. No such error there. Did a test batch of PC's to see if the error will pop up, nothing so far. Now to just migrate the rest of the 524 PC's. :(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-07-13T22:32:09+00:00

    Good to know StBlade,, that the event error doesn't carry over to Windows 11. Not ready to switch over yet, so just dealing with a 'basically' inert Event Error 2545 being recorded daily on my error log. Thanks for the update.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-07-14T05:41:53+00:00

    maybe switching to linux, or mac, or whatever other os will help too?

    btw ms does not allow me to install win11, even if i wanted to do it.

    Was this answer helpful?

    0 comments
  4. lmacri 2,505 Reputation points
    2023-07-14T13:39:59+00:00

    Started moving my pc's over to Windows 11. No such error there. Did a test batch of PC's to see if the error will pop up, nothing so far. Now to just migrate the rest of the 524 PC's. :(

    Hi StBlade:

    Given that these Event ID 2545 errors are logged at Applications and Services Logs | Microsoft | Windows | DeviceManagement-Enterprise-Diagnostics-Provider | Admin, I suspect that the logging of these errors also depends on whether the computer is used as a home PC (i.e., like my Win 10 Pro laptop, which logs this error once a day) or if it is used as a client on a LAN in a business or large organization.

    Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3208 * Firefox v115.0.2 * Microsoft Defender v4.18.23050.5-1.1.23060.1005 * Malwarebytes Premium v4.5.32.271-1.0.2051 * Macrium Reflect Free v8.0.7279

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-07-27T00:21:14+00:00

    I had this same issue with several dozen workstations and kept running into a brick wall. I had been at this for a couple weeks and nothing I tried worked. Finally, I did this on the problem workstation:

    1. sfc /scannow
    2. dism /online /cleanup-image /checkhealth
    3. dism /online /cleanup-image /scanhealth
    4. dism /online /cleanup-image /restorehealth
    5. Restart
    6. Go to HKLM\Software\Microsoft\Enrollments
    7. Delete the key referencing the MDM. This is usually the key with the most values and references the MDM. It should be obvious.
    8. Delete the key referencing WMI_Bridge_SCCM_Server
    9. gpupdate /force

    This kick-started things again and I was back up and running.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments