Effective Methods To Resolve DistributedCom Error 10016

DistributedCom error 10016 is a permission issue that you may be stuck with and have no idea how to get rid of. If you are facing the above situation, then this is the article from which you can learn some of the effective methods to resolve the error. If you delay much longer in fixing the error, then the condition of the error may worsen, which will affect your computer badly. So, it is advised to try the below methods at the earliest to fix the error 10016.

About Error 10016

10016 is a well-known error that occurs due to the permission restriction to open an app, which requires a DCom server to start. It starts clogging the Eventvwr with numbers of events. And the error message window will display:

“The application-specific permission settings do not grant Local Activation permission for the COM server application”

In addition, a few users also get the error message as “The %1permission settings do not grant %2 %3 permission for the COM Server application…”.

Effects of DistributedCom Error 10016

Once you get the error 10016, you may see that the error message pops-up several times. And thus becomes a barrier to perform any other tasks. Sometimes, the system responds too slow to the input signals due to the error. Overall, this error will not let you work with your system peacefully. So, solving it quickly will be a great idea, and you can do it easily, by following the instructions provided below.

Procedures to Solve DistributedCom error 10016

Here in this section, we have provided a number of procedures with the help of which many of the users who faced DistributedCom error 10016 were able to solve the problem effectively. So, let’s not waste time, and proceed to the methods.

Procedure 1: Run a Script to Change Permissions in Component Services

To begin this procedure, you need to have enough time in your hand. To run this procedure completely and to get the error fixed, a minimum of one and a half hours is required.

Step 1: Locate the Exact Class ID under Registry Editor

First of all, you need to identify the process or service CLASS ID which is present in the error window. After that copy the CLASS ID. And to do this, at first you need to select the whole ID and then press both the Ctrl and C key together. The CLASS ID will look like something similar to “{D63B10C5…}”. Remember to include the curly braces as well while selecting the CLASS ID.

Now, press both the Windows and the letter R to get the Run bar open. On the Run bar, type regedit.exe and click on OK. This will open a permission window. Click on Yes to get the Registry Editor window open.

After that, from the available tabs, click on Edit. Next, select the “Find…” option from the menu window. Then, you will see that the cursor blinks beside Find what. Here, you need to paste the CLASS ID which you have already copied from the error window and then, press the Enter button. This will navigate you to the section “HKEY_CLASSES_ROOT\CLID” inside the Registry Editor window.

Now, on the right side of this window, you may see two options under Name. One is Default and the other is AppID. For the Default option, you may see the Data status as RuntimeBroker. Also, match this AppID with the ID which you have seen in the error message window. Definitely, it will match. Next, you need to run a script to make changes in Component Services for this particular service.

Step 2: Copy and Download the Codes under the PowerShell Window

Now, to make the required permission changes under Component Services for RuntimeBroker, at first, you need to run a script. The script will allow making such changes.

For this purpose, first, open the PowerShell as an administrator. After that, under the Administrator: PowerShell window, enter the script that you can search online. And then press the Enter button, to execute. Follow further steps to solve DistributedCom error 10016.

Step 3: Exfoliate Component Services till RuntimeBroker

After running the script as said above, now, open the Component Services window. For this, at first you need to press down the Windows button, to get the search bar active. Then, on the search bar, type “component services” without the quotes. After that, click on the top-most search result to get a window open.

Now, from the window that opens, locate the Component Services folder and expand it. Then navigate to the path as given below.

  • Computers> My Computer> DCOM Config

Next, go through the options until you get RuntimeBroker. You may see more than one options named as RuntimeBroker, but it will be located serially. Now, the question is how to identify the one which is listed in the error. The trick is very simple. But you need to apply the trick one by one on the RuntimeBrokers.

The trick is, you need to right-click on the RuntimeBroker and then select the Properties option. Next, from the available tabs under the RuntimeBroker Properties window, click on General. Here, you will find the AppID. Check if it matches with the error message generating AppID or not. And if matches, then it is the one you are searching for.

There may be more than one RuntimeBroker, which are responsible for the error. If you are getting errors in Event Viewer with an ID of 10016 for numbers of CLSID, then it signifies that both RuntimeBrokers need to repair.

Step 4: Solve RuntimeBroker Permissions Issue

Once you have identified the issue causing RuntimeBroker, go to the Security tab under the RuntimeBroker Properties window. And then ensure that the “Edit…” button, under the “Launch and Activation Permissions” section is active. If the “Edit…” button is greyed out, the PowerShell script did not execute in a true sense. Once you click on the “Edit…” button, you will get a pop-up warning window. From, this pop-up window, you need to click on the Cancel button. Here, you will see a list of default accounts.

Sometimes, Account Unknown are also enlisted in this window, do not do anything with it. And the other two options in this window are “ALL APPLICATION PACKAGES” and “SELF”. Here, on this window, you need to add two more accounts without deducting one. For this, click on the “Add…” button. And then, under the “Enter the objects name to select” box, enter SYSTEM. Next, click on the Check Names button> OK. On doing this, the SYSTEM named account gets added to the list.

Also, add an account named LOCAL SERVICE following the same steps as above.

Further, under the Security tab, click on each of these newly made accounts (SYSTEM and LOCAL SERVICE) one at a time and follow the steps as below. Activate the “Allow” option for both SYSTEM and LOCAL SERVICE, which you get under the Permissions section. After that, click on OK to save these changes.

Next, restart the computer and go ahead to use your device. Hopefully, you will not see DistributedCom error 10016 anymore.

Procedure 2: Deleting Registry Keys

Though most of the times the above method work, but if it is not in your case, then without losing hope try this method. The steps to follow for this is very simple and are as below.

At first, press down the Windows logo button to get the search bar active. Then, on it, type regedit.

Next, from the search results, click on regedit. This will open up a permission window, click on the Yes button to get the Registry Editor window open.

After that, from the left-hand side panel, click twice on the “HKEY_LOCAL_MACHINE” folder, to expand. And then follow the path as given below.

  • SOFTWARE> Microsoft> Ole

After clicking on the Ole folder, at the right-hand side, you will get the list of options as below.

  • Default
  • DefaultLaunchPermission
  • EnableDCOM
  • LegacyImpressionLevel
  • MachineAccessRestriction
  • MachineLaunchRestriction

Among which, delete all except EnableDCOM and LegacyImpressionLevel.

Next, restart the computer to get the issue resolved.

Mentioned above are the effective methods in solving DistributedCom error 10016. Hopefully, after following the fixes, you will get the error resolved. But in case, the issue persists, even after following the methods mentioned here, you can leave your feedback in the comment section below. We will try to find a workaround for the problem you might be facing.