Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Hi,

is the last step important?
"Now go back to regedit and for the CLSID & Appid changed ownerships revert back to default TrustedInstaller."
because ive found a more detailed guide to your way of fixing this but theres no mention of it..

Yes, it is important. You need to return ownership to TrustedInstaller for security reasons.

You can try adding launch and activation permissions for user "All Application Packages" and see if that helps.

May just as well run a PC without a password too.
@mike0092 : If you follow the instructions step by step the error should be gone. If not, something wasn't done properly.

Cheers,

fdegrove said:

Hi,



Yes, it is important. You need to return ownership to TrustedInstaller for security reasons.



May just as well run a PC without a password too.
@mike0092 : If you follow the instructions step by step the error should be gone. If not, something wasn't done properly.

Cheers,

ill just assume giving back ownership to trustedinstaller for these 2 keys is just reversing the first steps?

Hi,

All you need to do is change both regkeys back to TrustedInstaller (NT SERVICE\TrustedInstaller).

Cheers,

fdegrove said:

Yes, it is important. You need to return ownership to TrustedInstaller for security reasons.
May just as well run a PC without a password too.

Hmm, I see; you clearly do not have any understanding of the Windows NT object security model, at all. Is that correct? To wit:

1. Changing ownership back to whoever makes no difference after you have already given the admin access rights to the object in question. If you are concerned about restoring security, you would have to delete the access permissions you just gave to admins. But you knew that, did you not? In other words, you need to both revert ownership back to TrustedInstaller and revoke the permissions you gave to admins.
2. App security is governed by a nested security structure so, no, giving access to "All Application Packages" (a common ACL structure for a number of Windows system objects, by the way, if you care to inform yourself about the subject) has nothing whatsoever to do with "running the PC without a password". That analogy doesn't even hit in the same galaxy... All this means is that an app run by a user may obtain access to other objects that already allow access by that same user through the bridge constituted by the DCOM object. Feel free to ask if you have more questions. This book may be helpful if you want to learn more.

lx07 said:

Sure it would remove the error message but at the expense of giving every single Windows Store app the authority to do whatever they want.

Sorry, I only saw this just now. See my more detailed answer above.

fleks said:

ill just assume giving back ownership to trustedinstaller for these 2 keys is just reversing the first steps?

No, see my answer above.

Hi,

Dcom error are easily solved. No need for books to achieve that so let's move on. OK ?

Cheers,

fdegrove said:

Dcom error are easily solved.

No, they're not; not all of them, anyway.

fdegrove said:

No need for books to achieve that so let's move on.

That's not the point. People following the advice given so far have indeed opened up their systems to potential security holes, by allowing any user with admin rights to modify activation and launch permissions for the objects in question. In particular, nothing keeps any such user from allowing anyone to launch these processes remotely. To repeat: If you want to fully restore the security of your system to the level it was at before you started fiddling with those DCOM permissions, you have to revoke the admin access permissions you have added. While you don't seem to care about security, some people may do so, in which case they would be well advised to read what I wrote.

Hi,

While you don't seem to care about security, some people may do so, in which case they would be well advised to read what I wrote.

Why don't you just go trolling elsewhere ?
This is a very fine forum with extremely helpful people so ?

Cheers,

fdegrove said:

Why don't you just go trolling elsewhere ?
This is a very fine forum with extremely helpful people so ?

Would you like to explain what, specifically, you mean by "trolling" as it applies to my post(s)?
Or, would you like to explain what you find unhelpful about a post explaining how people should restore the integrity of their systems if they so wish? What do you find objectionable in the post of mine you were responding to? Please be specific so I can edit my post accordingly.

Thank you.

fdegrove said:

Hi,

All you need to do is change both regkeys back to TrustedInstaller (NT SERVICE\TrustedInstaller).

Cheers,

and how do you do that?
i understand thats easy for people with the knowledge but if you explain something for people without that you kinda have to describe it in detail..
telling me or any other person without the knowledge to "just change regkeys back" is like a wall of questionmarks.

because for example here:
Error - Event ID DistributedCOM - Microsoft Community
this got linked as a solution to the problem yet there is no mention of changing back anything after those steps - its just very confusing at this point and i dont think someone without experience in the registry should do this?
is it even needed to fix these errors? or should lesser skilled users just ignore them?