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

Hi DonT5,

Welcome to Microsoft Community.

According to the information you provided, we know that the MDM of Windows has an error. Could you please confirm whether your computer is in the domain environment （school/company/organization）?

The issue of MDM error reporting in a domain environment is beyond the support of the Answers community. I mean this is an event for professionals, if you need to diagnose problems with MDM, this page may be helpful Diagnose MDM failures in Windows 10，

Of course, I would recommend going to Microsoft Learn, which is a networking and problem-solving community for users who use the same specialized features as you, where you can ask questions and provide an error log so that skilled users can help you.

Thanks for your patience and understanding!

Best Regards,

Manson - MSFT | Microsoft Community Support Specialist

Hi DonT5,

Welcome to Microsoft Community.

According to the information you provided, we know that the MDM of Windows has an error. Could you please confirm whether your computer is in the domain environment （school/company/organization）?

The issue of MDM error reporting in a domain environment is beyond the support of the Answers community. I mean this is an event for professionals, if you need to diagnose problems with MDM, this page may be helpful Diagnose MDM failures in Windows 10，

Of course, I would recommend going to Microsoft Learn, which is a networking and problem-solving community for users who use the same specialized features as you, where you can ask questions and provide an error log so that skilled users can help you.

Thanks for your patience and understanding!

Best Regards,

Manson - MSFT | Microsoft Community Support Specialist

Hello Manson and thank you for replying. My Computer is not joined in a domain environment (school/company/organization) at all. Like I said these Errors did not start until after I installed the above mentioned updates. I have submitted a report via the Feedback Hub. I am using Windows10 Home
Version 22H2 OS build 19045.2193 Windows Feature Experience Pack 120.2212.4180.0. Thank you again for your input.

Respectfully

Hi DonT5,

Welcome to Microsoft Community.

According to the information you provided, we know that the MDM of Windows has an error. Could you please confirm whether your computer is in the domain environment （school/company/organization）?

The issue of MDM error reporting in a domain environment is beyond the support of the Answers community. I mean this is an event for professionals, if you need to diagnose problems with MDM, this page may be helpful Diagnose MDM failures in Windows 10，

Of course, I would recommend going to Microsoft Learn, which is a networking and problem-solving community for users who use the same specialized features as you, where you can ask questions and provide an error log so that skilled users can help you.

Thanks for your patience and understanding!

Best Regards,

Manson - MSFT | Microsoft Community Support Specialist

Hello again Manson. I wanted to update you and let you know that my wife's HP Envy laptop is getting the same error as my HP Omen desktop. We both updated our computers at the same time with the above mentioned cumulative updates KB4023057, KB5018482 and KB5018202. This definitely points to a bug in one of those updates. We are both running Win 10 Home Version22H2 and after installing the cumulative update we are both now on O.S. Build 19045.2193 and I think this should be escalated. If MS can't admit there is a bug in the updates and cannot find a solution in time then I will just delete the entries in the Admin Events event log under DeviceManagement-Enterprise-Diagnostics-Provider and disable that log like the logs pertaining to this discussion https://answers.microsoft.com/en-us/windows/forum/all/many-persistent-errors-in-event-viewer-after/c218ee04-89a5-4ce2-805d-565b8d1b1744 were done that has had no answers from MS as to why those errors are being generated or if there will be a fix. Personally I do not feel like I should have to chase this 2545 error or any other error created by updates every month down a bunch of rabbit holes to find a solution. I have reported it and now it is up to MS to take care of it.

I would like to thank you again for reading my discussion and offering your advice and knowledge to this problem. Hopefully MS will get this error sorted out along with why every month there are problems and errors generated by the installation of updates they send out to us.

Respectfully

Hello! If anyone else is seeing this 2545 Error concerning MDM Declared Configuration: [removed_js] operation (Read isNewInstanceData) failed with 

(The parameter is incorrect.) in your Event Viewer then please file a report in the Feedback Hub to draw the attention of the Devs.

Respectfully,

UPDATE:

I followed Manson's (Microsoft Agent/Moderator) suggestion to post my question in Microsoft Learn and I saw just now that I have an answer from a Community Expert there which answers my question. Please see the screen shot below.

Respectfully,

Hello, I too am seeing Event error 2545, "MDM Declared Configuration: [removed_js] 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, I too am seeing Event error 2545, "MDM Declared Configuration: [removed_js] 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,

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.

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

Not fix yet?