New
#10
But it seems we are not alone:
https://answers.microsoft.com/en-us/...9-58fd1f8a716e
But it seems we are not alone:
https://answers.microsoft.com/en-us/...9-58fd1f8a716e
JPSilva and EternalEntity, hello.
I too had the error Event ID 2545 since 19045.2193.
With my limited knowledge of Windows 10 and time constraint, I concluded MDM is not needed for a standalone computer.
So I disabled it
Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider
{3da494e4-0fe2-415c-b895-fb5265c5c83b}
in Registry
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin Enabled to 0
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Operational Enabled to 0
Errors no longer logged.
If not important for stand alone pc then why show up on stand alone pc.
csmdew and JPSilva
New bug introduced in .2193?
It is only my understanding and am only responsible of my own computers.
The above is my way of addressing messy Event Viewer - I dislike errors/warnings.
Please disregard me and I apologize for the above "solution", csmdew and JPSilva.
Solution is fine but why does it bother stand alone pc if not intended for them. Does this also affect apps, since now quite a few are not working.