Windows 10: Event Viewer Event ID# 10016 listed four consecutive times at boot??

Morning Steve C,

I appreciate your willingness to participate in this discussion.

Thanks and regards,

 

Hi,

I just noticed today that in my Event Viewer I find this item listed four consecutive times after each boot:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 4/10/2018 3:47:19 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: LOCAL SERVICE
Computer: (Hidden by poster)
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.


When I have googled this event ID error I have seen there is a way to get rid of them but it involves steps way over my 76-year-old brain-housing group capabilities ...lol From what I have read and understand this error is normally nothing to worry about.

I have seen different #10016 errors besides this one but I never noticed any of them appearing four consecutive times after each boot. All four entries are exactly the same.

I am just curious if having the same identical entry four consecutive times is a cause for worry.

Thanks and regards,


:)

 

Event log writes error related to application-specific permissions on Windows 10 computer

Wow, are we just talking about the "Event Viewer - Event ID 10016" fix for F72671A9-012C-4725-9D2F-2A4D32D65169 here?

If so, there is a far simpler fix that resolves it in no time without deleting any entries.

 

Event viewer error with event id 10016

Hello,

I am running win 10 SL home edition 64 bit. I am getting this error several times in a day in event viewer.

.



Can you please help me fix it? Any suggestion from your end would be appreciated.

I look forward to seeing you soon.

Thank you.

 

Your APPID points to the ShellServiceHost. You are correct; there are ways to remedy this DCOM error, but you either have to do the steps or live with it.


I am not entirely certain this particular DCOM error is harmless; nonetheless at least you have the class pointers telling you why the error is occurring.


I could walk you through the steps to get rid of it; but some will argue that it opens up security holes. I normally enter the command prompt in the recovery environment and start my registry hacking there; but it is extremely more complex than doing the regular component services method after altering the permissions on the keys.

 

I just pointed another person to this long thread, so have a read and see if it helps you.

 

That is a nice thread. In fact, that is the one that got me interested in fixing DCOM errors.

 

I had an attempt at it once but ultimately failed. I believe I read somewhere that they are not real errors but I don't know enough about it.

 

Yes; that is generally the accepted realm of thinking when it comes to these errors, so long as they are DCOM 10016 errors. You would be amazed at how many times I found the reason for the error being generated, was because there were random segments of code left over in the registry and there was basically no real problem at all.


That is why (usually, not always) they are harmless; simply because it is something in the registry trying to call attention to something that no longer exists and a simple deletion of the troubling Guid usually fixes the broken protocol.


However; when you have the APPID and CLSID being flagged, you cannot simply delete the Guid in question. The component services must be adjusted and some still argue it opens up security holes.

 

Hi, EyeInTheSky and swarfega,

I appreciate both of your replies. It looks like I had better just learn to live with this error until there is a way for 'old folks' like me to correct them ....lol

Thanks and regards,

 

Don't lose hope. Sometimes the Cumulative Updates from Windows Update corrects them. If enough people complain about them or document them like you did, Microsoft puts out Cumulative updates that not only correct the log error; but they security patch the backdoor that causes the error as well in the Component Services. That is why it is best to let Microsoft take care of them in due time; unless you know absolutely for sure what you are doing.


In my particular case, I'm not on a home network; so I generally know how to set the component services manually without creating a security risk to myself.

I noticed on my previous build (Last Falls Creator Update - Version 1709) that some of my DCOM errors were disappearing automatically after Cumulative Updates. The ones that couldn't be fixed because they were dead entries in the registry are the ones I had to go after manually.

Some people use a registry cleaner to do that; but in all honesty, I don't use them because when I add my right click hacks and nir commands, the registry cleaner would delete my hard work even when I had them on the ignore list of keys in the registry to not touch.

 

Hi EyeInTheSky,

Thanks for the added information on this subject.

Regards,

 

Some people have this error code on a clean install and I have them on all PCs. There are ways to fix them but nobody really understands the consequences of fixing what in reality may not be an actual error. I just ignore them and hope MS manages to fix these 'errors' in routine updates.