Scenario

Changing Launch and Activation rights in Component Services

You're trying to change the DCOM Launch and Activation rights in Component services, with the following steps

  1. Open the Component Services console (by hitting the Windows buttons and typing "Component Services")
  2. Expand Component Services
  3. Expand Computers
  4. Expand My Computer
  5. expand DCOM Config

  6. Right-click the DCOM service you need to change, choose {AppName} with {AppID}, and then click Properties. 

  7. Click the Security tab.

Issue

You might notice that the "Launch and Activation" Permissions are greyed out.

Solution

 Caution

Modify the registry at your own risk.

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method.

These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved.  

Find the AppID in the HKEY_CLASSES_ROOT of the registry

Run Regedit.exe and search for the {AppID} in "HKEY_CLASSES_ROOT\AppID\{AppID}" key.

 

Get permissions

Right-click on the {AppID} key and select Permissions... 

Error when Changing permissions

 

 Caution
NOTE: DO NOT modify/change any permissions for the TrustedInstaller account.

 

When you try to change the permissions, like Full control for the administrators, you'll get an error.

Error pop-up


Error message

Unable to save permission changes on {AppID}.
Access is denied.

Change ownership

Click the Advanced button in the Permissions window and select the Owner tab. You'll notice the Trusted Installer as owner. Click the Change link (next to the current owner) to select the applicable owner (e.g. Local Administrators group) and click Apply, then OK. 

Change permission

Under the Permissions window, select the local Administrators group and under Permissions for Administrators select Full Control and click Apply, then OK.

 

Try changing the component services again

  1. Close the component services console
  2. Open the console again
  3. Try changing the L&A permission again (first chapter)

See also