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

214 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-01-12T18:56:28+00:00

    I had the very same problem on Windows 10 x64 Pro.

    I followed the instructions above, but that did not help. By Trial and Error I found one additional step:

    18. In the properties of that service, also go to tab 'Identity'

    19. This was set to the first item 'Interactive User', I changed it to the second item 'User starting the service'

    This sees to to the trick for me.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-01-14T03:05:31+00:00

    I am experiencing the same issue repeatedly described in this post. In my case, the DCOM errors pertain to Cortana and, more frequently, to RunTimeBroker. I followed the process described in this post and the "fix" appeared to stop the error messages for my main account, which is a member of the Administrator's Group; however, the "fix" caused major problems with another account that is not a member of the Administrator's Group. The standard User account lost the ability to open the Edge browser (it closes itself immediately after opening), lost access to the Start menu, ran unbelievably slow, and exhibited other weird behaviour. Perhaps this is why another person posted that the fix rendered his system virtually unusable (including mentioning the inability to access the Start menu). This seems to indicate that the fix has a detrimental (i.e. devastating) effect on accounts that don't belong to the Administrator's group. The Event Log seemed to indicate that the standard User account could no longer start RunTimeBroker at all after the fix was applied:

    The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.

    I hope this issue has caught the attention of someone at Microsoft !

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-01-14T04:16:32+00:00

    I have no expertise in these solving issues like this. Nonetheless, from my unknowledgeable perspective, it appears that the documented "fix" transfers ownership of a service (e.g. RunTimeBroker) to the Administrator account or the Administrators Group (as the case may be). This seemed to solve the problem for accounts that are members of the Administrator's group; however, the "fix" proved problematic in situations where the Interactive User is not a member of the Administrator's Group, for example, when a standard user logs onto the computer.

    I read about the role of the Interactive User here: https://msdn.microsoft.com/en-us/library/windows/desktop/ms686587(v=vs.85).aspx

    However, the above linked explanation of the Interactive User role did not help me understand how I could safely go about fixing the issue for users that are not members of the Administrators Group.

    Perhaps someone wiser than me can further connect these ideas and formulate a universally robust solution?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-01-25T23:43:56+00:00

    When you changed the ownership, did you change it to "Administrators"? As in with an 's' at the end?

    Was this answer helpful?

    0 comments