Windows 10: Event 10016, DistributedCOM

Page 1 of 2 12 LastLast
  1.    07 Aug 2015 #1

    Event 10016, DistributedCOM


    Since upgrading to Windows 10, my error log is flooded with this message. Over 520 incidents in the past week. The instructions provided for that error in Windows 8 do not work with 10, since it is impossible to grant full permission to the administrator account via RegEdit.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160}
    and APPID
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
    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.
      My ComputerSystem Spec

  2.    12 Aug 2015 #2

    same here


    same here, but not immediately after upgrade, but two days later after a reboot.

    any news already?
      My ComputerSystem Spec

  3.    12 Aug 2015 #3

    Event 10016, DistributedCOM


    bousix said: View Post
    same here, but not immediately after upgrade, but two days later after a reboot.

    any news already?
    I'm having the same problem but this is only one of quite a few I now have listed in my event viewer (I've only just discovered this facility existed!) My upgrade to Windows 10 hasn't been great and I'm now left with turning off power saving as my Dell Inspiron 7548 freezes if it goes into this mode. I then have to power down/up - which amazingly doesn't result in any need to safe boot. Also, when I try to shut down, the power stays on to the on/off button and the keyboard lights!

    Immediately after the upgrade I identified an issue with the graphics driver (AMD) which was causing the BSOD. Obviously there's still a problem but at least I'm able to use my PC most of the time. Not sure if this is related to the logs in the event viewer.
      My ComputerSystem Spec

  4.    13 Aug 2015 #4

    Event 10016, DistributedCOM


    I'm also seeing these errors in the Event Log, hundreds of them.
      My ComputerSystem Spec

  5.    15 Oct 2015 #5

    Hi !

    Exact same problem here! Any solutions or ideas ?

    Bye!
      My ComputerSystem Spec

  6.    16 Nov 2017 #6

    because I am sure that this thread will be found again now that those dcom 10016 errors are back, I will link to another thread where I posted my solution.
    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Page 34 - Windows 10 Forums
      My ComputerSystem Spec

  7.    17 Nov 2017 #7

    Just ignore these errors and wait for MS to fix them. There are solutions on this forum but I doubt anyone really knows the implications of trying to fix these errors.
      My ComputersSystem Spec

  8.    18 Nov 2017 #8

    Hi,

    What implications would that be ?
    It's easy enough to fix if you follow the steps correctly:

    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

    No need to wait and hold your breath. MS can't be bothered with errors that appear to be random or caused by third party software really.

    Cheers,

    EDIT: Just noticed the link was posted already.
      My ComputersSystem Spec

  9.    18 Nov 2017 #9

    fdegrove said: View Post
    It's easy enough to fix if you follow the steps correctly
    That would be nice now, wouldn't it? Unfortunately it turns out that Microsoft has made a complete mess out of things in Windows X, with the result that not all DCOM errors can be fixed. One may note in passing that the information given in the error messages you see in Event Viewer may or may not be accurate.

    fdegrove said: View Post
    MS can't be bothered with errors that appear to be random or caused by third party software really.
    Nonsense.
    First, some of these error messages appear in brand-new virgin installations of Windows 10.
    Second, once users have fixed permissions to resolve some of the errors, they come back after major Windows updates since Microsoft reverts permissions to the previous state.
    Third, among the "third party applications" causing these errors are signature Microsoft products, such as Microsoft Office.

    Bottom line, Windows 10 is a disgraceful mess, with no indication of things improving. Chances are that Windows 10 and its successors will remain at beta quality for the foreseeable future. Certainly this will not change as long as people not only put up with but even defend this state of affairs.
      My ComputerSystem Spec

  10.    19 Nov 2017 #10

    Hi,

    That would be nice now, wouldn't it? Unfortunately it turns out that Microsoft has made a complete mess out of things in Windows X, with the result that not all DCOM errors can be fixed. One may note in passing that the information given in the error messages you see in Event Viewer may or may not be accurate.
    What to say ?
    Personally I have not seen a DCOM error that could not be resolved. Maybe we could help should you care to detail the errors experienced by you ?
    As stated before I run 8 FCU installs and they're all DCOM error free.

    Cheers,
      My ComputersSystem Spec


 
Page 1 of 2 12 LastLast

Related Threads
The only constant errors I get when I reboot are these four, that all share the same ID of 7031. The Contact Data_Session2 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000...
Event 441, Kernel-PnP in BSOD Crashes and Debugging
Hi All, This problem shows when i've upgraded to WIndows 10, due to this problem. i've revert back to windows 7. This was not encountered while using windows 7. It seems like the system was not able to detect the audio output even thou its...
Windows 8.1 64bit PRO updated to Windows 10 PRO - intel rst 14.5.2.1088 by station-drivers I see this irstrtsv error in the Event Viewer. id event 0 The description for Event ID 0 from source irstrtsv cannot be found. Either the...
ESENT errors in my Event Log in BSOD Crashes and Debugging
On Windows 10 Pro x64 I am getting quite a few ESSENT errors in my Event Log after I start up W10. I see Event ID's 413, 455, 488, and 489. If these are indicative of a problem does anyone know the fix? Thanks
Watch the 10 launch event in Windows 10 News
https://www.youtube.com/watch?v=NfveyXCsiA8&feature=youtu.be
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 03:08.
Find Us