Windows 10: DistributedCOM Error.

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.

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,

Vaio 7 said:

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.