Why Certain DCOM 10016 Events Don't Matter

EdTittel · 11 Dec 2018

@gboutin It's your choice if you don't want to accept the MS explanation. It's your privilege to believe the error classification is incorrect. But that's the data that Microsoft provides, and the explanation that goes with it. I have no trouble accepting it, and proceeding from the understanding I outlined in the original post to this thread. If you don't like it, you might want to jump up on the Feedback Hub and share this perspective with Microsoft there. Who knows? Maybe they'll do something about it.
Best wishes,
--Ed--

MeAndMyComputer · 24 Dec 2018

Ed and f14tomcat, this is an excellent thread and excellent responses for all of us.

BLaZiNgSPEED · 24 Apr 2019

I have exactly the same issue with DCOM Event ID 10016 DistributedCOM.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-JU46CAH\Rahul SID (S-1-5-21-3103493426-1909410407-3242254243-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

Now I tried fixing this issue using the same method from the Windows 8 forums. https://www.eightforums.com/threads/...1/#post-135109
This fix worked for Windows 8.1 when I previously had this issue.

However, be warned that when I tried making the exact same attempt in fixing this issue in Windows 10 it completely dismantled my Cortana SearchUI.exe functionality.

I ended up having to do a Windows System Restore as SFC /Scannow did not fix the problem.

In both attempts I tried to modify the registry to add permission in the space of a few days. And then I went to Computer Services and searched for {15c20b67-12e7-4bb6-92bb-7aff07997402} which is associated with the RuntimeBroker. I tried modifying the permissions but it won't let me as it will be greyed out. I tried to force it to work by going to Default option and then back to Customise.

And even when I added my Administrators username the error still showed up in Event Log. Upon restart of the PC SearchUI.exe will fail to work.

Fortunately for me Windows System Restore fixed it for me. In fact I made a system restore point prior to the experiment because I knew if this were to break again at least I can fix it by restoring the computer again.

So far this particular error in the Event Log is incurable. My event log is flooded with this error and this error only. I don't know whether this issue happens across all Windows 10 OS versions. But it is definitely something Microsoft need to fix with a Windows Update hotfix.

This is actually very disappointing. I had a problem with Windows 8.1 Event Log Kernal Error Event ID 2 being triggered when accessing Network Sharing Center. I fixed this with a reformat and installation of Windows 10 only so that I now have DCOM Event ID 10016 error...

Steve C · 24 Apr 2019

BLaZiNgSPEED said:

I have exactly the same issue with DCOM Event ID 10016 DistributedCOM.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-JU46CAH\Rahul SID (S-1-5-21-3103493426-1909410407-3242254243-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

Now I tried fixing this issue using the same method from the Windows 8 forums. https://www.eightforums.com/threads/...1/#post-135109
This fix worked for Windows 8.1 when I previously had this issue.

However, be warned that when I tried making the exact same attempt in fixing this issue in Windows 10 it completely dismantled my Cortana SearchUI.exe functionality.

I ended up having to do a Windows System Restore as SFC /Scannow did not fix the problem.

In both attempts I tried to modify the registry to add permission in the space of a few days. And then I went to Computer Services and searched for {15c20b67-12e7-4bb6-92bb-7aff07997402} which is associated with the RuntimeBroker. I tried modifying the permissions but it won't let me as it will be greyed out. I tried to force it to work by going to Default option and then back to Customise.

And even when I added my Administrators username the error still showed up in Event Log. Upon restart of the PC SearchUI.exe will fail to work.

Fortunately for me Windows System Restore fixed it for me. In fact I made a system restore point prior to the experiment because I knew if this were to break again at least I can fix it by restoring the computer again.

So far this particular error in the Event Log is incurable. My event log is flooded with this error and this error only. I don't know whether this issue happens across all Windows 10 OS versions. But it is definitely something Microsoft need to fix with a Windows Update hotfix.

This is actually very disappointing. I had a problem with Windows 8.1 Event Log Kernal Error Event ID 2 being triggered when accessing Network Sharing Center. I fixed this with a reformat and installation of Windows 10 only so that I now have DCOM Event ID 10016 error...

Trying to fix these 'errors' can result in unforeseen consequences as you have discovered. They are best left alone. If you are bothered then file a feedback report and hope that Microsoft fixes them.

f14tomcat · 25 Apr 2019

Agree with Steve 100%, hence the title of this thread. Although there can, and have been, some rare occurrences of reports tying DCOM errors to BSODs and other specific issues, on specific machines, under specific circumstances, in general they are best left alone.

ddelo · 25 Apr 2019

f14tomcat said:

Agree with Steve 100%, hence the title of this thread. Although there can, and have been, some rare occurrences of reports tying DCOM errors to BSODs and other specific issues, on specific machines, under specific circumstances, in general they are best left alone.

After spending a lot of time trying to battle these errors, I couldn't agree more.

And as Ed mentioned, if the Microsoft explanation presented in the 1st post, is not adequate for some people, just take it from our experience and leave them alone!

chrisinthesun · 30 Apr 2019

Just to check in. Does this mean that this specific DCOM error I'm getting (always the same AppID), can safely be ignored?

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user MSI2080\chris SID (S-1-5-21-3365679145-3112613430-3461068617-1001) 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.

And just out of interest, any idea which application or program is causing it? I read somewhere that this AppID is Nvidia related, but I can't find anything concrete on that. If its any help, my laptop includes both Intel IGP and an Nvidia 2080GTX, so there is GPU switching that occurs. Could it be that? My laptop is an MSI GE75 8SG if thats any help.

EDIT: Steam causes one instance of this error in event viewer every time I start it. Steam was set to use hardware acceleration, meaning it was switching from IGP to the Nvidia GPU. I disabled this, restarted Steam and still got the error in event viewer - so I know its not related to the GPU switching.

I can also reliably generate an instance of this error when I load a webpage that contains a Flash element. (under Firefox).

Chrome also generates an instance of this error when started, although I've noticed that Firefox does not.

And I do sometimes see some instances of this error but with a different AppID - although the AppID listed above is by far and away the most common one I see.

Now I wish I'd never opened the bloody Event Viewer lol! Sometimes blissful ignorance is best.

swarfega · 30 Apr 2019

I have trained myself to not bother to check event viewer now and I feel happpier as a result.

Zardoc · 06 May 2019

I've turned off DCOM. Don't miss it at all.

BLaZiNgSPEED · 06 May 2019

Zardoc said:

I've turned off DCOM. Don't miss it at all.

If this is the method you used to turn off DCOM from the Component Services. https://i2.wp.com/missvirtualreality...5/08/dcom8.jpg
Well sadly this does not stop the error that the
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}

This error absolutely all Windows 10 users suffer from regardless of what their settings are. I've tested Windows 10 LTSB Enterprise 2015, Windows 10 Home and now Windows 10 Pro. On all 3 versions I get the exact same DCOM error before the Windows update and after.

Microsoft should've worked to strip-off this error message from appearing in the Event Log. It is annoying and causes one to feel that they have a problem with their Windows even though this appears to be not a problem at all. It should never appear as an error it is psychologically misguiding.

The way you wrote that gave me a first impression that you don't have this error in your event log, but I don't believe that's the case. I'm sure if you check your Event Viewer you will see you'll be flooded with this error.

Anyway, I'm glad I saw this thread a few weeks ago otherwise I would've been obsessed over how to fix this without any good reason. In Windows 8.1 it was possible by granting permission to the above ID's via registry. But this doesn't work in Windows 10.