Windows Server

Solution for Error – Event ID 10016 – DistributedCOM

The following events logged on the system event logs running windows. In this article will see how to fix this issue.

Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Description: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}

Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Description: 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}

Follow the below steps to fix this issue:

1. Go to Regedit

2. Then go to – Go to HKEY_Classes_Root\CLSID\*CLSID*.
That means – Go to HKEY_Classes_Root\CLSID\{C2F03A33-21F5-47FA-B4BB-156362A2F239}

3. Right click on it then select permissions

4. Click Advance and change the owner to Administrators group. Also click the box that will appear below the owner line. (“Replace owner …”)

5. Apply full control

6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.
That means – Go to HKEY_LocalMachine\Software\Classes\AppID\{316CDED5-E4AE-4B15-9113-7055D84DCC97}

7. Right click on it then select permission

8. Click Advance and change the owner to Administrators group

9. Click the box that will appear below the owner line

10. Click Apply and grant full control to the Administrators group

11. Go to Administrative tools

12. Open component services

13. Click Computer, click my computer, and then click DCOM

14. Look for the corresponding service that appears on the error viewer [Immersive Shell]
That means – Look for the one that appeared at the right panel of the RegEdit. For example, the AppID Registry (316CDED5-E4AE-4B15-9113-7055D84DCC97) contains the “Immersive Shell” Data with a (Default) as a name. Now look for “Immersive Shell”.

15. Right click on it then click properties

16. Click security tab then click Add User. Add Local Service then apply

17. Tick the Activate local box

The solution was originally discussed here (https://bit.ly/2XwmWfK). Thank you both for addressing the problem and providing the solution!

I just tried to make it more simple and presentable.

If you wish you can work around this issue by modifying the permissions on DCOM components to stop this error from being logged. However, not recommend this method because these errors do not adversely affect functionality and modifying the permissions can have unintended side effects.

Leave a Reply

Your email address will not be published. Required fields are marked *