If the Event Viewer displays an error message Application-specific authorization settings do not grant local activation authorization for the COM Server application, this article will help you. It comes with a Event ID 10016, and this error mainly appears after upgrading the operating system. While this error does not affect the user experience of the normal Windows 10 user, some of you may want to know why this is happening and what you can do to this subject.
The whole error message looks like this:
Application-specific authorization settings do not grant local activation authorization for COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB- 156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to user NT AUTHORITY LOCAL SERVICE SID (S-1-5-19) from LocalHost (at ; LRPC help) running in SID application container not available (not available). This security authorization can be changed using the component services administration tool.
For your information, CLSID and APPID may be different on your computer as they represent a component service on your computer. Regarding the solution, it is already mentioned in the error message. You need to change the security permission from an admin tool in Windows 10.
Application-specific authorization settings do not grant local activation
To fix app-specific permission settings don't grant local activation error in Windows 10, do the following:
- Identify and confirm CLSID and APPID
- Change the ownership of the CLSID key from the Registry Editor
- Change security authorization from component services
Read on for the steps in detail.
You need to identify the CLSID and APPID. As they can be different on your computer, it is very important to recognize them. Otherwise, you will not be able to get rid of this Event Viewer error message. Based on the error message mentioned above, the CLSID is {C2F03A33-21F5-47FA-B4BB-156362A2F239} and the APPID is {316CDED5-E4AE-4B15-9113-7055D84DCC97}. There is another element called SID, but it is not necessary at the moment.
You should now find the component that is creating the problem. To do this, open the registry editor on your computer. To do this, press Win + R, type regeditand the Enter button. After that go to this path-
HKEY_Classes_RootCLSID
Don't forget to replace the Enter-your-CLSID with the original CLSID that you received in the error message. After getting it, you should find the APPID on your right. Make sure that this APPID and the previous APPID (which is mentioned in the error message) are identical. After confirmation, right click on the CLSID on your left and select the permissions option.
Then click on Advanced button.
By default, this key belongs to TrustedInstaller, but you must change the owner to Administrator. To do this, click on the Change button in the Advanced security settings window> note "Administrator"> click on the Check names button> click on D & #39; agreement button.
You must also select Replace owner of subcontainers and objects check box.
After that select administrators of Group or user names and check the box Allow / Full Control check box. Now save your settings.
You should also check the Default – Data first name. In this example, the default data name is Immersive shell. It should be different if the CLSID and APPID are different in your error message.
After that, you also need to take ownership of the APPID. To do this, go to this path in the Registry Editor –
HKEY_Local_MachineSoftwareClassesAppIDyour-APPID
You must do the same as above to change the ownership of this registry key.
If you are having trouble changing the ownership of the registry key, you can check out our free tool called RegOwnit which allows you to do so with one click.
If you have completed these steps, you should open the Component services. You can search for it in the search area of the taskbar and click on the corresponding result. After opening Component Services, go here-
Component Services > Computer > My Computer > DCOM Config > Immersive Shell
Based on this example, the CLSID corresponds to this Immersive Shell component service. You have to find the Default – Data name you got from Registry Editor. After recognizing, right-click on the component service and select properties. Here you should find the Application id or APPID which you can confirm again.
Then go to security tongue. Here you will find three labels, including Launch and activation permissions. Click on the correspondent edit button.
If you receive a warning message, click the Cancel button and go ahead. You must follow the same steps as above to add two accounts-
After adding them, select one at a time and give Local launch and Local activation permissions for both.
Save the changes, you will no longer get the same problem in the Event Viewer.
Whether you encounter the problem with RuntimeBroker or Immersive Shell or any other process, the solution is the same for everyone.