DistributedCOM Error.

Kpat62 said:

Does MS like giving us the runaround?

No; Microsoft likes to show us that we are not in control of our computers because we choose to use their OS under their EULA terms. Plain and simple; even if you opted for the free upgrade when Windows 10 was first introduced for public use, you are still bound by any EULA agreement they come up with in the meantime because of the choice of continually using their OS.


In other words, the evolving EULA is as evolving as the OS itself. So if you want to see just how in control they are and you are not, just take a gander at the current EULA.

Guys I did a fresh install of Windows 10 last night and right after finish I checked the events. Guess what 10016 is there.
I'll personally give up, have better things to do with my time on my computer than to fix what Microsoft doesn't. Cheers

EdTittel said:

I don't know (and haven't been able to find) a single case where a DCOM error has led to noticeable performance degradation or other stability or reliability issues with Windows 10. Seems like something less that critical priority, in the grand scheme of things. That said, of course, it's your system and you can choose how you want to spend your time and energy on it. Do keep us posted, if you find anything interesting, or figure something useful out. Thanks,
--Ed--

Let us be the first to correct that then

This error will absolutely shut down my computer every time it occurs. No blue screen, just a immediate halt that forces a reboot after a set amount of time. Anything playing/running at the time stalls/stops.

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-T24B9EL\locol SID (S-1-5-21-3276084130-2428855680-3385592425-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.

Ever had chrome freeze for a bit? I just did and jumped in event viewer, yep, 10016 runbroker. Chrome started responding again while I was viewing. Will keep an eye on it if it's repeatable...could be chrome though. If I catch it a couple more times, I might regedit it and see if it still happens.
BTW, it isn't always chrome as there are a lot of 10016's that I never notice doing anything.
Will keep ya posted and yea, MS should fix this...better than the multitude of updates that are a PIA managing 20 pc's in a small business.

I will also say these errors have been causing me problems the last few weeks with soft-resetting back to BIOS.

10016 error with SecurityAppBroker, WscDatProtection, and WscBrokerManager.

I changed the owners from all 3 from TrustedInstaller to Administrator, and got permission denied when trying to change the user SID like the other poster said to do. So I'll see if this fix works for now.

Originally Posted by drclap01

Let us be the first to correct that then

This error will absolutely shut down my computer every time it occurs. No blue screen, just a immediate halt that forces a reboot after a set amount of time. Anything playing/running at the time stalls/stops.

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-T24B9EL\locol SID (S-1-5-21-3276084130-2428855680-3385592425-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.

I'm getting bunches of these errors in twos and fours on my Win 10 Pro 64-bit version 1903. They belong to PerAppRuntimeBroker. Fortunately no BSODs or shutdowns.

I have not tried to fix them in dcomcnfg because I come up against a Windows Security warning. Please see my new thread here at 10016 Warnings for PerAppRuntimeBroker but Windows Security warnings