Local Activation permission for the COM Server application runtime broker

Question

_{Tuesday, October 13, 2015 9:31 AM}

Hi, 

When starting up it shows 'your pc ran into a problem and restarting...' msg

I recently upgraded to win 10 and I get this error.

In the event logs I can see this error:

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\LOCAL SERVICE SID (S-1-5-19) 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.

error details:

Can you please help me.

Regards

Dahasak

All replies (2)

_{Wednesday, October 14, 2015 6:21 AM ✅Answered}

Hi,

Try this:

1. Right click Start button, select Run -> Type -> dcomcnfg, expand Component Services -> Computers -> My Computer -> DCOM Config.

2. Click View -> Detail -> Now you will get Application Name and Application ID in right side.

3. Scroll down and find the application ID -> Right Click -> Properties and select the Security tab.

For your issue, it's {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}. We could see it's below:

4. Click Customize under "Launch & Activation Permission" -> click Edit -> Add in the account user

user NT AUTHORITY\LOCAL SERVICE and set local launch and local activation.

5. Restart the application Service linked to this Application ID or restart the server and monitor.

More information, please refer to this article:

https://support.microsoft.com/en-us/kb/899965

Note: It's also applied to Windows 10.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

_{Sunday, February 14, 2016 4:16 AM}

Here is a fix that works for Windows 10 and other previous versions.

Fix for Distributed COM RuntimeBroker (Error ID: 10016):

Because DCOM RuntimeBroker in Component Services won’t let you edit the security settings, you need to right click on the task bar Windows icon, click Run and type in regedit, and then press Enter. Do the instructions 1-4 below for each of these registry keys:

HKEY_CLASSES_ROOT\AppID\9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

HKEY_CLASSES_ROOT\AppID\RuntimeBroker.exe

.

1. Go to each key and back it up by doing a right click on the registry key and click Export and save the file to a documents folder (you should always backup any registry key you change). Now right click on the registry key again and click Permissions > Advanced.

2. If Administrators has Full Privileges, then go to the next registry key and start with instruction #1 again. Otherwise change ownership to Administrators by clicking Change at the top where is says Owner then click Advanced > Find Now > Administrators > OK > OK > Apply > Yes.  If a message(s) comes up just click OK or Yes until back to the Permissions window.

3. Click on Administrators and check off Full Control then click OK.

4. Check "Replace all child objects...." and then Apply.  If a message(s) comes up just click OK or Yes until back to the Permissions window.  Then click OK to close the Permissions window.

5. When done with both registry keys, reboot.

6. Go to Control Panel > Administrative Tools > Component Services > Computers (middle window)> My Computer > DCOM Config and then right click on RuntimeBroker and click Properties >  Security.  You’ll see 3 edit buttons.

7. Make sure Customize is checked and then click on the top Edit under Launch and Activation Permissions and you may see this:
   
   If you see it click Cancel.

8. In the Group or user names box highlight each and make sure that Local Launch and Local Activation are checked.  Make sure that you have in the Group or User Names window: All Applications Packages, Self, System, Administrators, and Interactive. If any are missing, then click Add > Advanced > Find Now > [Name]> OK > OK, and make sure that Local Launch and Local Activation are checked.

9. Now click the middle Edit under Access Permissions (make sure Customize is checked off) then in the Group or user names box highlight each and make sure that Local Access is checked off.  When done click OK. Make sure that you have in the Group or User Names window: All Applications Packages, Self, System, Administrators, Local Network, and Network Service. If any are missing, then click Add > Advanced > Find Now > [Name]> OK > OK, and make sure that Local Access is checked off.

10. Click the bottom Edit under Configuration Parameters (make sure Customize is checked off) then click Advanced. Each Principal should have Read Access except for Administrators, and TrustedInstaller who should have Full.  If you need to make any changes, highlight the one to change then click Edit, make any changes, and then click OK.   You should have the following principals listed: All Applications Packages, System, Administrators, Users, and TrustedInstaller. If any are missing then click Add > Advanced > Find Now > [Name]> OK > OK (make sure that Read is checked). Then click OK until all the Properties windows are closed. Now close up the Component Services window.

11. Now go back to the regedit window and change ownership to SYSTEM on the same four keys previously changed. Do this by clicking Change at the top where is says Owner then click Advanced > Find Now > SYSTEM > OK > OK > Apply > Yes. If a message(s) comes up just click OK or Yes until back to the Permissions window and then click OK > OK.

12. When done changing the owner to SYSTEM on both registry keys like you did in #2 then close up regedit.

13. Best to reboot at this point and then you are done.