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: Newest
  1. Anonymous
    2015-11-13T09:56:29+00:00

    I did the permissions thing, and the 10016 disappeared. 

    I run the troubleshooter, and didn't find any problems.

    But yesterday I had 38 such errors again, with the same "offender" RunTimeBroker.

    BTW; still experiencing problems with Cortana, as it stops working out of the blue, and I have to kill the task for it to reinitialize.

    [EDIT]

    It seemed to be a one off...

    But now, after applying the 1511 build (Nov. upgrade ) I get the same error again for RunTimeBroker.......

    The update has restored permissions....!!!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-11-13T06:59:44+00:00

    Just as an update, while the troubleshooter may fix a related problem that can possibly contribute to at least the frequency of this error, it's not the silver bullet. I think that's going to come in the form of an update to Windows, since there's absolutely no way that this is intended behavior.

    If you go through the trouble of giving it the permission that it asks for, it still happens. It even happens on a clean install of TH2!  You may not see the extreme frequency of the errors with a clean install, but it's the exact same error pertaining to the exact same thing (Cortana, aka the Immersive Shell).

    I'm working with support on this, and they've submitted it to the product team for review.

    Was this answer helpful?

    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2015-11-09T23:17:56+00:00

    @rseiler - thanks for post this. I followed the steps you outlined, the troubleshooter did, indeed, find and fix an issue. I'll go back and wipe the logs and see what accumulates in coming days.

    This makes me wonder if I should simply run ALL the troubleshooters and see what they come up with... Maybe they'll ID issues that I didn't know were there...

    Was this answer helpful?

    0 comments No comments