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-11-24T01:45:45+00:00

    i get 'access denied' whenever i try to change the administrator's permission to full control.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-10-07T19:25:14+00:00

    I'm seeing this same error in my Event log.  What I'm trying to figure out is whether I should do anything about this or to just ignore it.  What are the problem(s) folks experiencing that they believe in elevating permission to some com objects that this is addressing.  I've not looked too deeply into this problem, but one replier suggested that the com object in question was the Runtime Broker.  My quick check on the internet suggests that the Runtime Broker is responsible for making sure that an app only uses services that it has explicitly declared it uses.  If that's true, granting elevated permissions might get rid of the error message, but it also might not be the right thing to do.  Whose to say that you're not opening the door for malicious software to do something it didn't have permissions to use and you just open the door to that kind of attack.  I didn't read every reply, to the original question, but all the many I looked at seemed focused on making sure the error is not logged in the future, without once specifying the problem that the fix addresses.  In my case, I was looking at the event log to see if I can find any events that might be related to a Bluetooth device not working be being reported as connected.  That's when I saw this event so I was tring to see if it might be related to the problem I wanted solved.  My guess is it's not, so I won't be doing any of the suggested solution since it not clear from any of the discussion what problem it fixes, if any.  What I'm suggesting is that under some situations, the logging of an error is the right thing, and no corrective action is required.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-09-14T16:32:32+00:00

    If your using a OEM installer for windows 10 what does this mean to you ?  I think you can use one OEM installed version with the one time key to activate windows on one machine right  ?  If you have a USB stick with the installation of windows that you can go use it on other machines but you would have to buy an actual activation key to activate it but you will need to have the other computers hooked up to the internet there with the different activation key ok !!!  I think also you cant use the same activation key from one computer installed of windows to use the same key to other computers is why you have to do what I said here to get another activation key for other computer systems then !!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-09-14T15:28:54+00:00

    Hi,

    I just posted a thread about a problem I having (stuck when trying to RDP to another Windows 10 machine):

    https://answers.microsoft.com/en-us/windows/forum/windows\_10-networking/help-suddenly-cannot-rdp-from-my-windows-10-pro/a3c25c92-bb80-477c-be2f-bcd5bdbc2b7b

    Does the script just above this fix this problem (BTW, this is the FIRST TIME I have encountered this problem)?

    Also if so do I run that script on ALL Windows 10 machines?

    Or, just the target Windows 10 machine?

    Or, on my RDP client Windows 10 machine?

    Thanks,

    Jim

    Was this answer helpful?

    0 comments