Share this article

This article is translated in

Improve this guide

DistributedCOM Event ID 10016: Use These 4 Ways to Fix it

DCOM server errors are common and they usually get fixed in the registry

6 min. read

Updated onJuly 23, 2024

updated onJuly 23, 2024

Share this article

This article is translated in

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Resolve multiple Windows PC issues and speed up your PC effortlessly with specialized software.

DistributedCOM Event ID 10016 error appears usually in the Event Log, and it doesn’t cause too much trouble.

If you don’t want to deal with it anymore, keep on reading to learn how to get rid of it for good.

What is the 10016 event ID?

This error appears in the Event Viewer when an application tries to access the DCOM server, but doesn’t have the necessary permissions. The error message is harmless according to Microsoft.

How do I fix error 10016?

How do I fix error 10016?

1. Delete the Registry keys

1. Press theWindowskey +Rto launch theRunconsole.

2.Typeregeditin the Run dialog boxand pressEnteror clickOK. The Registry Editor will open.

3.Navigate to the following section in the Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

  1. Delete the following keys:DefaultAccessPermission,DefaultLaunchPermission,MachineAccessRestriction, andMachineLaunchRestriction.

  2. Finally, you can save the changes by restarting your PC.

The recommended way to fix theDistributedCOM error 10016 is to make a few changes to your Registry.Thedefault permissions will be written for the system if you delete the above-mentioned four keys from your registry.

Hence those apps that require access to the DCOM Server will eventually get access as a result.

2. Use third-party software to fix this error

A lot of Windows errors are pretty hard to pinpoint and the DistributedCOM 10016 error is definitely one of them.

As you can see, we have some excellent solutions here but if editing the Registry is not your thing, you can try using adedicated repair solutionthat will fix the problem automatically.

3. Add a custom filter to Event Log

This is an official solution from Microsoft and it hides these events from your Event Viewer.

4. Enable sufficient permissions

After that, you need to make a few changes to Component Services.

Finally, you will find some otherClSIDandAppIDvalues. Repeat the following steps for all of those values that have been listed in the event logs.The changes will take effect after you restart your system at the end.

Can Event ID 10016 cause a crash?

According toMicrosoft’s documentation, this is just a standard event log, and it can’t cause crashes or other problems, and in most cases, it should be ignored.

These events can be safely ignored because they don’t adversely affect functionality and are by design. It’s the recommend action for these events.

Event ID 10016 is a harmless event that can appear in Event Viewer and in most cases it should be ignored. But if you don’t want to deal with it, you can always use our methods to get rid of it.

To learn more about similar errors, check our guides onEvent ID 1000andEvent ID 10010.

Leave us a note if you managed to fix the problem using our solutions. Also, feel free to share with us if you have any quick workaround for the error.

More about the topics:Event Viewer,windows 10 errors

Milan Stanojevic

Windows Toubleshooting Expert

Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he spends most of his time learning about computers and technology.

Before joining WindowsReport, he worked as a front-end web developer. Now, he’s one of the Troubleshooting experts in our worldwide team, specializing in Windows errors & software issues.

User forum

1 messages

Sort by:LatestOldestMost Votes

Comment*

Name*

Email*

Commenting as.Not you?

Save information for future comments

Comment

Δ

Milan Stanojevic

Windows Toubleshooting Expert

Before joining WindowsReport, he worked as a front-end web developer. Now, he’s specialized in Windows errors & software issues.