How to Fix Event ID 10016, DistributedCOM Windows.SecurityCenter.WscBrokerManager Error in Windows 10

Monday, December 17, 2018 0

Hi Folks!

I am back today with another solution to a common problem. It seems every time Microsoft releases an update to Windows 10, Your event log is full of Event ID 10016 Errors. these errors range from issues with Windows Security Center, to general DCOM Errors involving Shell host.

Now according to Microsoft, some of these DCOM Errors are by design and are harmless. To quote the recent Microsoft DCOM Event ID 10016 is logged in Event Viewer Knowledge Base article:

These 10016 events are recorded when Microsoft components tries to access DCOM components without the required permissions. In this case, this is expected and by design.

A coding pattern has been implemented where the code first tries to access the DCOM components with one set of parameters. If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it does not skip the first attempt is because there are scenarios where it can succeed. In those scenarios, that is preferable.

How to Fix Faulting application name: devicecensus.exe, version: 10.0.17134 In Windows 10 1803 April 2018 Update

Sunday, June 17, 2018 2


As you may not already know, The Windows 10 Spring Creator's Update 1803 April of 2018 has been officially cleared for the Business/Enterprise update channel for Windows Update. This means those that have been holding on to the 1709 or earlier versions of Windows 10 will probably be prompted upgrade soon. While this version of Windows does bring some new features, it also brings some new bugs and errors. the most annoying of these errors is the Faulting application name: devicecensus.exe, version: 10.0.17134.1 error that shows up in the event log.

Today I am going to show you how to solve this annoying error. So without further ado, lets get started!

How to Fix The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {9E175B6D-F52A-11D8-B9A5-505054503030} and APPID {9E175B9C-F52A-11D8-B9A5-505054503030} to the user in Windows 10 Event ID 10016

Saturday, May 20, 2017 0



It feels good to be back after such a long hiatus! Today we are going to go over an error I have noticed pop up on Windows 10 with the Anniversary and the Creators Update. This error can cause Windows Login to take much longer then it should, and it fills your Windows Event Viewer up with a bunch of annoying red error warnings. So how to we fix this issue?

1. What Causes this error? - This error appears to be caused because Windows does not grant the user account logging into the system the appropriate user rights and permissions, in this case Local Activation permissions, for the DCOM object in question. This creates an unnecessary error condition causing it to re-try multiple times until its successful activating under the System authority account. This will probably be fixed in a future Microsoft Optional update or Hotfix patch later down the road, but until that time comes lets fix it.


Copyright ronwoods.us. Powered by Blogger.

Get Updates By Email

Popular Posts