top of page



Fix DCOM Event ID 10016 Error On Windows 10

The first thing we have to do is figure out which process or service is associated with the CLASS ID listed in the error. To do this, go ahead and copy the CLSID listed in the event description. In my case, it started with {D63B10C5. Make sure to copy both the curly braces also.

Fix DCOM Event ID 10016 error on Windows 10

By deleting four registry keys, you may be able to completely eliminate DistributedCOM error 10016 and other permission related DCOM errors. As stated earlier, please back up the registry before proceeding.

In most cases, you can ignore them if they're not adversely affecting your computer's performance. This is especially true with most 10016 errors, which is one of the most common. These don't usually indicate anything wrong with your computer outside of an app or site not accessing remote servers correctly.

If you're discovering an error in Event Viewer, it's easy to wonder why Windows didn't let you know about with a notification. Since these aren't serious errors that stop critical functions of Windows, you don't get an error. If you're actively trying to connect to a remote server via an app, the app might give you an error, though. You can then cross-reference with Event Viewer to get the event ID to further troubleshoot the error.

If you know you're having a DistributedCOM issue, but can't find it in Event Viewer when searching specifically for \"distributedcom,\" try searching for \"dcom\" instead. Certain errors are listed as \"DCOM\" while others use \"DistributedCOM.\" Some error source, but they're named differently based on different event IDs. Remember, you can also search by the event ID or error code number.

It's actually a good idea to glance through Event Viewer once a month or so just to see if you're having any regular DistributedCOM errors or warning events. These don't always mean something serious is wrong. For instance, I occasionally have login errors where a service didn't start correctly or within a set time frame. However, the service starts fine on the next reboot. As with most technology, there are random glitches. If the warning or error occurs all the time, it's worth researching it further to see if it's a sign of something more serious going on.

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.

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.

Such a complicated error might make inexperienced users throw up in frustration. They are unfamiliar with this terminology. Plus, troubleshooting DCOM errors is a pain so I ignored it at first but the event log was full of them as it occurred every hour or so. Determined to fix it, I decided to investigate.

Hi Folks!I am back today with another solution to a common problem. It seems every time Microsoft releases an update to Windows 10, Your event log is full of Event ID 10016 Errors. these errors range from issues with Windows Security Center, to general DCOM Errors involving Shell host.Now according to Microsoft, some of these DCOM Errors are by design and are harmless. To quote the recent Microsoft DCOM Event ID 10016 is logged in Event Viewer Knowledge Base article:These 10016 events are recorded when Microsoft components tries to access DCOM components without the required permissions. In this case, this is expected and by design. A coding pattern has been implemented where the code first tries to access the DCOM components with one set of parameters. If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it does not skip the first attempt is because there are scenarios where it can succeed. In those scenarios, that is preferable. However, to many people these errors are annoying and serve no purpose other than to clog your event log with a bunch of annoying error messages like seen below..The solution to Windows.SecurityCenter.WscBrokerManager, Windows.SecurityCenter.WscCloudBackupProvidor, and Windows.SecurityCenter.WscDataProtection DCOM 10016 errors has to do with the Windows Security Center Service and its by default delayed auto start.The problem with the security center service delayed auto start is Windows.SecurityCenter.WscBrokerManager,and Windows.SecurityCenter.WscCloudBackupProvidor tries to initiate very early in the boot up process, and this will cause it to fail and give those error messages. It will later retry after the Windows Security Center Service(wscsvc) has finally started up, and then succeed as normal.To fix this problem, you must change the delayed start value of wscsvc to start up sooner in the boot process so its not delayed by disabling the delayed start of the wscsvc service.You can not however change the startup value of the Windows Security Center Service via the Services application because you simply won't have permissions to do so. It can only be changed via the registry.To fix these errors, perform the following steps:1. type regedit in the Windows Search box and "Run it as administrator and click OK in the UAC prompt.2. Navigate to the following Registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc3. In the right-hand pane look for the DWORD Value named DelayedAutoStart4. Double click DelayedAutoStart and change the value from 1 to 05. Close the Registry Editor and restart your computer.6. Those DCOM Error messages with Event ID 10016 concerning Windows.SecurityCenter should no longer be present.As always, I hope this little articles helps folks out there wondering why they are getting these annoying errors.Merry Christmas Folks!Have a great New Year! Disclaimer: I am not responsible for anything that may happen to your PC when changing settings or changing registry values. If you choose to make changes, you do so at your own risk.. You are solely responsible for any damage to your computer , data, or other hardware due to user error, inadequate cooling, too high of voltages, incorrect software settings, and any other factors. Please remember to back up your computer before attempting this. If overclocking, Do not Overclock on the stock AMD or Intel CPU Heatsink and fans. Use Aftermarket cooling heat sinks of sufficient TDP or water cooling to ensure best chance of not having premature hardware failure. As always, remember to backup your data before attempting any change. I am not responsible for data loss or damage of any kind.

You install Microsoft Windows SharePoint Services 3.0. When you view the System log after Windows SharePoint Services 3.0 is successfully installed, you see event ID error 10016 or 10017 logged one or more times.

This issue occurs if the domain user account that you specified as the Windows SharePoint Services 3.0 service account does not have the Local Activation permission to the IIS Wamreg Admin Service. The event ID error messages 10016 or 10017 that are mentioned in the "Symptoms" section do not affect the functionality of Windows SharePoint Services 3.0.

You can safely ignore the event ID error messages 10017 or 10016 that are logged in the System log. If you want to prevent the event ID error messages from being logged in the System log, use the Component Services snap-in to enable the Local Activation permission to the IIS Wamreg Admin Service for the domain user account that you specified as the Windows SharePoint Services 3.0 service account. To do this, follow these steps:

Event ID 10016 DistributedCOM Windows 10 Error is one of the most notorious issues that users confront in the System log. This error triggers when certain processes do not contain permissions to the DCOM components that are mentioned in the event logs. It restricts the computer to run flawlessly which eventually annoys the users.

All the users irrespective of professional or semiprofessional as well as the beginners want their computers to be running smoothly without having any error. Unfortunately, this thing is not maintained always hence they go through some difficulties. It is hard on the part of a professional user to accept. Event ID 10016 DistributedCOM Windows 10 Error is such a troublesome thing which most of the users commonly face in their system probably every day.

While working with computer and applications, users will face different errors frequently. But all the problems come with a solution. Instructions elaborated above will help the users to fix Event ID 10016 DistributedCOM Windows 10 Error smoothly. Ensure that you read the steps properly and applied in the right places. Any mistake in the process will not dismiss the Event ID 10016 DistributedCOM Windows 10 Error rather it will be waste of time.

The Distributed Component Object Model (DCOM) is a protocol that enables software components to communicate directly over the network. DCOM is designed for use across multiple network transports, including Internet protocols such as HTTP.[1] A DCOM error 10016 means that a program tried to start the DCOM server by using its' infrastructure, but the user does not have the necessary permissions to do so.

The solution is two phased. Phase one is to allow the DCOM permissions of the blocking process to be modified. Phase two is to add the blocked account the permissions to launch the blocked process. The following instructions are based upon the error listed in this technical article, for user EDP\edpadmin3 being prevented from running the RuntimeBroker process. The APPID and USER in the customers DCOM error will vary within each customer environment.


bottom of page