Share via


RuntimeBroker - Launch and Activation Permissions - ADD is greyed out

Question

Tuesday, October 8, 2019 6:37 PM

I've been getting a few annoying DistributedCOM warnings (Event ID 10016) in Event Viewer such as...

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-AI976VT\keith SID (S-1-5-21-902422483-3872304736-3775899550-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.

...and they often coincide with the Win10 OS crashing. I'm not sure the crash is related but there are no other Administrative Events in Event Viewer apart from these warnings so I tried to get rid of them. I edited the keys in the registry giving Administrators group and my personal windows user name Full Control permissions. Then I tried to access RunTime Broker following the procedure below.

Launch DCOMCNFG from command prompt running as Administrator.

Console Root > Component Services > Computers > My Computer > DCOM Config > Runtime Broker > Properties > Security > Launch and Activation Permissions > Edit

I get a popup "One or more of the permission entries attached to Registry Value has an unrecognized type and can not be displayed."

I clicked on OK

==> Unfortunately "Add..." is greyed out

So I'm stuck, cannot add Administrators group or my personal windows user name to the list.

Does anyone have a solution?

All replies (4)

Wednesday, October 9, 2019 4:02 AM

Give the app causing the error sufficient permissions

S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP


Wednesday, October 9, 2019 4:58 AM

Hello,

Regarding DCOM error 10016, from https://support.microsoft.com/en-in/help/4022522/dcom-event-id-10016-is-logged-in-windows-10-windows-server, Microsoft says:

"These events can be safely ignored because they do not adversely affect functionality and are by design. This is the recommend action for these events."

As far as crashes are concerned, try to perform clean boot and see if that helps:

https://support.microsoft.com/en-in/help/929135/how-to-perform-a-clean-boot-in-windows

Hope this helps!

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support [www.kapilarya.com]


Wednesday, October 9, 2019 5:56 AM

Hi,

Event ID 10016 is a permission issue, it shouldn't cause the os crash issue. These events can be safely ignored because they do not adversely affect functionality and are by design. This is the recommend action for these events.

Could you provide more information of the crash issue? 

To get rid of the event 10016, please try the following: 

1. Click Start -> Run -> Type -> dcomcnfg, expand Component Services -> Computers -> My Computer -> DCOM Config.
2. Click View -> Detail -> Now you will get Application Name and Application ID in right side.
3. Scroll down and find the application ID {15C20B67-12E7-4BB6-92BB-7AFF07997402} -> Right Click -> Properties and select the Security tab.
3. Click Customize under "Launch & Activation Permission" -> click Edit -> Add in the account NT AUTHORITY\SYSTEM and set local launch and local activation.
4. Restart the application Service linked to this Application ID or restart the server and monitor

More information of event 10016, please refer to: 

https://support.microsoft.com/en-us/help/4022522/dcom-event-id-10016-is-logged-in-windows-10-windows-server

Best regards,

Yilia 

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Monday, October 14, 2019 7:32 AM

Hi,

Is there anything I can do for you?

If you have any problems or concerns, please feel free to post here. 

Best regards,

Yilia

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].