Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Hi,

Looks good to me.
Only a few things I want to add for your convenience: no need to close the registry editor whilst your are in DCOM console.
A reboot is not required immediately. At next restart the error(s) should no longer appear.

DCOM errors are pretty harmless to begin with. Don't be surprised that they or some of them keep coming back with every update MS releases for as long as MS don't fix these (and they can't seem to be bothered at this point in time) all the configuring we did now will be overwritten.

You did a great job Marco. This way it should be easier to understand for others as well.

Cheers,

fdegrove said:

Hi,

Looks good to me.
Only a few things I want to add for your convenience: no need to close the registry editor whilst your are in DCOM console.
A reboot is not required immediately. At next restart the error(s) should no longer appear.

DCOM errors are pretty harmless to begin with. Don't be surprised that they or some of them keep coming back with every update MS releases for as long as MS don't fix these (and they can't seem to be bothered at this point in time) all the configuring we did now will be overwritten.

You did a great job Marco. This way it should be easier to understand for others as well.

Cheers,

Thank you fdegrove. So I tried it, and in the first instance, that is RuntimeBroker, method worked just fine, no more DistributedCOM errors. Whereas in the second instance, that is Immersive Shell, it did not work. I'm sure I did everything exactly as described above in my previous post, but the DistributedCOM error keeps coming back as before. Any ideas or suggestions?

New one with redstone upgrade: 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.
Has to do with CDP Activity Store, whatever that is.

Hi,

Whereas in the second instance, that is Immersive Shell, it did not work. I'm sure I did everything exactly as described above in my previous post, but the DistributedCOM error keeps coming back as before. Any ideas or suggestions?

No suggestions really. The procedure is basically always the same.
Maybe do it once more and check everything thoroughly ?
@csmdew : the first hive key is granted to System not TrustedInstaller. The second key is also the DCOM container.
You will have to add System as a user because it's missing in DCOM.


Cheers,

OK I already had system added but who should be the owner so I can edit the security, it's still grayed out with system as owner. How can I edit the batch file used for runtime broker to fix this one, thanks.

Hi,

In regedit ownership should temporarily be granted to Administrators (plural) for both keys then returned to the original owners after you're done in dcomcnfg.

In your particular case original ownership of the first key belongs to SYSTEM so you have to keep that in mind.

Cheers,

made changes and after this reboot the 10016 was gone but now the 10010 is back, you would think with all the problems in this area that MS would have fixed it in the upgrade. thanks for the 10016 help now back to solving the other one.

fdegrove said:

Hi,



No suggestions really. The procedure is basically always the same.
Maybe do it once more and check everything thoroughly ?
@csmdew : the first hive key is granted to System not TrustedInstaller. The second key is also the DCOM container.
You will have to add System as a user because it's missing in DCOM.


Cheers,

Thanks Fdegrove. So, I was reading this thread on EightForums Solved Numerous event id 10016 errors win 8 pro 64 bit when I remembered that, right after assigning ownership from TrustedInstaller to Administrators, there were these other two options, which are supposed to give you permission on all sub-keys:

- Replace owner on subcontainers and objects

- Replace all child object permission entries with inheritable permission entries from this object



Do you think I need to select said options maybe? Will it make a difference with my "Immersive Shell" issue?



As a side note, on Microsoft Answers forum one user suggested an alternative way as to take ownership and allow permissions without modifying the registry. That is, by launching Component Services as administrator, then navigating to My Computer node > Right click > Properties > COM Security tab > Edit Limits.



But I cannot tell if this is reliable as a method. Do you think it is safe to try it as a last resort for "Immersive Shell" DistributedCOM error? Needless to say, I'm quite reluctant and hesitant

Hi,

Do you think I need to select said options maybe? Will it make a difference with my "Immersive Shell" issue?

I don't think so but you can try it out. Basically when you're able to add the user in DCOM and grant the local permissions to that and then return the registry keys to the original owner then that's it.

The so called second method allows you to add a user but then that user would be added to all the containers ?
I don't see the point in doing that.

The Immersive shell DCOM error has been there for a long time but I can't remember it being present with the Anniversary Upgrade.
Either way, if you follow the basic guidelines and you're able to grant the local permissions for the user in the Event Viewer error message then that's all there's to it.

One thing I can think of why it doesn't stick is when fast boot is enabled. You could try disabling it, see if that helps and re-enable it once the problem is gone.

Cheers,

Hey all, and thanks again for help many months ago.
With the Anniversary Update, I am now getting the following, and have a new sub-question:

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.

My sub-question is: why does it say "running in the application container Unavailable SID (Unavailable)"? Should I do anything special because it's "Unavailable SID (Unavailable)"?

Thanks.