Summary :
In this article, we will discuss the Event ID 11016 errors related to DistributedCOM in the Event Viewer. If you want to find some solutions to get rid of the error, this post is what you need. Now, you can continue to read this post from MiniTool.
Event ID 10016
Almost all Windows versions have found DistributedCOM Event ID 10016 on Windows Event Viewer. This error will not crash your system immediately and you will not die suddenly at a blue screen. The basic error message is the same — Application-specific permission settings do not grant local activation permissions for COM Server applications.
What Is DistributedCOM
What is DistributedCOM? It is the abbreviation of Distributed Component Object Model and it is also called DCOM. It is an integral part of Windows computer network communication. It is a Microsoft proprietary technology, and it will work immediately whenever an application is connected to the Internet. Traditional COM can only access information on the same computer, while DCOM can access data on a remote server.
When an application or service tries to use DCOM but does not have the appropriate permissions, Event ID 10016 error usually occurs. Now, let’s see how to fix Event ID 10016 Windows 10.
Fix 1: Use Registry Editor
First, you can try to fix the Event ID 10016 error with Registry Editor. But you had better back up the registry individuals in advance. Here is how to fix the issue:
Step 1: Open Registry Editor by typing Registry Editor in the search bar.
Step 2: Then, navigate to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole
Step 3: Then, delete the following four registry keys:
DefaultAccessPermissionDefaultLaunchPermissionMachineAccessRestrictionMachineLaunchRestriction
Step 4: Close Registry Editor and reboot your computer to check if the Event ID 10016 error has been fixed.
If not, try the next solution.
Fix 2: Modify the Permissions
Then, you can also try to fix the Event 10016 error by modifying the permissions. Follow the guide below:
Step 1: Open the RuntimeBroker properties window, click the Security tab.
Step 2: Then, click the Edit button under Launch and Activation Permissions. If it’s greyed out, the PowerShell script didn’t run properly.
Step 3: When you receive the warning message, you should click Yes.
Step 4: Then, click the Cancel button. Now you’ll see a list of default accounts and you might also see an Account Unknown listed.
Step 5: After that, click Add and type in System and then click Check Names. Next, click OK and it will add that account to the list.
Step 6: Click Add again and this time type in Local Service and follow the same steps.
Step 7: At last, select the Local Launch and Local Activation checkboxes under Allow.
Now, you can check if the Event ID 10016 error has gone. If not, continue to fix it.
Also see: What Is Runtime Broker and How to Fix Runtime Broker High CPU
Final Words
To sum up, this post has shown 2 ways to fix the Event ID 10016. If you come across the same error, try these solutions. If you have any better ideas to fix it, you can share them in the comment zone.
ABOUT THE AUTHOR
Position: Columnist
She was graduated from the major in English. She has been the MiniTool editor since she was graduated from university. She specializes in writing articles about backing up data & systems, cloning disks, and syncing files, etc. She is also good at writing articles about computer knowledge and computer issues. In daily life, she likes running and going to the amusement park with friends to play some exciting items.
Originally published at https://www.minitool.com on March 4, 2021.
