Windows 10: Need help with Windows.SecurityCenter 10016 Event Crashing PC (Clean install)

Hello, so i saw a thread (https://answers.microsoft.com/en-us...t/92003aba-41bc-4de5-aa32-c2af28e285b3?page=2) and have the exact same problem. To the tee. I also did a clean install and still have the same issue. That thread is locked and i still cant find an answer.

:)

 

Event ID 10016, DistributedCOM Windows.SecurityCenter.WscBrokerManager

I don't think it's RuntimeBroker. Take a look at a recent one:

 

Why Certain DCOM 10016 Events Don't Matter

EdTittel and all here - many thanks for your posts. Just this Sunday, I upgraded my Win 10 Pro 1803 to 1903 (with a brief stop at 1809), and last night started getting these 10016 errors - those CLSID and AppID numbers exactly.

In the past, I have changed settings in DCOM. But, for now, for this CLSID and AppID, I shall no nothing.

However ... they seemed to start this time after TWO CHANGES:

1. I fixed a different Event 10016 event warning in an unusual way by changing its Service start in Registry -- see
   Event ID 10016, DistributedCOM Windows.SecurityCenter.WscBrokerManager
2. I installed yesterday's GiveAwayOfTheDay free version of AOMEI Partition Assistant Professional Edition 8.2.

So, are these two changes triggering the Event 10016 Warnings described here Or are they inherent to Win 10?

Thoughts? Thanks.

 

Need help with Windows.SecurityCenter 10016 Event Crashing PC (Clean install)

I'm still getting the 4 Windows Security Center errors (Event ID 10016)

Windows.SecurityCenter.WscCloudBackupProvider

Windows.SecurityCenter.SecurityAppBroker

Windows.SecurityCenter.WscBrokerManager

Windows.SecurityCenter.WscDataProtection

I think I may have fixed the other issue with the runtimebroker I had with Smittychat's recommendation. I will see over the next few days if it worked. But the Windows Security Center errors happen as soon as the PC boots...