Windows 10 Error ID 10016

JamieKavanagh

Commendable
Apr 19, 2016
318
0
1,780
0

Windows 10 error ID 10016 is a notorious error that has been around since at least Windows 8. It is flagged when an application tries to start the DCOM server when it doesn’t have the permission to do so. While not a showstopper, the error can clog up Event Viewer with hundreds of instances. So if you want to fix Windows 10 error ID 10016 and clean up your Event Viewer, here’s how.

You usually only see error 10016 on a computer upgraded to Windows 10 and not on clean installs. It seems to be an inherited setting that the installer doesn’t overwrite.

As mentioned, as far as I can tell error 1016 doesn’t impact the working of Windows 10 aside from filling up Event Viewer. However, it’s always nice to have as few errors as possible so real ones show up much clearer.

Fix Windows 10 error ID 10016
Before undertaking this fix, take a copy of your registry just in case. You will also need to be logged in with administrative access or with the administrator account to make this work.

1. Type or paste ‘regedit’ into the Search Windows box.
2. Navigate to ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole’.
3. Delete these four keys if they appear, DefaultAccessPermission, DefaultLaunchPermission, MachineAccessRestriction, MachineLaunchRestriction.
4. Reboot your computer.

Deleting those four keys will cause DCOM to write default permissions for the system and should grant access to the apps requiring access to the DCOM Server.

More Windows 10 tips you might like:
How to get into advanced startup options in Windows 10
Quick guide to optimizing Windows 10
How to Optimize boot performance of Windows 10



 
Jul 9, 2018
1
0
10
0
This may be a late posting but there's a Microsoft article regarding this event ID.

https://support.microsoft.com/en-ca/help/4022522/dcom-event-id-10016-is-logged-in-windows-10-windows-server

Cause
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.
 

Similar threads


ASK THE COMMUNITY