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

Anonymous

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

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

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}

0 comments

214 additional answers

Anonymous

2016-01-26T05:54:24+00:00

Of course.

I had to do a system restore just to get the thing to stay on :(.
Was this answer helpful?

0 comments No comments
Anonymous

2016-01-28T03:55:24+00:00

My worry is that the error is not as benign as you suggest. I started looking into the event log because Windows 10 keeps logging me into a "temporary profile" when restarting after a shutdown. So after ensuring that there are no viruses and no disk corruption, the logical place to start looking is for errors that occur right after restart. I've had several people now that I know look into their event logs on Windows 10, by the way, and they all have this garbage. Brand new W10 machines with almost nothing on them, "right out of the box." Apparently it's not a big priority at Microsoft.
Was this answer helpful?

0 comments No comments
Anonymous

2016-01-28T04:12:54+00:00

That infamous "temporary profile" problem dates back to at least Server 2003 though. You can remedy it with Method 1 here. There's no data loss, it goes back to the way it was.
Was this answer helpful?

0 comments No comments
Anonymous

2016-01-29T04:01:07+00:00

I appreciate your "Method 1" info but that is really to recover your account after you've been totally locked out. My interest is to not have the problem in the first place. A key phrase in the "Method 1" text is, "Windows might not read your user profile correctly, such as if your antivirus software is scanning your computer while you try to log on." So that is what leads me to believe that this may be related to the flurry of errors that Windows 10 generates upon reboot. The constant furious effort by Windows to restart failed services upon startup is possibly the kind of activity that would interfere with Windows being able to read your profile.

And you don't need any anti-virus software or anything else installed to get the flurry of system failures. Have anybody you know with a Windows 10 machine look in his/her Windows System event log and filter for just the errors. You'll find everyone has a ton of them. This is in part because Windows 10 (and Windows 8 and 8.1 apparently) comes right out of the box with at least two DCOM services that have insufficient permissions to start. One of them is "RuntimeBroker" and the other one has something to do with Cortana (I can't remember the specifics). Heaven help you if you turn on Cortana, by the way - that will be the start of a new series of headaches that I don't even want to discuss here.

The thread I referenced in my earlier post on this thread has some instructions for eliminating these service-permission problems (and the system errors they cause), but the procedures are very dangerous because they involve changing ownerships and permissions on crucial registry keys and on the services themselves. So you really need to know what you're doing and even then it's dangerous and parts of the instructions are vague so you have to improvise. I managed to eliminate the startup errors associated with "RuntimeBroker" and since then my machine has not logged me in with a temporary profile but I've only tried it a few times so there's nothing conclusive here.
Was this answer helpful?

0 comments No comments