FIX Event 10016 in RuntimeBroker on Server 2016: Application-specific permission settings do not allow Local Activation for a COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID-3688078-378ABAC-278-38ABAC-27. (Solved) – wintips.org

DistributedCOM error with Event ID 10016 on Windows Server 2016 “Application-specific permission settings do not allow local activation for COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and {8APP47ACID {88APP4EEC). -AFC4-AB702511C276}” RuntimeBroker occurred due to insufficient permissions of the SYSTEM account during the process.

FIX event 10016 in RuntimeBroker on Server 2016

This guide contains step-by-step instructions for fixing the following warning events in Windows Server 2016/2019, which describe:

Source: distributed COM
Event ID: 10016

Application-specific permission settings do not allow Local Activation for a COM Server application with a CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to user NT AUTHORITY\SYSTEM SID (S-1-5-18) running in application container LocalHost (using LRPC) Not Available SID (Not Available). This security permission can be changed using the Component Services administrative tool.

Application-specific permission settings do not allow Local Activation for a COM Server application with a CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to user DomainName\Administrator SID (S-1-5-21-3604224176-2080924081-1124411871-500) from LocalHost (using LRPC) running in application container SID (Not Available). This security permission can be changed using the Component Services administrative tool.

How to fix: Application-specific permission settings do not allow Local Activation for RuntimeBroker COM Server application in Server 2016.

Step 1. Take ownership of the RuntimeBroker registry key.

1. Open Registry Editor and navigate to:

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

image

3. In the “Permissions” window, click Complicated.

image

4. press Change Owner takes ownership from TrustedInstaller.

image

5. Type Administrators and press OK.

image

6. Inspection the Replace owner on subcontainers and objects check box and click Please apply.

image

7. select Administrators and press Editing.

image

8. select Full control To give full access to administrators, check the box and click OK three (3) times to apply the change.

image

9. Closing registry editor.

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

1. Open Component Services. For this:

    1. press at the same time Windows image + R buttons to open the run command window.
    2. Type dcomcnfg and press Enter.

image_thumb16

2. Expansion Component services -> Computers -> My computer -> DCOM configuration.

3. From whom Appearance menu selection Detail.

image_thumb34

4. Right click enabled RuntimeBroker and select Characteristics.

image

5a. Yes Security tab, click Editing enabled Permissions for launch and activation.

image

5b. If you receive a security message to remove unknown permission entries, click Turn off.

image

6. click on Add button.

image

7. Type Administrators; SYSTEM and press OK.

image

8. Inspection the Local activation checkbox in both Administrators & SYSTEM accounts and click OK twice to apply the change.

image

9. Close the Component Services window and restart the server.

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

If you found this article useful, please support us by donating. Even $1 can make a big difference for us We continue to help others while keeping this site free:

Leave a Comment