Windows 10: Error 10016 in Event Viewer

Hello.

I keep having Errors 10016 involving DCOM in Event Log.

Even when I set correct permissions with the Regedit and DCOM administrative console regarding the CLSID and APPID, those errors keep appearing with a different item each time a few days later.

So I was thinking to do the following, instead of modifying each key each time : open DCOM Administrative console, clicking on "Components Services", "Computers", "My computer". Then right clicking on "My Computer", "Properties", "DCOM Security", and add Users SIDs involved in the 10016 errors in the "Launch and Activation" category.

Do you think it would work ?

Thanks !

:)

 

Event viewer error 10016

Hi Eve,

For us to narrow down your concern for getting the event viewer error 10016, we would like to know the following:

• Were there any changes made on your computer prior to the issue (i.e., updates, software installation)?
• Is this the first time you experienced the issue?
• When did the issue first begin?

We look forward to your response.

 

Event viewer error 10016

Hi,

I've tried everything to try and resolve multiple errors relating to com server. I can't alter the permissions within the component services/DCOM config. I've tried everything logging in with the default built in administrator account and making sure my
user account has permissions at the computer level. That didn't work. Then tried booting in safe mode and tried to change the permissions but that didn't work. Every time I would go to the permissions tab for the CLSID hex value everything was grayed out.
The same happened when I tried to change permissions in the registry. I'm at a loss! Does anyone have a clue why this is impossible to change?

Thanks so much.

 

I can answer : it doesn't seem to work.

"System" has already had all of the checkboxes checked, but I had to manually add the permissions.

 

In Event viewer you have to see:
- which User is missing, for example, Networking Service, System
- which permission is missing, for example "Local Activation"
- you have to take ownership of CLSID and APPID that are shown in Event viewer, but remember who has the Ownership because you should put it back to this one after you finished.
- Search Registry for both CLSID and APPID and takeownership
- In APPID, in the right pane, there is the real Service Name; Take note of it, you need to look for it later.
- Reboot
- open Run> COMEXP.MSC
- Click Computers>My Computer>DCOM Config
- Search for the Service Name you noted from registry entry or you may search by APPID from event viewer
- Right Click>Properties>Security and there you have to make the changes that Event Viewer said are bad or missing

 

Is the error showing up in your Reliability History?
Is it causing any software to not function?

If the answer is "No", to both, don't worry about the DCOM errors in Event Viewer.
I get them all the time, and they are meaningless to the user.
Some errors are actually expected, such as the DCOM.

Some are just timeouts:

Here it states "do not grant Local Activation permission for the COM Server", So it probably needs online permission.
I tried fixing it once(with instructions online), and my system went

and then I had to reimage.

Also granting permissions, where you shouldn't opens the door to malware and Ransomware.

 

<quote>'Here it states "do not grant Local Activation permission for the COM Server",
First time I have seen a straightforward statement about this (annoying) recorded error at startup. If it is associated with online then that is the explanation because my system starts up so fast...or the internet connection is so slow there are also messages that network etc are not there. That fast startup is disabled but this current AU version zooms into action before the connections so this DCOM error has persisted.

 

For my "poor" understanding, system is complaining that Local Activation is not granted as required , in other words, system can not perform request because the Local Activation is not allowed. It has nothing to do with that it should be remotely, the message should , in that case, be then "Remote Activation".

 

Hi,

Correct.
Those DCOM errors are quite easy enough to fix but OTOH they're harmless and next time there's a CU they'll quite likely sneak back in.

To TS: If you like to fix this then here's how to :

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Cheers, *Wink

 

Hi there,
I did this corrections and since then and after at least 321 and 351 updates they did no come back.
Indeed, I did had situations where the corrected DCOM errors were coming back. There are so many "updates" flying around and I can not remember in what situation they were coming back, but I believe it was by doing a In-Place upgrade that they come back, but I am not sure.

EDIT: The "problem" is that Machine is losing "time" trying to do the Task and Writing Events, so all that take time and makes PC Slower.

 

Hi,

Quite often they are :

-Runtimebroker

-Immersive Shell

_ {F72671A9-012C-4725-9D2F-2A4D32D65169}

The main thing to remember is to return ownership to the original owner. Most of the time that would be TrustedInstaller but not always.

Yeah, I lost track of how or why these crop up again too........

Cheers, *Wink

 

Thanks for post, Cliff. At least I won't be spinning my wheels trying to fix something relatively unimportant now.

 

You're welcome John.

I have found Event Viewer is there, to help give information about the error Windows shows you(Reliability History, or a popup window), and not to look for errors.

 

Thank you very much! Really helpful to solve my 10016 issues!