FIX: Application-specific permission settings do not allow local activation for COM server application (resolved) – wintips.org

Event Viewer System Alert “Application-specific permission settings do not allow local activation for the COM Server application…” event ID “10016” can log in with Microsoft components on computers running Windows 10, Windows Server 2019, or Windows Server 2016. Attempt to access DCOM components without required permissions.

According to Microsoft, the recommended course of action is to ignore 10016 events, as they do not adversely affect functionality and are by design. However, if you want to fix the problem, continue reading below.

Application-specific permission settings do not allow local activation for a COM server application

This guide provides step-by-step instructions on how to fix warning 10016 in Event Viewer on Windows 10 and Windows Server 2016/2019, with a description of:

Source: distributed COM
Event ID: 10016

Application-specific permission settings do not allow Local Activation for a COM Server application with a CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to user ComputerName\Username SID (S-1-5-21-3546043924-4163678793-3661266528-1001) from LocalHost (using LRPC) running in application container Not Available 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 the COM Server application (Event ID: 10016) on Windows 10 and Server 2016/2019.

Step 1. Change the permissions on the APPID registry key.

1. Find the APPID of the COM Server application from event 10016 with insufficient rights.

For example, in this example, the APPID is: {15C20B67-12E7-4BB6-92BB-7AFF07997402}

Do not allow local activation

2. Open Registry Editor and navigate to:

3. Expand the AppID key and click on the APPID mentioned in event 10016. (eg “{15C20B67-12E7-4BB6-92BB-7AFF07997402}” in this example)

4a. In the right pane: Note the AppID name in the default REG_SZ value. (eg “PerAppRuntimeBroker” in this example).

4b. In the left panel: Right click Click and select APPID Permissions:

image

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

image

6. press Change Registry key ownership owner.

image

7. Type Administrators and press OK.

image

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

image

9. Then double click to open Administrators access

image

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

image

11. Shut down Registry editor and restart your personal computer.

Step 2. Change the permissions on the 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

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

3. From whom Appearance menu selection Detail.

image

4. Right click In the name of the APPID you saw in step 1 (4a) above (eg “PerAppRuntimeBroker” in this example) 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 LOCAL SERVICE and press OK.

image

8. Check it out the Local activation check box and click OK twice to apply the change.

image

9. Close the Component Services window and restart your personal computer.

10. After restarting, the “Application-specific permission settings do not allow local activation for COM server application” error should be resolved.

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