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

It's really kind of funny, it's October 10, 2023, and I found the same problem on my computer, but again, there is still no solution!

<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-22T16:23:06.4922813Z" /><EventRecordID>119</EventRecordID><Correlation /><Execution ProcessID="1480" ThreadID="14876" /><Channel>Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin</Channel><Computer>DESKTOP-KEB57AB</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>

It happen to me twice today with hard shutdown ,twice playing Jedin Fallen Order and crashing in the same place on the map
Just manage to get rid today of : The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled...anyway since the last updates this is just killing me right now ,one after another <My specs : Edition Windows 10 Pro

Version 22H2

Installed on ‎12/‎10/‎2022

OS build 19045.2364

Experience Windows Feature Experience Pack 120.2212.4190.0

Device name DESKTOP-

Processor AMD Ryzen 9 5900X 12-Core Processor 3.70 GHz

Installed RAM 32.0 GB

Device ID

Product ID

System type 64-bit operating system, x64-based processor

Pen and touch Pen support

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.

I'm having the same problem with my updated Windows 10 PRO

Hello, I too am seeing Event error 2545, "MDM Declared Configuration: Function (checkNewInstanceData) operation (Read isNewInstanceData) failed with,(The parameter is incorrect.)" on a daily basis., It has only appeared since, these updates were installed. As a matter of fact, I responded to Don's complaint as a 'Reply', on the Microsoft Community Feedback, and it seems to have disappeared. So, again, I am reporting that I , have this same exact error, and I have no 'Domain issues' to report as I do not connect to any group, school or organization with my computer. I am ignoring this daily error until Microsoft responds to a fix, as my computer 'seems' to be operating correctly.

Regards, Andy Asmussen

Hello Andy and thank you for your response. I checked the Feedback Hub to see if I had any type of response on the bug report I submitted about this but of course I had not and probably never will but they know about this. This is really getting aggravating with getting some type of error every time an update gets installed. If I hear anything I will let you know. Thanks again for helping to make this problem aware to people.

Respectfully,