如果事件查看器^{(Event Viewer)}显示错误消息The application-specific permission settings do not grant Local Activation permission for the COM Server application，那么本文将对您有所帮助。它带有一个DCOM Event ID 10016，这个错误主要出现在升级操作系统之后。尽管此错误不会影响普通Windows 10用户的用户体验，但你们中的一些人可能想知道为什么会发生这种情况以及您可以采取哪些措施。

当Microsoft^(Microsoft)组件在没有所需权限的情况下尝试访问DCOM组件时，会记录这些 10016 事件。这些事件通常可以安全地忽略，因为它们不会对功能产生不利影响并且是设计使然。

整个错误消息看起来像这样 -

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} 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.

供您参考，您的计算机上的CLSID和APPID可能不同，因为它们代表您计算机上的组件服务。关于解决方案，错误消息中已经提到。您需要通过Windows 10中的管理工具修改安全权限。

特定于应用程序的权限设置不授予本地激活

要修复Windows 10^{(Windows 10)}中特定于应用程序的权限设置不授予本地激活^(Activation)错误，请按照下列步骤操作 -

1. 识别^(Identify)并确认CLSID和APPID
2. ^(Change)从注册表编辑器^{(Registry Editor)}更改CLSID键的所有权
3. ^(Modify)从组件^(Component) 服务^(Services)修改安全权限

请继续阅读以了解详细步骤。

您需要识别CLSID和APPID。由于它们在您的计算机上可能不同，因此识别它们非常重要。否则，您将无法摆脱此事件查看器^{(Event Viewer)}错误消息。根据上述错误信息，CLSID为{C2F03A33-21F5-47FA-B4BB-156362A2F239}，APPID为{316CDED5-E4AE-4B15-9113-7055D84DCC97}。还有一项称为SID，但此时不需要。

现在您需要找到造成问题的组件。为此，请在您的计算机上打开注册表编辑器。为此，请按Win+R，键入regedit，然后按Enter按钮。之后，导航到此路径-

HKEY_Classes_Root\CLSID\<Enter-your-CLSID>

不要忘记将Enter-your-ClSID替换为您在错误消息中获得的原始CLSID 。得到它后，你应该在你的右手边找到APPID 。确保此APPID和以前的APPID（在错误消息中提到）相同。确认后，右键单击左侧的CLSID ，然后选择^(CLSID)权限^{(Permissions)}选项。

然后，单击高级^{(Advanced )}按钮。

默认情况下，此密钥由TrustedInstaller拥有，但您需要将所有者更改为Administrator。为此，请单击“高级安全设置”窗口中的“^{(Advanced Security Settings )}更改”^{(Change )}按钮> 记下“管理员”> 单击“检查名称^{(Check Names )}”按钮 > 单击“确定^{(OK )}”按钮。

此外，您需要选中替换子容器和对象的所有者^{(Replace owner on subcontainers and objects )}复选框。

之后，从组或用户名^{(Group or user names )}列表中选择管理员，然后勾选^{(Administrators )}Allow/Full Control 复选框。现在保存您的设置。

此外，您需要检查默认 - 数据^{(Default – Data )}名称。在此示例中，默认数据^{(Default Data)}名称为Immersive Shell。如果您的错误消息中的CLSID和APPID不同，则应该不同。

之后，您还需要拥有APPID的所有权。为此，请在注册表编辑^{(Registry Editor-)}器中导航到此路径-

HKEY_Local_Machine\Software\Classes\AppID\your-APPID

您需要执行与上述相同的操作来更改该注册表^(Registry)项的所有权。

如果您在更改注册表项的所有权时^{(ownership of the Registry key)}遇到任何问题，您可以查看我们名为RegOwnit的免费工具，只需单击一下即可完成。

如果您完成了这些步骤，您需要打开Component Services。您可以在任务栏^(Taskbar)搜索框中搜索它，然后单击相应的结果。打开Component Services后，转到这里-

Component Services > Computer > My Computer > DCOM Config > Immersive Shell

基于此示例，CLSID与此Immersive Shell组件服务匹配。您需要找到从注册表编辑器获得的^{(Registry Editor)}默认 - 数据^{(Default – Data )}名称。识别后，右键点击组件服务，选择属性^(Properties)。在这里您应该可以找到可以再次确认的应用程序 ID^{(Application ID )}或APPID 。

接下来，转到“安全^{(Security )}”选项卡。在这里您可以找到三个标签，包括Launch 和 Activation Permissions^{(Launch and Activation Permissions)}。单击相应的编辑^{(Edit )}按钮。

如果您收到任何警告消息，请单击“取消^{(Cancel )}”按钮并继续。您需要按照与上述相同的步骤添加两个帐户-

• 系统
• 本地服务

添加它们后，一次选择一个，并授予它们两个本地启动^{(Local Launch )}和本地激活^{(Local Activation )}权限。

保存更改，您将不会在事件查看器^{(Event Viewer)}中再次遇到相同的问题。

无论您遇到 RuntimeBroker 或 Immersive Shell 还是任何其他进程的问题，解决方案都是相同的。^{(Whether you get the issue with RuntimeBroker or Immersive Shell or any other process, the solution is the same for all of them.)}

