Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Not sure if this helps, just an observation...

Normally when I have to deal with DCOM issues I only change the permissions for the AppID and CLSID
to be able to edit DCOM, which I believe you've already done. In this case the following.

Computer\HKEY_CLASSES_ROOT\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
Computer\HKEY_CLASSES_ROOT\CLSID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}

I checked my system and I don't have the Launch in the following, I'm guessing 3rd party software added it ???

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
Default REG_SZ ShellWindows
Launch REG_BINARY ?????
RunAs REG_SZ Interactive User

Hi,

Launch REG_BINARY ?????

I do not have that Dword either. I'm guessing the same as you and that's probably why Joanne's the only person (so far) who's experiencing this issue.

Cheers,

Thank you for your observations, Eagle51 and fdefrove.

1) @fdefrove, the power config command you wrote has to do with Hibernation, and I always disable Hibernation, right after the clean installation of my OS.

2) To both of you, guys: initially, I did not understand what Eagle51 reffers to, but now I have observed this Launch Permission REG_BINARY key, there...

Okay, so what is that?! Should I delete it? What do you guys have there? Just (Default) REG_SZ and RunAs REG_SZ?

Thank you.

EDIT: Okay, I went ahead and deleted that "obsolete" Registry key - it was found in my AppID location only - I've cleaned my Event Viewer and rebooted. So far -way too soon- no errors. We will see... I will update this post, accordingly. Thanks :)

Hi,

Good to hear it, Joanne. Normally once a DCOM error is fixed it stays fixed. (Untill MS comes along and breaks it again, LOL)

Cheers,

Unfortunately, this error keeps appearing. As I said, it was way too soon to speak. For the last time I will post here some screenshots I consider important.

My OS:




The error:




Registry settings:




Component Services settings:




After all this, the error keeps appearing.


If anyone has any ideas, cool. Otherwise I give up.

Thank you.

You deleted that Launch from this one.
Computer\HKEY_CLASSES_ROOT\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}

Did you also delete it from this one ?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
Note: If you haven't deleted it yet, export it first before deleting it.
Note: If you can copy/paste the full name of that Launch (I can't see all of it in your pic) and it's Data. Maybe, we can track down what it is.

Eagle51 said:

You deleted that Launch from this one.
Computer\HKEY_CLASSES_ROOT\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}

Did you also delete it from this one ?
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{9BA05972-F6A8-11CF-A442-00A0C90A8F39}

No, not yesterday, but I have deleted it this morning. I made sure that this "Launch..." is not present in my Registry, in any of these locations. After rebooting a couple of times the error appeared again!

Eagle51 said:

Note: If you can copy/paste the full name of that Launch (I can't see all of it in your pic) and it's Data. Maybe, we can track down what it is.

That "Launch..." value does not exist in my Registry any more. Before deleting it though, I took two screenshots. It does not allow me to paste its contents in notepad, for example, the window cannot be maximized or enlarged, either, so I just took screenshots.





Anyway, as I said, the 10016 error keeps appearing in my system, even after completely removing that "Launch..." value. I have no idea why this is happening...

If you can make something about the "Launch..." value, it would be interesting to know. I do not think this will resolve the problem, though, because the 10016 appeared again even after deleting the "Launch..." and rebooting.

My personal and subjective opinion is that there might be an issue with the locations in my Registry where I am applying all this, and also perhaps with the User.

Thank you for your support!

Hi,

My personal and subjective opinion is that there might be an issue with the locations in my Registry where I am applying all this, and also perhaps with the User.

Yes, those keys should not be touched, just the ones shown in Eagle51's posting.

Cheers,

fdegrove said:

Hi,



Yes, those keys should not be touched, just the ones shown in Eagle51's posting.

Cheers,

Hi,


Initially, I have applied lx07 PowerShell script (post #12) and then, since this has not resolved it, Marco83 instructions (post #90). I have shown all these with my screenshots.

According to your expertise:

- Can / Should I go back and, somehow, revert those Registry changes to their Default state? Is this even possible?

OR

- The only way to resolve this is a clean installation of my OS?

I am asking just out of curiosity. Besides the fact that I am not facing any issue with my OS, I've just run SFC and it has not found any Integrity violation. I realize that this 10016 is nothing, really. I'm just asking.

Thank you.

Hi,

- Can / Should I go back and, somehow, revert those Registry changes to their Default state? Is this even possible?

If you recall exactly what you've changed then, yes, it is possible but it involves some work at your end and what will it solve ?

- The only way to resolve this is a clean installation of my OS?

Quite probably but I still wonder what's causing this DCOM error. Most of these DCOM errors are pretty much benign and we all have them (and mostly the same ones) on our installs. Solving them is pretty straightforward once you grasp the mechanism involved.

I still suspect it must be some software package you have or had installed that triggered it. No idea why it does not seem to obey to the basic fixing routines though.

In this particarly obtuse case I'd opt for a clean install and start with a clean slate again.

Best of luck,