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

I am using windows 10 how can I complete this. Nothing that I have tried allows me to change the properties. Access denied!!!!!!!!!!

Hello guys. I ve tried all of those steps You posted here but still i cant make "add" button working in "Launch and activation" settings. I ve seen that someone had this problem too so please advice. The issue is with runtimebroker.exe

I have put together a fix for this problem that goes step by step as some of the previous fixes can be confusing.

 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

HKEY_CLASSES_ROOT\CLSID{D63B10C5-BB46-4990-A94F-E40B9D520160}

HKEY_CLASSES_ROOT\CLSID{D63B10C5-BB46-4990-A94F-E40B9D520160}\LocalServer32

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 all 4 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 Permissionsand 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 Customizeis 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 all 4 registry keys like you did in #2 then close up regedit. 13. Best to reboot at this point and then you are done.

Do NOT use the above fix if you want Apps and Store to function properly. RuntimeBroker is not an Apple product, and can be found in a fresh install of Windows 10. I tried this fix three times; all three led to restoring my OS from backup.

I encountered issues as a result of this fix the first couple times I attempted to execute it. I also need to restore my O/S to a previous state as result of those first few attempts. However, on my third or fourth attempt, I seem to have got the fix implemented correctly. There were a few things I had to figure out by trial and error:

• the first two references to "Administrator" should be references to "Administrators" with an "s";
• be careful in locating the correct check box below the change owner selection; it is immediately below, not mid dialogue box;
• when adding users to the privileges screen, you may need to add users other than the ones listed in the fix instructions; for example, you may need to add System, Administrators, and possibly Users; I found that I had to add the Users group or the fix failed to work for accounts that didn't have admin privileges;
• lastly, I set ownership of the CLSID and the APPID back to TrustedInstaller after modifying the privileges; there are instructions elsewhere that show how to do this; the only trick is getting the TrustedInstaller user to reappear.

I executed the fix with the above listed details a few weeks ago. I haven't seen the error for this CLSID and APPID since executing the fix and I haven't noticed any issues. I don't seem to have any issues with Store or Apps despite implementing the fix. I do, however, still have similar DCOMM issues related to Cortana. In the case of the DComm errors related to Cortana, the error message says the APPID is unavailable or other similar indication. Thus, I'm not sure how to try to fix the Cortana related DCOMM errors (without knowing the APPID).

If anyone has suggestions how to address the DCOMM errors related to Cortana that don't identify the APPID, I am interested in those suggestions.