DCOM error 10016 in event viewer / windows 7 home premium, 64bit

Anonymous
2011-05-05T23:27:34+00:00

I get this error :

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID

{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}

and APPID

{344ED43D-D086-4961-86A6-1106F4ACAD9B}

to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

This error shows up every time I start or reboot my PC. I found out the CLSID is from the IPBusEnum service.

I get the same error in my other windows 7 PC as well. It startet around april 2011...I assume it has to do with some microsoft updates.

What I did so far:

I went into component services and tried to change security settings for IPBusEnum...but everything is grayed out.

I went into registry and changed ownership and permission for this key....still greyed out!

I added NETWORK SERVICE in component service/my computer/properties and gave full permission to everything....still greyed out!

I went into services and changed the status of PnP-X IP Bus.. to Manual so it wouldn't start...still get the error.

I changed service to Automatic...and error went away...but the service changes back to the initial status of Automatic/delayed start after every reboot.

 Before  the SP1 update the service was set to Manual...I don't know why it is on auto/delay now.

I think I tried every solution I could find online, but for me somehow nothing works....

Anybody has the same proplem and found a fix?

Windows for home | Previous Windows versions | Windows update

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 No comments
{count} votes
Answer accepted by question author
  1. Anonymous
    2012-01-04T16:52:41+00:00

    Unfortunately, the link you provided doesn't solve the problem entirely. (It's also for Windows XP. Is there an equivalent Windows 7 article?) It misses the key problem the OP has (and I had)... "I went into component services and tried to change security settings for IPBusEnum...but everything is grayed out."

    The following is what I had to do before I could grant permissions to the COM component:

    1.    Make sure you’re logged on as an administrator.

    2.    Click Start, type regedit in the Search bar, then click regedit.exe

    3.    In the Registry Editor, press CTRL-F, type {344ED43D-D086-4961-86A6-1106F4ACAD9B} and click “Find Next”.

    4.    The first result is located in HKEY_CLASSES_ROOT\AppID. This is the key we need.

    5.    Right-click the key {344ED43D-D086-4961-86A6-1106F4ACAD9B} in the left sidebar, and then press “Permissions…”

    6.    We first have to change the ownership of the key. The current owner is TrustedInstaller. We have to change the owner to Administrators. Therefor, click Advanced. Then go to the tab Owner, select Administrators, check the box “Replace owner on subcontainers and objects”  and press OK.

    7.    Now that we have changed the ownership to ourself (member of the Administrators group), we can change the permissions on the registry key. In the Permissions window, grant Administrators AND SYSTEM Full Control permissions. Then click OK to confirm the changes. In these 8 steps, we have granted the Administrators and SYSTEM account full permissions to the key HKEY_CLASSES_ROOT\AppID{344ED43D-D086-4961-86A6-1106F4ACAD9B}.

    8.    Verify that in this key, the value of LocalService is IPBusEnum

    9.    Click Start, type Component in the Search box, and then click Component Services

    10.    In the Component Services window, go to Computers –> My Computer –> DCOM Config. Right-click IPBusEnum and click Properties.

    11.    Go to the tab Security. In the Launch and Activate permissions section, select Customize and click Edit.

    12.    Select SYSTEM, select the permissions checkbox “Local Launch”. Then click OK to apply the change.

    13.    Done!

    Credit for this solution goes to

    http://www.itexperience.net/event-10016-the-application-specific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server-application-with-clsid-c97fcc79-e628-407d-ae68-a06ad6d8b4d1/

    49 people found this answer helpful.
    0 comments No comments

13 additional answers

Sort by: Most helpful
  1. Anonymous
    2013-05-22T12:41:53+00:00

    Paola, Thank you. This worked on Windws 7 Pro and Windows 7 Home Edition, both 64-bit.  Both were new laptops bought separately from two different manufacturers. within 5 months.

    0 comments No comments
  2. Anonymous
    2013-08-15T04:22:51+00:00

    I added the user from my event errors and granted full local Activation permission but still get the 10016 error for three applications....what now?

    Anybody?

    0 comments No comments
  3. Anonymous
    2014-08-26T23:23:22+00:00

    After you change the permissions in the registry, you will need to restart before you can make the changes in component services.

    0 comments No comments
  4. Anonymous
    2015-02-14T21:44:18+00:00

    I ran across this thread because I have the same error message appearing.  However, I'm not certain of the significance because, when I go to Services.msc, I see that the IPBusEnum service is running.  It was set to Delayed Start.

    0 comments No comments