Event ID 10016, DistributedCOM

This is getting very weird. Without modifying anything whatsoever, suddenly the event is not triggered anymore for one of the Users (the PC has two users) - no event for the last two days.

Hi, I tried this to remove the same error, and it appeared to work fine and the error went away for several boots, but now it's come back again, exactly as before! The procedure seems to have correctly added me as a user with local activation permission (only) to Windows Management and Instrumentation in DCOM Config. I assume that's what it should have done, but the error messages are still there.

The errors are still happening, but only at boot time, often two with the same time stamp.
I can actually change the security permissions on Windows Management and Instrumentation in DCOM Config without DCOMPerm, using the normal interface, is that normal?
Giving local activation permission to myself with DCOMPerm or manually using the UI seems to make no difference to the problem anyway!

In my case, the problem started suddenly in the middle of May. No new Apps installed, no OS or other settings change, no OS update (Windows 10 Pro - 1709), no nothing. As per post #8, the event repeats every 4 hours. I’ve tried all of the different available methods in order to get rid of this event without any success. There is a scheduled task repeating every 4 hours - Task Scheduler Library/Microsoft/Windows/Windows Update/Automatic App Update (automatically updates the user's Windows store applications); I’ve ‘played’ with this task but it didn’t solve the problem either. Upgrading the OS to version 1803 doesn’t solve the problem because it seems to be also ‘inherited’.

A few days ago, I tried as an experiment giving ALL APPLICATION PACKAGES Local Activation permission (only) on Windows Management and Instrumentation in DCOM Config.
I haven't seen the error message since.
Whether this is opening up a security hole I don't know, but it only gives permission to activate, not to launch.
It does seem to be a fix for the error message, but what are people's thoughts on the desirability of this?

Thanks, that's very useful, and a very good analogy!
So I guess Microsoft.Windows.ContentDeliveryManager is trying to activate and can't, whether it's already launched or not, which is what's throwing the error. This may be expected behaviour in some circumstances, as detailed here, but it's still annoying. Regular error messages in an operating system which happen all the time and are supposed to just be ignored, simply make people blasé about the contents of the error logs, and they may well miss errors which really matter!

Nice fix. Finally I'm getting a clean event log again.

Good to hear, but do bear in mind that this is just a workaround, not a fix, and could potentially leave your system vulnerable to security breaches, as has been said.