Error - Event ID: 10016; DistributedCOM

Anonymous
2013-10-20T20:30:29+00:00

I am getting this error repeatedly since I updated from Windows 8 to 8.1. It occurs once every time the PC is booted, about 2 minutes after it boots up.

Can you please help me to fix it?

Log Name:      System

Source:        Microsoft-Windows-DistributedCOM

Date:          10/20/2013 3:19:04 PM

Event ID:      10016

Task Category: None

Level:         Error

Keywords:      Classic

User:          LOCAL SERVICE

Computer:     

Description:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID

{C2F03A33-21F5-47FA-B4BB-156362A2F239}

 and APPID

{316CDED5-E4AE-4B15-9113-7055D84DCC97}

 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.

The APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} is for a COM application called "Immersive Shell". I cannot use the Component Services administrative tool to edit the security permissions because every setting is "grayed-out".

I tried running in Safe Mode and was still unable to modify any of the Immersive Shell settings.

The PC has no software installed except for the latest Intel drivers. I performed a clean installation of Windows 8, installed chipset, VGA, Intel Rapid Storage Tech, LAN, and Intel Management Engine drivers. Then I updated to 8.1 through the Store app. The errors began immediately after that update.

The PC has an ASUS Z87 motherboard, 16 Gb of DDR3-1866 ram, Intel i7-4770k cpu. It is not overclocked but memory is in XMP mode at frequency 1866. The system drive is an SSD.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-10-24T18:39:39+00:00

In system event viewer, I started getting error Event ID: 10016 after upgrading to Win8.1 on October 17, 2013.  The system event viewer on my Dell XPS One 2710 was error free prior to upgrading from Win8 to Win8.1.

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID

{316CDED5-E4AE-4B15-9113-7055D84DCC97}  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.

For me, the solution was provided by Greg310 in Dulwichdik's link as follows:

  1. Open Regedit
  2. Go to HKEY_Classes_Root\CLSID{C2F03A33-21F5-47FA-B4BB-156362A2F239}
  3. Right click on it then select permissions
  4. Click Advance and change the owner to Administrators group. Also click the box that will appear below the owner line. ("Replace owner ...")
  5. Apply full control
  6. Go to HKEY_LocalMachine\Software\Classes\AppID{316CDED5-E4AE-4B15-9113-7055D84DCC97}
  7. Right click on it then select permission
  8. Click Advance and change the owner to Administrators group
  9. Click the box that will appear below the owner line
  10. Click Apply and grant full control to the Administrators group
  11. Go to Administrative tools
  12. Open component services
  13. Click Computer, click my computer, then click DCOM
  14. Look for the corresponding service that appears on the error viewer [Immersive Shell]
  15. Right click on it then click properties
  16. Click security tab then click Add User. Add Local Service then apply
  17. Tick the Activate local box

Thank you Daniel MoisesMagulado and Greg310 for addressing the problem and providing the solution!

Was this answer helpful?

800+ people found this answer helpful.
0 comments

99 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-11-30T22:38:47+00:00

    I agree...did the Fall Update (1709) tried to get rid of Windows.MiracastViewer logged errors (following tips an tricks all over the net)  an it caused all sorts of DCOM issues. So (an for other various reasons) I reinstalled the 1703 version an dealt with DCOM errors on a  per GUID (& APP ID) basis which is to say thru permissons (i.e. took ownership) on an individual basis without using Local Policy Group Editor or changing those settings. Doing so eliminated all the DCOM Event errors for me. (but you just never know theses days if that sort of thing will re-emerge) 

    At this point in time 1709 (Redstone 3?) is not running smoothly for me, with those DCOM an other Event Viewer errors so going back to 1703 an working through the DCOM (much fewer) as stated on an individual basis eliminated them. There was a 'fix' for DCOM 10016 errors on another site that went as follows:

    1. Type or paste ‘regedit’ into the Search Windows box.
    2. Navigate to ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole’.
    3. Delete these four keys if they appear, DefaultAccessPermission, DefaultLaunchPermission, MachineAccessRestriction, MachineLaunchRestriction.
    4. Reboot your computer. 

    What doing this did (for me) was cause MORE DCOM errors both in 1703 AND 1709 OS versions. Seems like the latest iteration of Win10 (1709) hates any tinkering with the registry files or trying to change installed apps settings; plus I found windows settings changed not to my liking in 1709 an can only be changed back using Local Group Policy (which I find odd in that they were not tinkered with in the earlier OS version)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2015-09-01T03:34:23+00:00

    Thanks a lot. I haven't had the issue since uodatingjto win 10 but will save this in case.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2015-08-30T19:45:25+00:00

    This error has been happening for several years and microsoft reports that they have no information on it.

    How is that? Unfortunately this fix only works with windows 8 and before.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2013-10-21T18:31:15+00:00

    Hi Rajesh, thanks for your assistance.

    1. Nothing happens that I can perceive, other than the logging of the error in Event Viewer. That's not to say it isn't causing any problems, just none that I have found since this is a new installation and I haven't used the PC yet.
    2. Not connected to domain, just a LAN.

    I have the system running in "clean" mode [where all startup items are disabled in Task Manager and all non-Microsoft services are disabled by the System Configuration utility]. The error is still occurring.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments