Windows.SecurityCenter 10016 Event Crashing PC the Windows.SecurityCenter.SecurityAppBroker Windows.SecurityCenter.WscDataProtection are not in the registry

Question

Windows.SecurityCenter 10016 Event Crashing PC the Windows.SecurityCenter.SecurityAppBroker Windows.SecurityCenter.WscDataProtection are not in the registry

DJ Smith 0

Windows.SecurityCenter 10016 Event Crashing PC the Windows.SecurityCenter.SecurityAppBroker Winddows.SecurityCenter.WscDataProtection are not in the registry it that why im gettin gthat error

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-11-25T07:55:13.5233333+00:00

Hello @DJ Smith ,
The Windows SecurityCenter Event ID 10016 error involving SecurityAppBroker and WscDataProtection could be pointing to a DCOM permission issue rather than missing registry keys. It occurs when certain Windows components try to access DCOM without proper Local Activation rights. To fix this, note the CLSID and APPID from the Event Viewer details, confirm they exist in the registry, and then use Component Services (dcomcnfg) to grant Local Activation permissions to SYSTEM, LOCAL SERVICE, and NETWORK SERVICE. If registry entries are missing, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files. These steps typically resolve the error without manual deletion of CLSIDs or APPIDs.

Your answer

Pauline Mbabu 1,840 Reputation points Microsoft Employee

2025-11-25T07:55:13.5233333+00:00

Hello @DJ Smith ,
The Windows SecurityCenter Event ID 10016 error involving SecurityAppBroker and WscDataProtection could be pointing to a DCOM permission issue rather than missing registry keys. It occurs when certain Windows components try to access DCOM without proper Local Activation rights. To fix this, note the CLSID and APPID from the Event Viewer details, confirm they exist in the registry, and then use Component Services (dcomcnfg) to grant Local Activation permissions to SYSTEM, LOCAL SERVICE, and NETWORK SERVICE. If registry entries are missing, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files. These steps typically resolve the error without manual deletion of CLSIDs or APPIDs.