The Application-Specific Permission Settings do not Grant Local Activation Permission for the COM Server Application

Updated April 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link

1. Download and install the repair tool here.
2. Let it scan your computer.
3. The tool will then repair your computer.

Windows 10 is the latest and best Microsoft operating system, and the company pushed users to openly update the previous ones. It makes sense and there are some improvements over its predecessors. However, recently, several error messages have appeared in the system logs “Error event identifier DistributedCOM (DCOM): 10016″.

These bugs are quite common, and many different error logs are maintained depending on the error. In this article we will focus on the topic “Application-specific authorization settings do not provide NT AUTHORITY user \ LOCAL SERVICE SID () LocalHost address no local activation permissions for COM server application with CLSID {}. and APPID {} (using LRPC) is executed in the application container. SID is not available (not available). This security permission can be changed by using l Error message of the Component Services Administration Tool.

Having received numerous messages from several users, we decided to investigate the problem and find a solution to completely eliminate it. In addition, we investigated the cause of this error and listed it below:

Invalid permissions: An error occurs when a certain process does not have sufficient permissions to access the DCOM components listed in the event log.

Note. In some cases the system may work fine despite this error. If so, it is best to allow the error to occur. However, if a particular application does not work properly, follow the instructions below:

Allow access to the DCOM components using the registry editor

• Run the registry editor (regedit.exe).
• Go to the registry section that corresponds to your CLSID. In my case it is HKEY_CLASSES_ROOT \ CLSID \ {000209FF-00000-0000-C000-00000046};
• In some cases you may also need to check the HKEY_CLASSES_ROOT registry section \ Wow6432Node \ CLSID . If you connected to the registry remotely, it is located in the HKEY_LOCAL_MACHINE registry section \ SOFTWARE \ Classes \ AppID.
• The application name must be specified in the class parameter (in my case Microsoft Word Application).
• The most common DCOM 10016 error occurs in the following components: Immersive Shell.
• CLSID: {C2F03A33-21F5-47FA-B4BB-156362A2F239}
• APPID: {316CDED5-E4AE-4B15-9113-7055D84DCC97}
• RuntimeBroker
• CLSID: {D63B10C5-BB46-4990-A94F-E40B9D520160}
• APPID: {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
• Right-click the registry section and select Permissions.
• Click the Advanced button.
• NT Service \ TrustedInstaller or SYSTEM are listed under “Owner”.
• Click the “Edit” button and enter a name for the administrator account. Save the changes.
• Note that the name of the current owner of the registration key has changed in your account. Check the Replace sub-container and object owner checkbox and click OK.
• Add your Administrator account to the authorization list and grant it full access rights.
• You have granted permissions for the registry section with CLSID. Now you need to repeat the previous steps and change the owner of the administrator account and permissions for your APPID registry partition from the error description (for example, HKEY_CLASSES_ROOT \ AppID \ {AD65A69D-3831-40D7-9629 -9B0B50A93843}).

Change security properties

• Now close the registry editor.
• Open the Component Service by going to Start |.
• Expand Component Services | Computer | My computer | DCOM Configuration
• Right-click the subnode with the specified [GUID] and select “Properties”.
• Go to the “Security” tab, then click “Add User”. Add a local service, click “Apply” and give the user all permissions.
• If you receive a warning message, click “Cancel” and continue. To add two accounts, you need to follow the same steps as above:
  • SYSTEM
  • LOCAL SERVICE
• After adding, select one by one and give the “Local Launch” and “Local Activation” permissions.
• Save the changes. The same problem is no longer shown in the event viewer.

Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here