Windows 10: Fixing "The application-specific permission settings do not grant Local Launch permission...

I've had a few crashes in the past days while gaming where my computer will completely freeze and the last seconds of audio will repeat until a forced restart. I've checked the event logs and when they log the error it's been this. See full text of the error below. Any help to isolate the issue and fix would be massively helpful.



Log Name: System

Source: Microsoft-Windows-DistributedCOM

Date: 19/03/2019 15:26:55

Event ID: 10016

Task Category: None

Level: Error

Keywords: Classic

User: DESKTOP-J6M7CG7\Conor

Computer: DESKTOP-J6M7CG7

Description:

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

Windows.SecurityCenter.WscCloudBackupProvider

and APPID

Unavailable

to the user DESKTOP-J6M7CG7\Conor SID (S-1-5-21-733465904-4135507663-537429890-1001) 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.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

<EventID Qualifiers="0">10016</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime="2019-03-19T15:26:55.577287500Z" />

<EventRecordID>8087</EventRecordID>

<Correlation />

<Execution ProcessID="408" ThreadID="7180" />

<Channel>System</Channel>

<Computer>DESKTOP-J6M7CG7</Computer>

<Security UserID="S-1-5-21-733465904-4135507663-537429890-1001" />

</System>

<EventData>

<Data Name="param1">application-specific</Data>

<Data Name="param2">Local</Data>

<Data Name="param3">Launch</Data>

<Data Name="param4">Windows.SecurityCenter.WscCloudBackupProvider</Data>

<Data Name="param5">Unavailable</Data>

<Data Name="param6">DESKTOP-J6M7CG7</Data>

<Data Name="param7">Conor</Data>

<Data Name="param8">S-1-5-21-733465904-4135507663-537429890-1001</Data>

<Data Name="param9">LocalHost (Using LRPC)</Data>

<Data Name="param10">Unavailable</Data>

<Data Name="param11">Unavailable</Data>

</EventData>

</Event>



Log Name: System

Source: Microsoft-Windows-DistributedCOM

Date: 19/03/2019 15:26:52

Event ID: 10016

Task Category: None

Level: Error

Keywords: Classic

User: DESKTOP-J6M7CG7\Conor

Computer: DESKTOP-J6M7CG7

Description:

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 DESKTOP-J6M7CG7\Conor SID (S-1-5-21-733465904-4135507663-537429890-1001) 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.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

<EventID Qualifiers="0">10016</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x8080000000000000</Keywords>

<TimeCreated SystemTime="2019-03-19T15:26:52.732100800Z" />

<EventRecordID>8086</EventRecordID>

<Correlation />

<Execution ProcessID="408" ThreadID="2012" />

<Channel>System</Channel>

<Computer>DESKTOP-J6M7CG7</Computer>

<Security UserID="S-1-5-21-733465904-4135507663-537429890-1001" />

</System>

<EventData>

<Data Name="param1">application-specific</Data>

<Data Name="param2">Local</Data>

<Data Name="param3">Activation</Data>

<Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>

<Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>

<Data Name="param6">DESKTOP-J6M7CG7</Data>

<Data Name="param7">Conor</Data>

<Data Name="param8">S-1-5-21-733465904-4135507663-537429890-1001</Data>

<Data Name="param9">LocalHost (Using LRPC)</Data>

<Data Name="param10">Unavailable</Data>

<Data Name="param11">Unavailable</Data>

</EventData>

</Event>

:)

 

The application-specific permission settings do not grant Local Activation permission for the COM Server application

Hello Rob,

Thank you for keeping us posted.

As per the description, I understand that you are experiencing issue with the application-specific permission settings do not grant Local Activation permission for the COM server application on the system.

I certainly understand your concern and will try my best to help you.

I really appreciate all your efforts in trying to fix the issue.

I would suggest you to refer to the suggestions provided by
“Amuzeini” replied on December 22, 2013 in the following Microsoft Community link.

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

Note:
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection,
back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:



How to back up and restore the registry in Windows

Also, I would suggest you to refer to the suggestions provided by
“SE. Mohammed” replied on June 2, 2013 in the following Microsoft Community link.

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

I would suggest you to refer to the suggestions provided by
“Cathy Kong” replied on May 12, 2010 in the following Microsoft Community link.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1}

I hope this information is helpful.

Please do let us know if you need any further assistance, we will be glad to assist you.

Thank you.

Jayant

 

Definitive guide how to fix errors "The application-specific permission settings do not grant Local Launch permission for the COM Server application"

Hello guys. While dealing with Windows errors I often see errors like this one:

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID


{05D1D5D8-18D1-4B83-85ED-A0F99D53C885}

and APPID

{AD65A69D-3831-40D7-9629-9B0B50A93843}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.


Most topics about such errors simply point you to DCOM Config to fix permissions, but in many cases all settings for failed component are grayed out so you can't change anything here. This guide is about how to fix it completely all at once regardless of
exact error message as this solution is universal.

So, if you've found what component settings are grayed out, this means what permissions for component's registry key restrict you from modifying it. We have to fix it first so we could fix DCOM configuration of component.

1) Launch Regedit as Administrator. Search key name with given CLSID (in this case it's
{05D1D5D8-18D1-4B83-85ED-A0F99D53C885}). Write down component's name from it's registry key, you will need it later.

2) Open permissions for this key and check them. In most cases you could see what both SYSTEM and Administrators haven't any permissions to change this key.

3) Enter advanced permissions and check the key owner. In most cases it's TrustedInstaller. Take ownership of this key by setting the owner to Administrators group. Also set "Replace owner on
subcontainer and objects" checkbox. Close all permissions settings and open them again.

4) Now grant full permissions over this key to SYSTEM and Administrators group. Also remove any unknown user accounts if some of them is on list. Replace permissions for subcontainers and objects of this key.

5) Now repeat same procedure for component's APPID key (in this case it's
{AD65A69D-3831-40D7-9629-9B0B50A93843})

Now back to DCOM Config. Launch it as Administrator. If you have troubles doing it, you could do it by simply launching cmd as Administrator and then entering "dcomcnfg". This will do the trick. Now:

6) Expand Component Services -> Computers -> My Computer -> DCOM Config.

7) Click View -> Detail -> now you will see both Application Name and Application ID in the list.

8) Find needed component using it's name which you've written down. Compare it's CLSID with yours as where could be many components with same name but different CLSID (it happens sometimes).

9) Right Click -> Properties and select the Security tab. All settings should be accessible for you to change them.

10) Now you need the box with permissions which has been mentioned in error message (in this case it's
Local Launch so we need a "Launch & Activation Permission" box). Click "Customize" there.

11) Check if user list contains needed account, mentioned in error message (in this case it's
NT AUTHORITY\SYSTEM). In most cases it's absent. Add it to list if so.

12) Now grant permissions mentioned in error message to this account (in this case it's
Local Launch). In most cases it's also worth to grant same type of activation permission. So in this case we will set both
Local Launch and Local Activation.

Problem solved.

 

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

another

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

{9E175B6D-F52A-11D8-B9A5-505054503030}

and APPID

{9E175B9C-F52A-11D8-B9A5-505054503030}

This is not in the DCOM Config