New
#11
Thanks, Ed for this thread. I was driving myself nuts trying to find a fix. Now I am just relaxing and ignoring the 10016 errors in the Event Viewer. Appreciate your work and post on this.
Thanks, Ed for this thread. I was driving myself nuts trying to find a fix. Now I am just relaxing and ignoring the 10016 errors in the Event Viewer. Appreciate your work and post on this.
I've been ignoring these events for years and will continue to do so.
Exactly. Annoyance? Nuisance? Against the purist grain? Very likely. But as stated in post #1 and many other places, save your sanity and just ignore them.
Extremely interesting thread!
Thanks for taking the time to post this important information.
The explanation clarifies many DCOM Events that don't make sense.
What a relief. Now, if MS can put a "Snooze" button on these events, etc.
Good work!
So true....
UPDATE
I wasn't looking for this but I am following another thread:
Windows 10 October 2018 Update rollout now paused and these and similar errors were mentioned so i've copied the posts here "FYI".
If you use Google Chrome I advise to allow Local Activation for 'Users' since Chrome execute in a User role sandbox and otherwise triggers an error every time it is started.
AND
About the 10016 events, mostly RuntimeBroker and Immersive Shell I don't think MS will correct since it's normally non-Microsoft applications (like Google Chrome) that triggers them.
I think I'll still ignore them though.
Last edited by VBF; 20 Oct 2018 at 07:17.