▷ How to fix DCOM error 10016 in Windows 7, 8 Y 10

Get a DCOM error with an ID. Of event 10016 means that a program tried to start the DCOM server using the DCOM framework, but the user does not have the necessary permissions to do it. This is a known bug that remains in previous editions of Windows, but that is not actually fixed when upgrading to a newer version of the operating system and is also seen in Windows 8 Y 10.

You will receive this as a system error and you will also receive a message containing a CLSID and APPID. This DCOM error may be completely harmless, but seeing him and having to deal with him all the time can be annoying.

But before proceeding with the troubleshooting process, make sure your system's power supply is up to par and is not faulty. If you are using any type of overclocking (CPU, GPU o RAM), lower it or remove it. What's more, make sure your system drivers, especially the GPU drivers, are up to date and then check if your system does not have the error in question.

There is a solution that has proven to work for many users, and for this you will need the CLSID and APPID of the error message, and you will have to follow the steps of the method indicated below.

Error DCOM 10016 in Windows

Method 1: grant the useful permissions S to the application causing the error

The CLSID and APPID are unique to an application, and having both can help you identify the app that is causing the problems. Even if you know which app is causing the problems, all you have to do is give it enough permissions so it doesn't cause trouble every time you need it. The steps to do it are very simple.

1. Press the Windows and R keys on your keyboard simultaneously and type RegEditar on Run Press Enter or click OK to open Registry Editor.

   Running Registry Editor

2. From the Registry Editor, expand HKEY_CLASSES_ROOT folder and CLSID folder inside.

3. Find the folder with the CLSID you received in the error message. Open the CLSID in Registry Editor

4. Now right click on it and select »permissions» and click on »Advanced«. Open the Advanced tab in Permissions

5. Click on Top, you will see the owner change it to the Administrators group.

6. At the bottom of the owner's window, also select Replace all minor object permission entries. Click OK and then select Yes for the Windows security warning.

   Replace all child object permission entries

7. Back in the main permissions window, click Add, enter All and click OK. Back in the main permissions window, select Everyone from the list of users at the top and select Full Control from the Allow column in the bottom half. Click ok.

   Click Add under Advanced Permissions

8. Apply full control.

9. Once you are done, expand HKEY_LOCAL_MACHINE inside, expand these folders: Software, then Classes, then AppID. Open AppID in Registry Editor

10. Go to the folder that has the same APPID that you received in your error message. Right click and choose the permissions and select »Advanced«.

11. With the steps 4 a 6, grant the application the necessary permissions.

12. Note that when looking at the folders with CLSID and APPID, you will see a registry key with the name of the service causing the problem.

13. Press the Windows key, type Control Panel and open the result, or open the Control Panel from the Start menu, depending on the version of Windows you are using. Open the control panel

14. Switch to the icon view at the top right and open Administrative Tools.

    PROFESSIONAL SUGGESTION: If the problem is with your computer or laptop, you should try using Reimage Plus, which can scan repositories and replace damaged and lost files. This works in most cases, when the problem originates due to system corruption. You can download Reimage for By clicking here

    Running administrative tools

15. Open component services. Open component services

16. Click Computer, followed by My computer. Open My Computer in Component Services

17. Now it finally finds the service that is causing the problem, right click on it and select properties. Then, click on the Security tab.

18. If the permissions are set correctly in the registry, you should be able to select Custom from the three categories in this window (launch and activation permissions, access permissions and configuration permissions). If any of these items are grayed out, repeat the steps above to set registry permissions and verify those settings.

19. Once Customize is selected in all three categories, select Edit under Launch and Activation Permissions. If you receive a warning that one or more attached permission entries have an unrecognized type, click delete. This just means that the registry permissions were set to a non-default value, what is necessary to complete the correction. Custom permissions

20. In the new window, look for System in the user list at the top. If it does not exist, click Add. Type System and click OK. Select System from the list of users in the window. In the lower half of the window, check the Allow column next to Local Launch and Local Activation. You can also see Local Access instead, just make sure there is a check mark for this item in the Allow column. Click ok. Repeat the steps for the other two items, Access permissions and Configuration permissions.

21. Repeat steps [numbered] for other ClSID and AppID values ​​listed in event logs.

22. A reboot is required after performing the steps above for the changes to take effect.

Although this may seem like a long and exhausting way to solve the problem, is the one that has been reported to work for the vast majority of users who have this problem. Follow it carefully step by step, and the DCOM error will go away in no time.

Method 2: delete registry keys

Some conflicting registry keys can also cause this problem. Registry keys are a form of binary instructions that the system must follow. There are some registry keys present in your registry that, although they belong to Microsoft's own subcategory, known to cause problems. Deleting these keys may solve the problem in question.

Warning: Changing the system registry requires technical knowledge and, if it is done wrong, can damage the system beyond repair, so proceed at your own risk. What's more, don't forget to create a backup of your registry if you are going to make changes to it.

1. Click on the Windows button and in the search box, type registry editor. Now, in the displayed results, right-click on the Registry Editor and click on »Run as administrator«. Open Registry Editor as administrator

2. Navigate to the next key:

   HKEY_LOCAL_MACHINENSOFTWARENMicrosoftNOle

3. Now delete the following keys

   1. DefaultAccessPermission
   2. Launch permission by default
   3. Restriction of access to the machine
   4. MachineLaunchRestriction

4. Save changes and reboot your system.

5. After deleting the above registry keys, the default permissions for the system will be written. As a result, applications that require access to the DCOM server will have access to it.

SUGGESTION: If none of the methods have solved your problem, we recommend that you use the Reimage repair tool, which can scan repositories to replace damaged and lost files. This works in most cases, when the problem originates due to a system corruption. Reimage will also optimize your system for maximum performance. You can download Reimage for By clicking here