Event ID 10016, DistributedCOM

Page 1 of 5 123 ... LastLast

  1. Posts : 72
    Windows Home Premium v22H2 64bit OS Build 19045.4291
       #1

    Event ID 10016, DistributedCOM


    Every time the PC starts I have the following error.

    Log Name: System
    Source: Microsoft-Windows-DistributedCOM
    Date: 25/05/2018 07:35:47
    Event ID: 10016
    Task Category: None
    Level: Error
    Keywords: Classic
    User: Home-PC\User
    Computer: Home-PC
    Description:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
    {8BC3F05E-D86B-11D0-A075-00C04FB68820}
    and APPID
    {8BC3F05E-D86B-11D0-A075-00C04FB68820}
    to the user Home-PC\User SID (S-1-5-21-4023029420-2456169105-2834210191-1002) from address LocalHost (Using LRPC) running in
    the application container Microsoft.Windows.ContentDeliveryManager_10.0.16299.15_neutral_neutral_cw5n1h2txyewy
    SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723).
    This security permission can be modified using the Component Services administrative tool.
    Event Xml:

    I have tried all the usual fixes including added Local to my user name in the Security settings for Windows Management & Instrumentation but the error still occurs.

    I am aware of the post at the beginning of the Forum explaining the information from Microsoft about DCOM errors being the norm but the MS fix doesn't include the CLSID or APPID of what I am seeing. Any clues to what I can do next to resolve the problem.
    Thanks
      My Computer


  2. Posts : 2,450
    Windows 10 Pro x64
       #2

    Hi @parsonm
    To solve COM errors, if you don't follow the Microsoft note, get a cli utility by Microsoft called dcomperm.
    Its source code is included with the Microsoft Windows SDK for Windows 7 and .NET Framework 4.
    The project source directory is:
    C:\Program Files\Microsoft SDKs\Windows\v7.1\Samples\com\fundamentals\dcom\dcomperm

    If you cannot or don't want to compile it yourself, you can download it from here. It is included in this zip file, along with some other stuff.

    Once you have it, use a program like PowerRun or execTI and open a command prompt as TrustedInstaller.
    Run dcomperm with the appropriate switch (dcomperm /? to see the switches) and give Local Activation permission for the APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the SID S-1-5-21-4023029420-2456169105-2834210191-1002


    EDIT: The command you need to run is (don't forget to run from a command prompt as TrustedInsraller):

    Code:
    DCOMperm -al {8BC3F05E-D86B-11D0-A075-00C04FB68820} set "Home-PC\<UserName>" permit level:la
    where <UserName> = the name of the user with SID S-1-5-21-4023029420-2456169105-2834210191-1002
    To get the <UserName>, if you don't already know it, type the following command:
    Code:
    wmic useraccount get name,sid

    Important note:
    Please mind, that the solution should be applied after every Windows feature update (like 1803 and on), as the update resets the permissions to DCOM components!!!
    Last edited by ddelo; 26 May 2018 at 03:31.
      My Computer


  3. Posts : 4,224
    Windows 10
       #3

    Good solution information, Dimitri (@ddelo). Thanks for providing help for the "terminally OCD!"
    --Ed--
      My Computers


  4. Posts : 2,450
    Windows 10 Pro x64
       #4

    EdTittel said:
    Good solution information, Dimitri (@ddelo). Thanks for providing help for the "terminally OCD!"
    --Ed--
    Glad I could help Ed.

    Especially for you, it's a return for your time+effort saver post!!

    If I could be of any any additional assistance (to the "terminally OCD"), please ask. I have spent lots of hours on this issue and I had some good help (Dick @f14tomcat )
      My Computer


  5. Posts : 72
    Windows Home Premium v22H2 64bit OS Build 19045.4291
    Thread Starter
       #5

    Event ID 10016, DistributedCOM


    HI ddelo,

    Thank you for taking the time to respond.
    I downloaded the dcomperm zip file and power run and unzipped them both. When I click on the exe file for dcomperf it opens a window and gives all the options. Click on the exe for power run and I have the screen as per their website .I then added the dcomperf entry into power run. However, when I open the command prompt in power run to add the code that you show, the response is that the software doesn't recognise the DCOM element. Can you confirm what entry in the command prompt I should be adding your code to as when I activate the command prompt in power run, the text in the command window shows the path to power run. I presume I should change this. Is it just a question of editing the command prompt? Or am I not doing something correctly?

    Thanks
      My Computer


  6. Posts : 72
    Windows Home Premium v22H2 64bit OS Build 19045.4291
    Thread Starter
       #6

    Event ID 10016, DistributedCOM


    Hi Ed,

    I note your comments re OCD.

    I am not a professional and I am one of the unfortunate people who upgraded a working Windows 7 PC to Windows 10 and have regretted it ever since. I have had to deal with numerous problems and use forums like this to help resolve any issues that occurred. In fact the only issue I now have is this DCOM error.

    I recently upgraded to Version 1803 build 17134-48 and that was another big mistake. The upgrade appeared to run its normal course. The next day, the first user logged on fine but then other users passwords were deemed to be incorrect. The only way to overcome this was the restart, which cured that problem. However, the day after the PC totally failed to load beyond one of MS Windows pictures - no prompt for user or password. Restarts failed totally. The only way out that worked was to revert to the previous version (1709). Reading forums I understand that there is a newer version available but they all said that you should try to correct any existing problems you have before attempting another upgrade. Hence the request here for help.

    Am I suffering from OCD, I don't think so, I am just cautious of what MS is now producing and wary of doing anything that I cannot get out of. Because I don't fully know what the DCOM error I posted here is saying and how it effects the operation of the computer, I thought I would ask for help. It is ok for MS to say there is no need to worry as it happens a lot but if you took your car to a garage with what you thought was a serious problem, and a mechanic said don't worry they all do that, you wouldn't be a happy Bunny!
      My Computer


  7. Posts : 2,450
    Windows 10 Pro x64
       #7

    parsonm said:
    HI ddelo,

    Thank you for taking the time to respond.
    I downloaded the dcomperm zip file and power run and unzipped them both. When I click on the exe file for dcomperf it opens a window and gives all the options. Click on the exe for power run and I have the screen as per their website .I then added the dcomperf entry into power run. However, when I open the command prompt in power run to add the code that you show, the response is that the software doesn't recognise the DCOM element. Can you confirm what entry in the command prompt I should be adding your code to as when I activate the command prompt in power run, the text in the command window shows the path to power run. I presume I should change this. Is it just a question of editing the command prompt? Or am I not doing something correctly?

    Thanks
    Start PowerRun. You don't need to add decomperm in PowerRun.
    Within PoweRun open a command prompt.

    Event ID 10016, DistributedCOM-powerun.png

    In the command prompt change to the folder where dcomperm resides. (for example if it's on your desktop type CD C:\Users\<Your UserName> \DESKTOP). When you get to the folder where dcomperm is, run the command I provided for dcomperm.

    Event ID 10016, DistributedCOM-dcomperm.png

    Caution
    Running programs (command prompt or any application) with the use of PoweRun (or ExecTI) should be done with EXTREME caution, as you run your applications as TrustetdInstaller or SYSTEM. Running programs as either one of these users, means that you play God!!!... and have access to vital components of the Operating System. If you’re not sure on the actions you take don't take them. You must be extremely careful, as you might damage your installation.
    Last edited by ddelo; 28 May 2018 at 13:39.
      My Computer


  8. Posts : 9
    Windows 10 Pro x64
       #8

    I’m facing exactly the same problem (since about three weeks ago) but with one additional ‘feature’: the event is triggered off once every four hours. Assuming, for example, the event occurs at 03.00 PM, turning OFF the PC and turning it ON again two hours later (for example) doesn’t trigger the event; it’s going to be automatically triggered off again at 07.00 PM.
    Turning OFF the PC and turning it ON again, not two hours later but at 07.00 PM or later instead, triggers the event immediately.
    I’ve tried different methods (including the ones mentioned here) in order to get rid of this event without any success. Virus or malware seems to be out of question (I couldn’t detect the existence of any virus, malware, etc.).
      My Computer


  9. Posts : 72
    Windows Home Premium v22H2 64bit OS Build 19045.4291
    Thread Starter
       #9

    Event ID 10016, DistributedCOM


    Hi ddelo,

    Thank you for the additional information. I have tried it a number of times and on each occasion I see the response:-

    INVALID LEVEL argument
    Syntax: dcomperm <option> [...]

    This happens when I either copy your code line or type it in copying your info. Looking at the options in dcomperf the format looks correct. Any suggestions?

    Thanks.
      My Computer


  10. Posts : 2,450
    Windows 10 Pro x64
       #10

    Try this:
    DCOMperm -al {8BC3F05E-D86B-11D0-A075-00C04FB68820} set "Home-PC\<UserName>" permit level:l

    Is it possible to post the exact command you're trying and gives the error?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:25.
Find Us




Windows 10 Forums