The application-specific permission settings do not grant Local Activation

If the Event Viewer displаys an error message The application-specific permission settings do not grant Local Activation permission for the COM Server application, then this article will help you. It comes with a DCOM Event ID 10016, and this error appears mainly after upgrading the operating system. Although this error doesn’t affect the user experience of the regular Windows 10 user, some of you might want to know why this happens and what you can do about it.

These 10016 events are recorded when Microsoft components try to access DCOM components without the required permissions. These events can usually be safely ignored because they do not adversely affect the functionality and are by design.

The whole error message looks like this-

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} 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.

For your information, the CLSID and APPID can be different on your computer as they represent a component service on your computer. Regarding the solution, it is already mentioned in the error message. You need to modify the security permission from an administrative tool in Windows 10.

The application-specific permission settings do not grant Local Activation

To fix The application-specific permission settings do not grant Local Activation error in Windows 10, follow these steps-

1. Identify and confirm CLSID and APPID
2. Change ownership of CLSID key from Registry Editor
3. Modify security permission from Component Services

Read on to know the steps in detail.

You need to identify the CLSID and APPID. As they can be different on your computer, this is very important to recognize them. Otherwise, you won’t be able to get rid of this Event Viewer error message. According to the above-mentioned error message, the CLSID is {C2F03A33-21F5-47FA-B4BB-156362A2F239} and the APPID is {316CDED5-E4AE-4B15-9113-7055D84DCC97}. There is another item called SID, but that is not necessary at this moment.

Now you need to find the component that is creating the issue. For that, open up the Registry Editor on your computer. To do so, press Win+R, type regedit, and the Enter button. After that, navigate to this path-

HKEY_Classes_Root\CLSID\<Enter-your-CLSID>

Do not forget to replace the Enter-your-ClSID with the original CLSID that you got in the error message. After getting it, you should find the APPID on your right-hand side. Make sure this APPID and the previous APPID (that is mentioned in the error message) are the same. After confirming, right-click on the CLSID on your left-hand side, and select the Permissions option.

Then, click the Advanced button.

By default, this key is owned by TrustedInstaller, but you need to change the owner to the Administrator. For that, click the Change button in the Advanced Security Settings window > write down “Administrator” > click the Check Names button > click the OK button.

Also, you need to select the Replace owner on subcontainers and objects check-box.

After doing that, select Administrators from the Group or user names list, and make a tick in the Allow/Full Control checkbox. Now save your settings.

Also, you need to check the Default – Data name. In this example, the Default Data name is Immersive Shell. It should be different if the CLSID and APPID are different in your error message.

After that, you need to take ownership of the APPID, as well. For that, navigate to this path in the Registry Editor-

HKEY_Local_Machine\Software\Classes\AppID\your-APPID

You need to do the same as above to change the ownership of that Registry key.

In case you are facing any problem changing the ownership of the Registry key, you can check out our free tool called RegOwnit that lets you do it with a click.

If you are done with these steps, you need to open the Component Services. You can search for it in the Taskbar search box and click the corresponding result. After opening Component Services, go here-

Component Services > Computer > My Computer > DCOM Config > Immersive Shell

Based on this example, the CLSID matches with this Immersive Shell component service. You need to find the Default – Data name that you got from the Registry Editor. After recognizing, right-click on the component service, and select Properties. Here you should find the Application ID or APPID that you can confirm again.

Next, go to the Security tab. Here you can find three labels, including Launch and Activation Permissions. Click the corresponding Edit button.

If you get any warning message, click the Cancel button and go ahead. You need to follow the same steps as above to add two accounts-

• SYSTEM
• LOCAL SERVICE

After adding them, select one at a time, and give Local Launch and Local Activation permissions to both of them.

Save the changes, you won’t get the same issue in the Event Viewer again.

Whether you get the issue with RuntimeBroker or Immersive Shell or any other process, the solution is the same for all of them.

Related posts

• 如何检查在Windows 10的Shutdown and Startup Log

• 如何详细介绍Windows 10的Event Logs与Full Event Log View

• 在哪里找到以及如何在Windows 11/10中读取Windows Update log

• Windows 10中缺少的日志

• Event Log中的Windows 10丢失事件

• Event ID 219插入设备时; Driver WUDFRD无法加载

• 该PC无法升级到Windows 10由于Parity Storage空间

• Event ID 307和304在Windows 10设备上使用error code 0x801c001d

• Fix无法在Windows 10上加载SteamUI.dll错误

• 如何在Windows 11/10上修复Event ID 642 ESENT error

• Fix ShellExecuteEx失败;代码error 8235在Windows10

• SFC未能Repair and DISM演出error 0x800f081f在Windows 10

• Setup无法在Windows 10上创建新的system partition error

• Fix Logitech Setpoint Runtime error在Windows 10上

• Fix Bdeunlock.exe Bad image，System Error或不响应错误

• 如何更改Windows 10中的默认Event Log file位置

• Fix Smart Check通过，HP computer的错误错误

• Windows 10中的Fix ShellExecuteEx错误错误

• 如何修复Event ID 455 ESENT error在Windows 10

• 如何在Windows 10修复Disk Signature Collision problem