Windows 10: The "Application Specific" permission settings do not give "Local Activation" permission to...

Hi all,


recently, my windows 2016 server with 2 SSD disks encountered problems after using recovery tool to do bare metal recover. I can launch windows normally. But some services failure. The error message is as follow:


The "Application Specific" permission settings do not give "Local Activation" permission to the user "NT AUTHORITY \ SYSTEM" (SID: S-1-5-18)
under the address "LocalHost (using LRPC)" COM server application with the CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and the APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
in the application container "Not available" (SID: Not available). Security privilege can be changed using the Component Services Administration Tool.

I found my disk number change after recovery images.

• original: disk 0 with volume c and disk 1 with volume d
• reboot: disk 1 with volume c and disk 0 with volume d

And I search many articles, the solution is that I should modify registry and reset DCOM permission. Does disk number or BIOS setting affect COM service permission? As I know, image recovery is disk level process. It's impossible to modify registry setting.

:)

 

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

 

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

 

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

@Dmitriy

Event Viewer Error Description:

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

{8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169}

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.

++++++++++++++++++++++++++++++++++++++++++

Goal: Add the missing Local Activation permissions to the missing user
System via Component Services tool

CLSID: {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}

APPID: {F72671A9-012C-4725-9D2F-2A4D32D65169}

User: SYSTEM

Application Name: {F72671A9-012C-4725-9D2F-2A4D32D65169}

Steps 3 – 11 are needed to change the current ownership of CLSID and APPID from System and TrustedInstaller respectively to Administrators and Administrators

• Open Regedit as Administrator
• Navigate to HKEY_CLASSES_ROOT > APPID > {F72671A9-012C-4725-9D2F-2A4D32D65169}
• Right-click on it and select "Permissions..."
• In the “Permissions for {F7267. . . “ dialog, click the "Advanced" button
• At the top, look for "Owner" and click the "Change" link near "TrustedInstaller" Note the current owner is “TrustedInstaller”
• In the Select User or Group dialog box type "Administrators" and click the "Check Names" link (it converts the name to the correct format)
• Select "Administrators" in the list and check the "Allow" checkbox for "Full Control"
• Click the “OK” button to return to the Regedit dialog
• Navigate to HKEY_CLASSES_ROOT > CLSID > {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
• Repeat steps 3 through 9 to change ownership of the CLSID from System to Administrators
• After completing the above steps you (as an Administrator) now have the ability to edit the permissions for these two keys
• Open Component Services (Start-search for, or run “dcomcnfg”)
• Browse to Console Root > Component Services > Computers > My Computer > DCOM Config
• Find "{F72671A9-012C-4725-9D2F-2A4D32D65169}" from the Application Name list – near the bottom, right-click on it and select "Properties"
• Navigate to the "Security" tab and click the "Edit" button in the "Launch and Activation Permissions" section. If the Edit button is grayed out, then review/redo steps 1 – 11.
• In the “Launch and Activation Permission” dialog add the missing user,
  System.
• Click the "Add" button
• Type in "SYSTEM", the User that does not have “Local Activation” permissions as per the Event ID 10016 Description from Event Viewer. Next click the "Check Names" button
• Click the "OK" button to return to the "Launch and Activation Permission" dialogue
• Select "SYSTEM" from the "Group or user names" list, and click to place a check in the "Local Activation"/"Allow" check box
• Click the "OK" button
• Back in the "Security" tab, click "OK", then close the Component Services tool
• Back in Regedit rework the previous steps to revert ownership of the APPID, {F72671A9-012C-4725-9D2F-2A4D32D65169} , to TrustedInstaller, and the CLSID, {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}, to System
• You will be required to type "NT SERVICE\TrustedInstaller" (without quotes) in the dialogue box mentioned above at step 6, and click the "OK" button
• Close all windows and exit Regedit
• Reboot

Many thanks to Marco83, csmdew, and fdegrove over in

this thread.