FIX Event 10016 on RuntimeBroker on Server 2016: Application-specific permission settings do not grant Local Activation permission for COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}(Solved)

FIX Event 10016 on RuntimeBroker on Server 2016: Application-specific permission settings do not grant Local Activation permission for COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}(Solved)

The DistributedCOM error with Event ID 10016 on Windows Server 2016 with description “Application-specific permission settings do not grant Local Activation permission for COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}” is caused due to insufficient permissions of the SYSTEM account on the RuntimeBroker process.

FIX Event 10016 on RuntimeBroker on Server 2016

This tutorial contains step-by-step instructions to fix following warning events on Windows Server 2016/2019, with description:

Source: Distributed COM
Event ID: 10016

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 AUTHORITYSYSTEM 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.

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 DomainNameAdministrator SID (S-1-5-21-3604224176-2080924081-1124411871-500) 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.

 

How to FIX: Application-specific permission settings do not grant Local Activation permission for COM Server application RuntimeBroker on Server 2016.

Step 1. Take Ownership of RuntimeBroker registry key.

1. Open Registry Editor and navigate to the following location:

  • HKEY_CLASSES_ROOTAppID

2. Expand the AppID key and then right-click at {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} and select Permissions.

image

3. At ‘Permissions’ window, click Advanced.

image

4. Click Change Owner to take the ownership from ‘TrustedInstaller’.

image

5. Type Administrators and press OK.

image

6. Check the Replace owner on subcontainers and objects checkbox and click Apply.

image

7. Select Administrators and click Edit.

image

8. Select the Full Control checkbox in order to give full permissions to Administrators and press OK three (3) times to apply the change.

image

9. Close the Registry Editor.

Step 2. Modify the permissions on RuntimeBroker COM Server application.

1. Open Component Services. To do that:

    1. Simultaneously press the Windows image + R keys to open run command box.
    2. Type dcomcnfg and press Enter.

image_thumb16

2. Expand Component Services -> Computers -> My Computer -> DCOM Config.

3. From View menu choose Detail.

image_thumb34

4. Right-click on RuntimeBroker and select Properties.

image

 

5a. At Security tab, click Edit on Launch & Activation Permissions.

image

5b. If you receive the security message to remove the unrecognized permission entries click Remove.

image

6. Click the Add button.

image

7. Type Administrators; SYSTEM and click OK.

image

8. Check the Local Activation checkbox on both Administrators & SYSTEM accounts and click OK twice to apply the change.

image

9. Close Component Services window and restart the server.

That’s it! Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.

If this article was useful for you, please consider supporting us by making a donation. Even $1 can a make a huge difference for us in our effort to continue to help others while keeping this site free:

Adblock test (Why?)

Leave a Reply

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