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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-12-24T00:28:19+00:00

    Here is the sad part I had zero errors in my event viewer until Microsoft released its

    Version 1809 Update that installed the 21st of December and prior to that no 10016

    Distributed COM errors

    The 21st the ''Quality'' updates installed :)

    Cumulative update for,NET Framework 3.5 and 4.7.2 for Windows 10 Version 1809 x64 (KB4470502)

    Feature update to Windows 10, version 1809

    And a Flash player 1809 version (KB4462930)

    I had a ''Critical'' error sandwiched between all these 10016 errors .

    The system has rebooted without cleanly shutting down first. This error could be caused if the

    system stopped responding, crashed, or lost power unexpectedly

    And that is why I am looking into this in the first place.

    There is nothing worse than your machine shutting down when you are in the middle of something.

    Shut down completely with no battery backup kick in nothing.

    That has never happened before.

    And it is not normal I had no errors like this prior to these updates

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-11-27T20:11:06+00:00

    neah not at all

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-11-27T17:41:06+00:00

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

    At least in a SERVER environment, do NOT regedit

    Hahaha I was right when I said this:

    "So I have this same error, but my question is, why are we even trying to fix this? Does anyone know what is actually broken or causing a problem? Or is the entire reason for this thread just to get rid of the error (in which case you'll probably break something else by "fixing" it).

    It seems like Windows is just getting more and more like Linux, i.e. every day you will see "errors" which are completely normal and meant to be ignored. There is no world in which you will be able to eradicate all Windows Server error messages in event viewer."

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-11-27T16:00:09+00:00

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

    At least in a SERVER environment, do NOT regedit

    Was this answer helpful?

    0 comments