Distributed COM error--application-specific permission settings

I have seen some veteran members here post about event viewer messages in the past, in the days of Win 7 and Win 8... with the general consensus not to bother with addressing them unless you're experiencing a functional issue. Is that generally still true in Windows 10?

Generally I like to run a "clean ship" and have resolved a few event viewer messages by correcting a registry entry or deleting a program and reinstalling it. But some recurring ones are a bit more mysterious and I wonder if there's any sense in trying to track them down and correct them.

Case in point, this repetitive entry:
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID XXX and AppID XXX...".

-

EventData

param1

application-specific

param2

Local

param3

Activation

param4

{D63B10C5-BB46-4990-A94F-E40B9D520160}

param5

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

param6

NT AUTHORITY

param7

LOCAL SERVICE

param8

S-1-5-19

param9

LocalHost (Using LRPC)

param10

Unavailable

param11

Unavailable

My event system log has a number of these entries with different CLSID's that periodically repeat. I noticed in the end of the message, "This security permission can be modified using the Component Services administrative tool." That leads me to believe that it can be corrected.

Question is, should I bother trying to track down the security permission required and fix it? Or is it just better to track down the program associated with the CLSID or AppID and uninstall/re-install it? Or... should I not even bother and simply accept that Windows 10 events are going to contain some mysterious error entries no matter what?

Hey cytherian,
Most of the DCOM 10016 errors are by design ... See this post - Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums

With that said, some of the DCOM 10016 errors can be fixed by adding the missing permission, but it's a bit of a pain to do so. If they really bother you, I recommend using PowerRun to launch the Dcom Config, so you have the correct permissions without having to mess around in the registry. I have a how to on this I can post if you want it?

Eagle51 said:

Hey cytherian,
Most of the DCOM 10016 errors are by design ... See this post - Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums
With that said, some of the DCOM 10016 errors can be fixed by adding the missing permission, but it's a bit of a pain to do so. If they really bother you, I recommend using PowerRun to launch the Dcom Config, so you have the correct permissions without having to mess around in the registry. I have a how to on this I can post if you want it?

Hi Eagle51, thanks for the info -- I should relax my OCD about wanting a clean computer, I supposed. Still, it would be interesting to see the effort involved with PowerRun. If you can dig up the reference at some point, please do so at your convenience. Thanks!

Still, it would be interesting to see the effort involved with PowerRun.

1. Download the latest PowerRun - PowerRun v1.3 (Run with highest privileges)
2. Unzip the PowerRun.zip file and double click PowerRun.exe or PowerRun64.exe to start the program
3. Add Component Services (i.e. Dcom Config) by clicking the Gear Icon (+)
Location - %SystemRoot%\System32\dcomcnfg.exe
Working Dir - %SystemRoot%\System32
Click Apply List
4. Double Click on the dcomcnfg.exe you just added to open Component Services
5. Expand Component Services > Computers > My Computer > Dcom Config
6. Component Services Top Menu > Click View > Detail so you can find and know you're working on the right AppID
7. Find the AppID and right click on it > Properties > Security Tab > Launch and Activation Permissions > Check Customize and Click Edit
8. Add the User and Grant the permission from the Dcom 10016 event viewer error (i.e. Local Service with Local Activation OR MyPcName\MyUser with Local Activation)
9. Close Component Services
10. Close PowerRun
11. Reboot PC

Note:
1. PowerRun is a stand alone program, so no install.
2. If you're not comfortable doing the above, then don't do it.