Seeking Advice for DistributedCOM Error 10016  

Windows 10 Pro - Version 20H2 (OS Build 19042.867)
FWIW: I've avoided KB5001330 based on all the talk online.

Howdy Folks,
(Please advise if I am posting in the wrong forum.)

My monitor just went blank and a quick check of my desktop indicated it was still running. A simple Off/On of my monitor's power switch brought it back to life.

My Event Viewer gave me "DistributedCOM Error 10016", and a quick Google Looksee tells me this: "DistributedCOM Error 10016" is common and may be NBD, but it can be fixed.

I'm interested in any thoughts/comments/suggestions.

TIA to all who read this post and to those who reply!

@jdUnionngarden

According to Microsoft...

These events can be safely ignored because they don't adversely affect functionality and are by design. It's the recommend action for these events.

https://docs.microsoft.com/en-us/tro...accessing-dcom



We all get those errors, and we ignore them. They have nothing to do with your monitor going blank.
I would probably check the Sleep setting for the monitor.

@Ghot

Thanks for the link and comment.

I will be able to sleep tonight!

jdUnionngarden said:

@Ghot

Thanks for the link and comment.

I will be able to sleep tonight!

Just ignore these errors. There is a good chance of causing more problems if you try to 'fix' them.

jdUnionngarden said:

Windows 10 Pro - Version 20H2 (OS Build 19042.867)
FWIW: I've avoided KB5001330 based on all the talk online.

Howdy Folks,
(Please advise if I am posting in the wrong forum.)

My monitor just went blank and a quick check of my desktop indicated it was still running. A simple Off/On of my monitor's power switch brought it back to life.

My Event Viewer gave me "DistributedCOM Error 10016", and a quick Google Looksee tells me this: "DistributedCOM Error 10016" is common and may be NBD, but it can be fixed.

I'm interested in any thoughts/comments/suggestions.

TIA to all who read this post and to those who reply!

Late to the party, but all the above advice is more than correct. These are annoying, but benign. They've been a mental thorn in the side for years, and they just need to be ignored as best as possible.

Some time back, over a year, MS moved them from "Error" status to "Warning", and at least that got them out of your face.

HTH

Wrote a sticky post about this issue a while back, but it's still relevant: Why Certain DCOM 10016 Events Don't Matter.
HTH,
--Ed--

There are hundreds of posts on this forum about that particular error. You can certainly spend some time reading through them bit it's because of this error that I learnt to ignore these errors.

Also because it's a desktop pc, it would be better to just turn your computer off at night. rather than sleep it. You have an SSD so it shouldn't take too long to boot up.

Sound advice................ ^^^^^^^^^^^^^^