Event ID 10016 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Anonymous
2012-11-20T22:14:35+00:00

Lately I get this system error a lot now that I have upgraded to Windows 8 Pro is a DistributedCom Event ID 10016. Below is the error text:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{D63B10C5-BB46-4990-A94F-E40B9D520160}

and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Anybody have any idea why I'm getting this error?

Walt

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2013-12-22T16:53:28+00:00

Same thing here. Greyed out. Windows 8.1 seems to fill the Event viewer with far more errors than previous versions.

edit: OK, found out why it was greyed out. There are 2 reg keys you have to set permissions to before you go to the DCOM Configuration in Component services. The CLSID key and the APPID key.

From another forum, although it applies to a different app, same principle:

*1. Open Regedit.2. Go to HKEY_Classes_Root\CLSID\*CLSID*.Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {C2F03A33-21F5-47FA-B4BB-156362A2F239}.3. Right click on it then select permission.4. Click Advance and change the owner to administrators. Also click the box that will appear below the owner line.5. Apply full control.6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.Note: *AppID* is the ID that appears in your event viewer. In your case it's {316CDED5-E4AE-4B15-9113-7055D84DCC97}.7. Right click on it then select permission.8. Click Advance and change the owner to administrators.9. Click the box that will appear below the owner line.10. Click Apply and grant full control to Administrators.11. Close all tabs and go to Administrative tool.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.15. Right click on it then click properties.16. Click security tab then click Add User. Add SYSTEM then apply.17. Tick the Activate local box.So use the relevant keys here and the DCOM Config should give you access to the greyed out areas:*CLSID:

{D63B10C5-BB46-4990-A94F-E40B9D520160}

and APPID

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

Was this answer helpful?

500+ people found this answer helpful.
0 comments No comments

214 additional answers

Sort by: Oldest
  1. Anonymous
    2017-11-28T16:45:08+00:00

    That's an informational security message and nothing else, in general. Would you consider it a problem if you received reports that people can't access your documents on your computer?

    Now, if someone is a colleague and should have access, that's a different story.  Try and resolve the problem through the misbehaving application, if there is any at all, in other words. Did you notice that Cortana can't index your documents, in the search results, for example? File a Cortana bug report in that case.

    She's doing it quite well indexing mine. In fact, this is the first I've heard of the issue.

    This has nothing to do with viewing files or documents, but a denial of access to installed programs trying to access the data they need to complete their expected goal.  If you've accepted the event log errors as unavoidable, the current state of error reports will never stop.

    Amuzeini has the correct solution

    amuzeini replied on

    A:

    Same thing here. Greyed out. Windows 8.1 seems to fill the Event viewer with far more errors than previous versions.

    edit: OK, found out why it was greyed out. There are 2 reg keys you have to set permissions to before you go to the DCOM Configuration in Component services. The CLSID key and the APPID key.

    From another forum, although it applies to a different app, same principle:

    *1. Open Regedit.2. Go to HKEY_Classes_Root\CLSID\*CLSID*.Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {C2F03A33-21F5-47FA-B4BB-156362A2F239}.3. Right click on it then select permission.4. Click Advance and change the owner to administrators. Also click the box that will appear below the owner line.5. Apply full control.6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.Note: *AppID* is the ID that appears in your event viewer. In your case it's {316CDED5-E4AE-4B15-9113-7055D84DCC97}.7. Right click on it then select permission.8. Click Advance and change the owner to administrators.9. Click the box that will appear below the owner line.10. Click Apply and grant full control to Administrators.11. Close all tabs and go to Administrative tool.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.15. Right click on it then click properties.16. Click security tab then click Add User. Add SYSTEM then apply.17. Tick the Activate local box.So use the relevant keys here and the DCOM Config should give you access to the greyed out areas:*CLSID:

    {D63B10C5-BB46-4990-A94F-E40B9D520160}

    and APPID

    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-11-30T17:20:46+00:00

    These are the errors I have but they cannot be found in component services and there is no way to sort or search in this window. Please advise. Thank you.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-08T03:07:50+00:00

    Thanks, but still this error remains mysterious for some people.

    I've been in this thread for weeks, and I just found a solution that actually works for my Runtime Broker related problem, which was a Windows Store game ( Lara Croft Go) that suddenly stopped working after a big Win10 update.

    Like many non-specialist people, I'm here because when there's a problem that won't go, I go to the Event Viewer, and I tackle the most worrying messages, and I found the RunTime Broker Permissions problem.

    Anyway now my Windows Store game works again, and I wish to share the solution, that was indeed linked to a Runtime Broker issue, apparently.

    Abstract : new (?) Defender "Exploit Guard" Exploit Protection default setting for Runtime Broker caused Windows Store game to hang after the first screen (developers' logo)

    (I have other Windows Store apps, they were still working, only had the issue with this game (a paid app))

    [ General documentation about Exploit Protection : https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-exploit-guard/exploit-protection-exploit-guard?branch=wdeg ]

    If by chance anyone is also here, not for indexing issues nor for the actual original question, but has the same problem with a Windows Universal Platform app and Runtime Broker,

    • go to Defender Security Center
    • go to App and browser control
    • scroll down to Exploit Protection, click "settings"
    • switch tab (program settings)
    • scroll down to and click RunTime Broker, then "change"
    • here I found a setting in blue color : "Disable extension points" that I had not changed myself, the setting was "replace system settings : activate". Change that to "disable".

    I understand the security concerns, but after a restart, my windows store game works again.

    Then I tried to check in the Event Viewer if I indeed had had errors related to that game + Runtime Broker + Defender Exploit Guard's Exploit Protection, but found nothing. ( I followed this tutorial for a custom view of Exploit Protection events : https://docs.microsoft.com/en-us/windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection )

    I've yet to check if the warnings this thread deals with (permissions) are still here.

    I hope I'm not spamming this thread, I wish I knew where to post that fix, because many people certainly have that problem, and when I searched the problem thoroughly I found nothing.

    (someone please provide the location of a bug report (fix report) platform for windows store apps?)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-12-11T18:55:34+00:00

    I'll put it as clear as I can, although I'm sure people will still insist they know better:

    * These errors are safe to ignore.

    * If you don't know what you're doing then do nothing. The "fixes" suggested here will remove callback permissions and break things most probably. Try and fix your specific problem, like BasilReznor did.

    * If you do know what you're doing, then check a few pages back. I have provided the proper way to grant the required permissions.

    Was this answer helpful?

    0 comments No comments