Error - Event ID: 10016; DistributedCOM

Andrea Vironda 816 Reputation points
2021-06-16T18:48:07.473+00:00

Hi,
i'm receiving this warning among System Windows logs:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user ANDREA_HOME\Andrea SID (S-1-5-21-3426705931-1929522426-4205465823-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

I just followed the points presented in this answer.

but they didn't solve my problem. How can I go further in the investigation?

Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,903 questions
0 comments No comments
{count} votes

Accepted answer
  1. Kapil Arya 7,596 Reputation points MVP
    2021-06-17T07:26:36.447+00:00

    Hello,

    From https://learn.microsoft.com/en-US/troubleshoot/windows-client/application-management/event-10016-logged-when-accessing-dcom, Microsoft says:

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

    If you still like to fix, refer this guide:

    https://www.kapilarya.com/fix-event-10016-error-the-application-specific-permission-settings-do-not-grant-local-activation-permission-in-windows-10

    Hope this helps!

    Note: Included link in this reply refers to blog post by a trusted Microsoft MVP.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Vicky Wang 2,646 Reputation points
    2021-06-17T08:24:35.727+00:00
    1. Open Regedit
    2. Go to HKEY_Classes_Root\CLSID{C2F03A33-21F5-47FA-B4BB-156362A2F239}
    3. Right click on it then select permissions
    4. Click Advance and change the owner to Administrators group. Also click the box that will appear below the owner line. ("Replace owner ...")
    5. Apply full control
    6. Go to HKEY_LocalMachine\Software\Classes\AppID{316CDED5-E4AE-4B15-9113-7055D84DCC97}
    7. Right click on it then select permission
    8. Click Advance and change the owner to Administrators group
    9. Click the box that will appear below the owner line
    10. Click Apply and grant full control to the Administrators group
    11. Go to Administrative tools
    12. Open component services
    13. Click Computer, click my computer, then click DCOM
    14. Look for the corresponding service that appears on the error viewer [Immersive Shell]
    15. Right click on it then click properties
    16. Click security tab then click Add User. Add Local Service then apply
    17. Tick the Activate local box
    2 people found this answer helpful.

  2. Vicky Wang 2,646 Reputation points
    2021-06-21T08:19:07.583+00:00

    Hi,
    I am glad to hear that your issue was successfully resolved. If there is anything else we can do for you, please feel free to post in the forum.
    Best Regards,
    Vicky

    0 comments No comments

  3. maxmarutti#Talos 81 Reputation points
    2022-03-06T03:52:31.347+00:00

    Dear @Kapil Arya even 7000+ logs ?

    My original Microsoft Comunity post with the same issue

    I have found used MSC file extension eventvwr.msc Event Viewer many sys issues today. Event Viewer administrative logs, 7281 events over the course of 45 days

    7281 events with ID 10016 : Source ="Microsoft-Windows-DistributedCOM" WIRED!

    I thought it might be an error of eventvwr.msc so I did System Restore to the latest restore point, then Run SFC ( System File Checker ) to restore the corrupt or missing eventvwr.msc file just in case - no issues.

    The initial log date indicates that it was shortly after the exchange of MOBO's

    King regards
    max 'A Dime a Dozen'
    iwillfind_him

    0f410c81-b0ed-453c-9801-bff50b9c0376
    abd0d464-bc6a-46c3-9e71-557bfd2aeccc

    0 comments No comments