Windows 10 operating system is one of the most used OS around the world. The version is the direct successor to Windows 8.1. This advanced version is preferred by most users due to manifold features that had been missing in the previous updates. However, it is not all a fairytale with Windows 10 version as it has been seen to cause the application-specific permission settings 10016 error in the system logs. In our today’s doc, we will be focusing on D63B10C5 BB46 4990 A94F E40B9D520160 error that does not grant local activation permission. So, let us look at the possible reasons behind the same and possible fixes for event ID 10016 the application-specific permission settings error in the doc.
How to Fix The Application-Specific Permission Settings 10016 Error
- Invalid permissions are the prominent reason behind the stated error if a specific program or an application cannot access DCOM components indicated in the event log.
- Distributed Component Object Model, also known as DCOM is a Microsoft software that allows components to communicate across different computers over a network.
- It enables using and reusing of components dynamically, without recompiling, on any available platform, at any time, and from any language.
- This COM extension might not be accessible by some programs on your device and hence can result in the application-specific permission error.
Considering the reasons that can stop certain applications or programs of your system to run because of 9CA88EE3 ACB7 47C8 AFC4 AB702511C276 error, the best possible solutions have been given below. One involves modifying permissions on APPID registry key and another one is modifying permissions on the COM server application. So, let us begin right away with fixing this error right away with the first method below:
Method 1: Modify APPID Registry Key Permissions
The first method to resolve event ID 10016 the application-specific permission settings involves modifying permissions on APPID registry key. As you know by now, this error is triggered when certain programs or processes of your system are unable to access DCOM components. Therefore, you must start by granting access to these DCOM components as listed below in the steps:
1. Open the Run dialog box, to open it press the Win + R keys together.
2. Type regedit and press Enter key to launch Registry Editor.
3. Now, navigate to the provided path in the Registry Editor.
Computer\HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}
4. Now, double-click on the Default key and note down its Value Data.
5. Next, navigate to the provided key folder path.
Computer\HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}
6. Now, right-click on the {9CA88EE3-ACB7-47c8-AFC4-AB702511C276} key from the left pane and select Permissions.
7. Select ALL APPLICATION PACKAGES in the Security tab and click on Advanced.
8. Next, click on Change next to the TrustedInstaller.
9. Now, click on Object Types…
10. Type Administrators in the box and click on OK.
11. Now, check the box for Replace owner or subcontainers and objects and select Apply.
12. Next, double-click on the Administrators to open the entry.
13. Now, select the Full Control checkbox and click on OK three times.
14. Finally, close the Registry Editor and reboot the PC.
Check if this solves D63B10C5 BB46 4990 A94F E40B9D520160 error or not.
Also Read: How to Stop Windows 10 From Asking Permission
Method 2: Modify Permissions on COM Server Application with CLSID
Once you have modified the registry key on your device, the next steps are to modify permissions on the COM server to resolve 9CA88EE3 ACB7 47C8 AFC4 AB702511C276 error. To do so, follow the steps provided below:
1. Launch the Run dialog box.
2. Now, type dcomcnfg command in it and press Enter key to open Component Services.
3. Next, expand Component Services and click on Computers in it.
4. Click on My Computer.
5. Next, expand DCOM config.
6. Now, from the main menu click on the View tab and select Detail.
7. Next, right-click on the APPID name that you noted down in Method 1 Step 4 and select Properties.
8. In the Properties tab, select Edit… in the Launch and Activation Permissions section.
5. Now, click on the Add… button.
6. In the box type LOCAL SERVICE and click on OK.
7. Select the Local Activation checkbox under Allow and click on OK twice.
8. Finally, close the Component Services window and restart the system.
Now, check if event ID 10016 the application-specific permission settings have been fixed.
Also Read: How to Change File Permissions in Windows 10
Frequently Asked Questions (FAQs)
Q1. How can I know which application is using Clsid?
Ans. Class ID or CLSID is a serial number that represents a unique ID for any program or application component in Windows. Therefore, it is easy to find all registry entries for an application component under the registry key {HKEY_CLASSES_ROOT\CLSID\{CLSID value}.
Q2. What causes application-specific permission settings error?
Ans. The error is usually caused when a specific process or program does not have enough permissions to access the DCOM components that are provided in the event log.
Q3. What is meant by CLSID on my computer?
Ans. CLSID on your computer is a globally unique identifier that helps identify a COM class object. You need to register a CLSID for each supported class of objects in case your server or container allows linking to its embedded objects.
Q4. How can I know which application server I am using?
Ans. You can know about the application server from the Connection Center.
Q5. What is meant by COM server application?
Ans. COM server application is a server in any object that provides services to clients. These services are present in the form of COM interface implementations that can be called by a client that is able to get a pointer to one of the interfaces on the server object. Two types of servers that are present include in-process and out-of-process.
Recommended:
We hope that our guide on the application-specific permission settings 10016 was helpful and informative enough to help you with resolving D63B10C5 BB46 4990 A94F E40B9D520160 error. Let us know by leaving your comments below if you have other queries, suggestions, or doubts.
