Event 10016, DistributedCOM

gil · 17 May 2018

Hi all,

I am getting a DCOM error which I'm unable to resolve.

Code:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user GIL-PC\Gil SID (S-1-5-21-4212775015-541755525-2815841924-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool.

If someone could share a screenshot of the ADVANCED SECURITY SETTINGS FOR {8BC3F05E-D86B-11D0-A075-00C04FB68820} on both CLSID and APPID, I might get it sorted.
I use SFC /SCANNOW and DISIM commands frequently to make sure nothing is corrupted.
But that last windows update created new event errors such as:
Event 3, Kernel-EventTracing
Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188
and Event 4,
The maximum file size for session "Circular Kernel Context Logger" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\system32\WDI\LogFiles\ShutdownCKCL.etl". The maximum files size is currently set to 20971520 bytes.
I've raised the log file size to be 100MB and I still get this error.

Hope I can get some direction for solving them.

Thanks!

coolmistry · 17 May 2018

I got same problem of your!! I have found the solve for Circular Kernel Context Logger see below link

>Fix: Session Stopped Due to the Following Error 0xc0000188 - Appuals.com

For Event 10016, DistributedCOM see post 2

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Windows 10 Forums

EdTittel · 17 May 2018

Please see this sticky thread in Performance and Maintenance: Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums. According to Microsoft itself, these 10016 errors occur by design, and do not need to be addressed.
HTH,
--Ed--

coolmistry · 17 May 2018

EdTittel said:

Please see this sticky thread in Performance and Maintenance: Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums. According to Microsoft itself, these 10016 errors occur by design, and do not need to be addressed.
HTH,
--Ed--

That great

gil · 18 May 2018

EdTittel said:

Please see this sticky thread in Performance and Maintenance: Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums. According to Microsoft itself, these 10016 errors occur by design, and do not need to be addressed.
HTH,
--Ed--

Sorry, this is not true in my case.
I manually messed up the permission settings for this windows management and instrumentation.
So I would appreciate any help on the matter.

EdTittel · 18 May 2018

If you search the threads here at TenForums, you'll find that the "secret" is to identify the GUIDs for the processes trying to make the DCOM change, then to grant them Trusted Installer or System levels of privilege so they can indeed make those changes. For example, see post#2 in this thread: Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Windows 10 Forums.
HTH,
--Ed--

PS: the afore-cited MS Support Note explains another way to do this by editing an XML file. I haven't tried that method myself, but they wouldn't recommend it if it didn't work. That's probably worth investigating, too.