Windows 10: DistributedCOM Error. Solved

Page 2 of 2 FirstFirst 12
  1.    1 Week Ago #11

    Good explanation on the DCOM & RPC stuff, Wynona. Nice job!
    --Ed--

    PS: I still have a paid-for copy of SpinRite sitting in my little tub 'o USB flash drives, right in front of me.
      My ComputersSystem Spec


  2. Posts : 79
    W7 x64 & W10 Pro x64 (Dual boot)
       1 Week Ago #12

    Hello,

    Although I could fix any potential 10016 errors with all previous builds, when I realized that I would have to do it with every new build I abandoned the usual procedure and found an easiest way. What's this? Well it's simple, just force Event Viewer not to log 10016 events. It's better and you are not potentially opening new security holes with the CLSID and AppID and Component services method. I'm still on version 1709 but it should work with build 1803 too.
    If interested let me know and I'll drop some extra lines here on how to proceed.
    Edit: see if this helps with your 10016 error.
    Open Regedit as admin go to HKLM\System\CurrentControlSet\Control\WMI\Autologger then
    Locate {1B562E86-B7AA-4131-BADC-B6F3A001407E} which is what your Event Viewer is reporting, it could be under System or Applications, or other branch, you should be able to locate, and at the right pane there is an entry mentionning enabled dword 1.
    Select it then Click on Edit - Modify and change that value to 0.
    Reboot pc.
    Now the error should not be logged in Event Viewer as we told Windows to ignore it.
    Enjoy!

    Cheers,
    Last edited by Vaio 7; 1 Week Ago at 16:07.
      My ComputerSystem Spec


  3. Posts : 73
    Windows 10 Home/64bit -Version 1803-Build 17133.1
    Thread Starter
       1 Week Ago #13

    I solved the DCOM Error.


    I first made sure I had an entire backup of my whole Registry and could restore it through command prompt in advanced options. Once I verified I could reinstall the whole Registry in the Recovery Environment, I just deleted the Guid alphanumeric codes from the registry wherever they showed up (showed up in three different spots) and rebooted the computer to have an error free log!

    Click image for larger version. 

Name:	log clear.JPG 
Views:	0 
Size:	56.8 KB 
ID:	184062


    As far as I could tell, the errors were being generated because random segments of code were left over in the Registry. Since I don't run a registry cleaner (never trusted them; and still don't) I swept the random segments of code out in short order with the delete command myself.


    You must be very careful when using the command prompt in the recovery environment when dealing with the registry because you can delete things that you would normally not be able to delete.


    I'm marking this solved.
      My ComputerSystem Spec


  4. Posts : 73
    Windows 10 Home/64bit -Version 1803-Build 17133.1
    Thread Starter
       1 Week Ago #14

    Vaio 7 said: View Post
    Hello,

    Although I could fix any potential 10016 errors with all previous builds, when I realized that I would have to do it with every new build I abandoned the usual procedure and found an easiest way. What's this? Well it's simple, just force Event Viewer not to log 10016 events. It's better and you are not potentially opening new security holes with the CLSID and AppID and Component services method. I'm still on version 1709 but it should work with build 1803 too.
    If interested let me know and I'll drop some extra lines here on how to proceed.
    Edit: see if this helps with your 10016 error.
    Open Regedit as admin go to HKLM\System\CurrentControlSet\Control\WMI\Autologger then
    Locate {1B562E86-B7AA-4131-BADC-B6F3A001407E} which is what your Event Viewer is reporting, it could be under System or Applications, or other branch, you should be able to locate, and at the right pane there is an entry mentionning enabled dword 1.
    Select it then Click on Edit - Modify and change that value to 0.
    Reboot pc.
    Now the error should not be logged in Event Viewer as we told Windows to ignore it.
    Enjoy!

    Cheers,

    Although your method is eloquent; I choose to see when all event log errors are generated. Hiding them isn't the same as solving them. Ultimately, when you choose to hide event ID 10016; you are creating a risk in and of itself. In other words, if you can't see the nature of why the error occurred (which can be detrimental) it is the same as not shutting down the DCOM service altogether.


    That is why most peoples posts that I come across when they are talking about DCOM errors; they are in general agreement that Event ID DCOM 10016 is usually harmless. I myself, still like to see why they are generated in the first place.
    Last edited by EyeInTheSky; 1 Week Ago at 17:23. Reason: Correction
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
DistributedCom 10016 permissions event error in Performance & Maintenance
This is a repeating error since the 1709 update. I edited and applied the permission change according to description posted in one of these subforums. That solved that particular application CLSID and APPID Another with a slightly different ID...
I do THANK all whom has helped me on my memory DUMp Error it was bad memory!!T This has happened serval time this month so far Now I have one more BSOD error details in ZIP thanks for all the Help :( Error 9/22/2015 3:40:32 PM...
Event Viewer DistributedCom error in BSOD Crashes and Debugging
I have been experiencing regular PC freezes over the last few months and have only recently discovered the Event Viewer in an attempt to identify the culprit, (forgive me I am a novice PC user!). The freezing is a separate issue, but this morning...
Hi, Is this something I should be concerned about ? I've tried the following solution to no avail my event viewer is still flooded with this error LogName: System Source: DistributedCOM EventID: 10016 Immersive Shell
Bluetooth DistributedCOM error? in Drivers and Hardware
Hi all, running Windows 10 Pro and I have a pretty clean event log except for 10010 DistributedCOM errors that keep cropping up randomly (to me). The offending GUID appears to be {DABF28BE-F6B4-4E40-8F40-C4FB26F3116C}, which is Bluetooth. I...
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 19:22.
Find Us