Windows 10: DistributedCOM permission settings Error 10016 -should I resolve this?

Inside W10's Event Viewer, I see an error with ID of 10016 (DistributedCOM). Its error description is -

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{ (long number) }
and APPID
{ (long number) }
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.

This error message says that I can modify security permission. As this topic is over my head, I don't know if I should do this or not. Thanks for any comments on this issue.

:)

 

Freezing issue

Go to: Windows 10 error 10016 from Run-time broker - cannot change permissions

for the DistributedCOM 10016 RuntimeBroker error mentioned in this thread.

 

DistributedCOM Error event ID 10016

I have this many so far today:

Error 10/02/2018 17:04:01 DistributedCOM 10016 None

Error 10/02/2018 17:04:01 DistributedCOM 10016 None

Error 10/02/2018 17:04:01 DistributedCOM 10016 None

Error 10/02/2018 17:04:01 DistributedCOM 10016 None

Error 10/02/2018 17:01:28 DistributedCOM 10016 None

Error 10/02/2018 17:00:57 DistributedCOM 10016 None

Error 10/02/2018 16:29:21 DistributedCOM 10016 None

Error 10/02/2018 16:29:21 DistributedCOM 10016 None

Error 10/02/2018 16:29:21 DistributedCOM 10016 None

Error 10/02/2018 16:29:21 DistributedCOM 10016 None

Error 10/02/2018 15:28:36 DistributedCOM 10016 None

Error 10/02/2018 15:28:13 DistributedCOM 10016 None

Error 10/02/2018 15:28:13 DistributedCOM 10016 None

Error 10/02/2018 15:28:13 DistributedCOM 10016 None

Error 10/02/2018 15:28:13 DistributedCOM 10016 None

Error 10/02/2018 13:48:30 DistributedCOM 10016 None

Error 10/02/2018 13:19:46 DistributedCOM 10016 None

Error 10/02/2018 13:18:12 DistributedCOM 10016 None

Error 10/02/2018 13:18:12 DistributedCOM 10016 None

Error 10/02/2018 13:18:12 DistributedCOM 10016 None

Error 10/02/2018 13:18:12 DistributedCOM 10016 None

Error 10/02/2018 13:16:06 DistributedCOM 10016 None

Error 10/02/2018 12:41:20 DistributedCOM 10016 None

Error 10/02/2018 12:41:20 DistributedCOM 10016 None

Error 10/02/2018 12:41:20 DistributedCOM 10016 None

Error 10/02/2018 12:41:20 DistributedCOM 10016 None

Error 10/02/2018 09:28:11 DistributedCOM 10016 None

Error 10/02/2018 09:28:11 DistributedCOM 10016 None

Error 10/02/2018 08:57:56 DistributedCOM 10016 None

Error 10/02/2018 08:56:40 DistributedCOM 10016 None

Error 10/02/2018 08:56:40 DistributedCOM 10016 None

Error 10/02/2018 08:56:40 DistributedCOM 10016 None

Error 10/02/2018 08:56:40 DistributedCOM 10016 None

Error 10/02/2018 08:48:51 DistributedCOM 10016 None

 

There are lots of discussions on this topic here at TenForums, but the clearest explanation of the problem and the fix come from this Shaun Cassells article: Windows 10 Event 10016 Fix: 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 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.I a – Quarter Five – Thoughts and Solutions. I've got this issue on most of my systems and have never bothered to fix it. Doesn't seem to have much of an impact either way. Do what you think best!
HTH,
--Ed--

 

Thanks, that fixed the problem! BTW, at the end of those instructions, under the heading "Change DCOM Permissions", where it says to give the newly added System full control, I decided to give it full local control only, rather than full local and also full remote control. I don't know what I'm doing, but it seemed like a good idea, and when I rebooted the PC, I now see no errors inside the error section in Event Viewer, so the problem has now been resolved.

 

Whoops, I have made an error in my reporting of the solved problem. Although the problem was solved on a reboot, when I did a "cold boot" the next day, the problem returned. But I've just realised something else. The CLSID and APPID in the event viewer error message are different to the ones that are used in the example above. Mine are:

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

There's a discussion about this issue with those IDs here, on tenforums. I followed the advice, which was similar to the advice given in the example above, but it didn't solve the problem. The advice also said that if the problem wasn't resolved, you could go ahead and delete the key in the registry. I haven't done that yet, and probably won't. I expect I'll just leave it, as it doesn't seem to be causing any issues.