Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Hi again,

When you do a search for that GUID key in registry editor does it have any subkeys ?

I also suspect some software running at start up is triggering this error so I suggest you disable systematically anything in Taskmanager "StartUp" untill the error vanishes.

Cheers,

I'll check the registry for any subkeys and I'll try the startup, although I don't have so many startup items.

Thanks a lot for your help. If I do solve it, I'll post back the results.
Take care!

Hi,

You're welcome.

Cheers,

Hi,

Ok, now try to disable the programs that are run at start up one by one untill the error no longer occurs.

Cheers,

For those of you that use the instructions in this thread to gain access to the offending DCOM component via the command "dcomcnfg" I found a really simple way to avoid having to change CLSID and APPID permissions in the Registry in order to change the DCOM entry using "dcomcnfg".

Download ExecTI from here.... ExecTI. Use either the CLSID or APPID in the Event log message to find the name of the DCOM component in your Registry. Use ExecTI to run "dcomcnfg" as TrustedInstaller which is the thing you need to change in your Registry using the typical instructions in this thread.

Just go to the DCOM name you found and you will notice you now have access to the entry and can change it. No need to go into the Registry and change permissions. You only need to get the name of the DCOM entry. The Registry entries will remain owned by TrustedInstaller.

streetwolf said:

For those of you that use the instructions in this thread to gain access to the offending DCOM component via the command "dcomcnfg" I found a really simple way to avoid having to change CLSID and APPID permissions in the Registry in order to change the DCOM entry using "dcomcnfg".


Download ExecTI from here.... ExecTI. Use either the CLSID or APPID in the Event log message to find the name of the DCOM component in your Registry. Use ExecTI to run "dcomcnfg" as TrustedInstaller which is the thing you need to change in your Registry using the typical instructions in this thread.

Just go to the DCOM name you found and you will notice you now have access to the entry and can change it. No need to go into the Registry and change permissions. You only need to get the name of the DCOM entry. The Registry entries will remain owned by TrustedInstaller.

can you make a guide with pictures ? to be 100% , because it's messy sometimes.

The 10016 from the the beginning of these posts (pg 1) has returned to my pc following the last update but the procedure on page 7 no longer works, so could the person that made that shell file make or modify another to make it work again, thanks, This is the error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} 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.

Hey guys, there is actually quite an easy fix for the DCOM errors. This method solved them all for me !

In Group Policy Editor (run: gpedit.msc), go to Computer Configuration > Administrative Templates > System > Distributed COM > Application Compatibility and enable "allow local activation security check exemptions"