Windows 10: Why Certain DCOM 10016 Events Don't Matter

  1.    1 Week Ago #1

    Why Certain DCOM 10016 Events Don't Matter

    Here at we get lots of questions about Event ID 10016, which shows up in Event Viewer on nearly all Windows 10 PCs (and in modern Server versions as well, as it turns out). People who post these questions may even be irritated or upset. Usually, they want to make those events go away, and absent themselves from the Event log.

    Thanks to some excellent sleuthing work from long-time member @f14tomcat, I can cite a Microsoft Support Note to explain that these events are perfectly normal. In fact, they do not need to be fixed, removed, or otherwise mitigated. The title of the note is "DCOM event ID 10016 is logged in Windows." As I write this post, the note reports it was last updated on April 30, 2018. It also reports that it applies to the following Windows versions:

    Windows Server version 1803, Windows 10 version 1803, Windows 10 version 1709, Windows 10 Version 1703, Windows 10 Version 1607, Windows Server 2016 Standard, Windows Server 2016 Datacenter, Windows Server 2016 Standard edition Nano Server installation option, Windows Server 2016 Datacenter edition Nano Server installation option, and Windows Server 2016 Essentials
    How can I assert that certain DCOM 10016 events don't matter? Because the note makes it clear that any such events that mention "application-specific settings do not grant Local Activation permission" are normal for the afore-cited Windows versions. Here's the meaty part of the Support Note that explains things completely:

    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.

    These events can be safely ignored because they do not adversely affect functionality and are by design. This is the recommended action for these events.

    What if I MUST Silence These Events Anyway?
    Some Windows 10 users won't like or care about this explanation. They simply won't settle for anything less than a clean Event Viewer on their PCs.

    For such folks, the note provides instructions on how to suppress those events in the Event Viewer "by creating a filter and manually editing the filter's XML query." Please consult the Note for detailed instructions. Please also be aware that if you choose to silence these events, you won't be informed if a real, noteworthy DCOM event occurs on your system. If you search these Forums, you can also find other ways to handle these events, too. These include editing the registry to suppress DCOM events completely (subject to the same observation about cutting oneself off from information about real errors), and changing permissions to grant the necessary system components the ability to alter DCOM component data (this is the safest way to prevent those events from recurring, but must be repeated for each feature upgrade that comes along).

    For the rest of us -- including me -- we can safely and completely ignore those events. They do not indicate problems or trouble, and occur by deliberate design.


    Last edited by EdTittel; 1 Week Ago at 09:53.
      My ComputersSystem Spec

  2. Posts : 73
    Windows 10 Home, 64-bit, Version 1803 (OS Build: 17134.48)
       1 Week Ago #2

    Why Certain DCOM 10016 Events Don't Matter

    Great ! !

    Ed and f14tomcat, thanks for that. . .
      My ComputerSystem Spec

  3.    1 Week Ago #3

    Yes, I had an "Aha!" moment as soon as I saw the MS Support Note on the topic. That's why I volunteered to write this up as a 'sticky post' for this forum. Glad you found it useful/informative.
    Best wishes,
      My ComputersSystem Spec

  4. Posts : 33,061
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       1 Week Ago #4

    KCR said: View Post
    Great ! !

    Ed and f14tomcat, thanks for that. . .
    You're most welcome! Hope it helps a bit.
      My ComputersSystem Spec


Related Threads
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL...
I have been seeing the following even in my laptop's System log for quite some time. (Months.) The error says essentially: The user CALM1\BobTB, does not have Local Activation permission to the DCom app named RuntimeBroker. The...
Before the update i had 0 of these errors now with 1709 i get them daily and everytime on boot up aswell (the keys change from day to day tho) So is this a critical error and does it need to be fixed? Or is it a mess by microsoft and just...
Cortana and DCOM Error Event 10016 in Performance & Maintenance
My PC was giving many DCOM error 10016 involving Cortana as follows: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID...
Solved DCOM error 10016 in Performance & Maintenance
I'm told this is a rather common error after upgrading from Windows 7 to Windows 10, but I have read many posts and suggested solutions, but I still get the error in the System Event Log when starting up. I suppose I could ignore it, as there does...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:30.
Find Us