HOWTO fix events 10016 related to WSC stuff


Almost 2 years ago, I wrote a post about how to fix events 10016, but with the latest Windows 10 versions, a new case popped up.

Three events 10016 continue to pop up similar to the following:

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The other two are about SecurityCenter.WcsBrokerManager and SecurityCenter.WscDataProtecting.

The problem here is that there isn’t any COM entity to fix.


Looking for a solution on the net, I found someone that found the solution.

The problem seems to pop up during the system startup phase because the Security Center service isn’t already started.

To fix it, we have to set the Startup Type from Delayed Start to Automatic.

The problem is that we cannot use our beloved Services window.

We need to open the Registry Editor and:

  • go to:
  • change the DelayedAutoStart from 1 to 0
  • reboot.