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
    2018-06-05T13:29:31+00:00

    When 1709 Fall Update was introduced MS added itself as a 'User' and has since locked down all DCOM settings. If you are now getting the Error ID 10016 (as of April 2018) MS says...'this is as intended and should be ignored'.

    In older OS's one could change settings to eliminate these errors but not anymore. It seems MS wants to be able to remotely access all the OS's from this (1709) point forward.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    2017-12-22T09:04:52+00:00

    When you say your PC shuts down it leads me to believe that it may be related to your Power Settings. Some come 'out of the box' or 'stock' to shut down after so many minutes. It could be sleep settings or hard drive settings to name a few. Those two need to be set to NEVER. Double check your Power Settings and make sure that they aren't set to shut down things. You'll have to go through each an every one setting them to the way you want when finished create your own personal power settings while there so if need be you can just click on that to reset them back to the way you want.

    As far as DCOM errors go you'll have to find which GUID is being generated in the Event Viewer showing those errors. Then you'll have to go into the registry file an 'take ownership' which means you'll change the Permissions to Administrators to allow you to change those settings. Some times they are default set to Trusted Installer, by changing those you'll be able then to go to the Group Policy Editor and add SYSTEM to that group (along with Administrators) that will stop those DCOM errors in W10. It usually is a RunTimeBroker setting that needs to be 'tweaked' Here is a link I used to fix those DCOM errors. I also had one other GUID showing so I copied that from Event Viewer and searched regedit changed those permissions to Administrator along with the greyed-out RunTime in GPO (Group Policy Editor) 

    note these tips where taken from a blog site found on Google

    Regedit Take Ownership

    You will need to take ownership then set rights against two different keys.  The keys are:

    HKEY_CLASSES_ROOT\AppID{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}

    HKEY_CLASSES_ROOT\CLSID{D63B10C5-BB46-4990-A94F-E40B9D520160}

    Open Regedit with Administrators privileges and navigate to the keys above (remember you have to do this twice)

    WinKey + X >> Command Prompt (Admin) >> Type in Regedit

    Right click the key >> permissions

    Click advanced

    At the top change the Owner to COMPUTERNAME\Administrators

    Please note if you are domain joined you’ll have to change where you are searching from to your local computer

    Look in the Permission Entries field

    If the local system administrators group is listed ensure it has full control

    if the administrators group is not listed add it and give it full control.  (note you can only do this if you are a member of the administrators group and it is now the owner)

    Click okay a lot >> Ensure you apply permissions to all child objects

    Change DCOM Permissions

    Need to ensure DCOM permissions are setup

    Open DCOMCNFG as an Administrator

    WinKey + X >> Command Prompt (Admin) >> Type in DCOMCNFG

    Navigate to Component Services >> Computers >> My Computer >> DCOM Config

    Find the RunTimeBroker  >> Right Click >> Properties >> Security Tab

    Launch and Activation Permissions >> Edit >> Add System and give it full control

    I also added the Administrators group just for testing

    While changing permissions I was prompted several times to remove bad account references.  I did this as the computer knows which accounts have been removed.

    Summary

    At this point you should have sorted the DCOM errors.  Give your computer a reboot.

    It can be a bit daunting at first I know it took me several tries til I felt comfortable with it. The main thing is getting the DCOM error App ID & GUID from the Event Viewer errors and finding them in the Registry.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2014-11-11T18:07:31+00:00

    When I implement step 5, it says "access denied".

    I was tring to the above step using administrator account.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2013-10-23T21:08:24+00:00

    I also had this error but I managed to resolve it after following the instructions in the link below.

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/weather-application/e4630db3-50c2-4cc5-9813-f089494a1145

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments