Event ID 10016 - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

I thought it worth mentioning for some with the "RuntimeBroker" problem to mention what worked for us. For myself I took ownership of the CLIDs and added my user name. I then restored ownership to the original owner. I had a few sporadic errors after that for a while and then they seemed to disappear. I wondered if Microsoft had finally fixed the original problem. Then I start to use Cortana and boy do the  DCOM 10016 errors flow forth. I had problems in the original 10 upgrade because I had Media Center, and other errors seem to come from changing the computers name and other problems with homegroup.

That would be my interest too, but sometimes you have to cut your losses. I never did figure out how to get the infuriating temp profile problem to stop happening in older versions of Windows (fortunately, I've never seen it in Win8/Win10), just how to undo it. Fortunately, it only happened a few times a year.

On retrospect, it's kind of funny that you bring it up in the context of this DCOM issue, which is another intractable one where I learned to stop worrying and love the bomb. I really do hope MS fixes it though, since I sigh every time I open up Event Viewer.

I appreciate your "Method 1" info but that is really to recover your account after  you've been totally locked out. My interest is to not have the problem in the first place.  A key phrase in the "Method 1" text is, "Windows might not read your user profile correctly, such as if your antivirus software is scanning your computer while you try to log on." So that is what leads me to believe that this may be related to the flurry of errors that Windows 10 generates upon reboot. The constant furious effort by Windows to restart failed services upon startup is possibly the kind of activity that would interfere with Windows being able to read your profile.

And you don't need any anti-virus software or anything else installed to get the flurry of system failures. Have anybody you know with a Windows 10 machine look in his/her Windows System event log and filter for just the errors. You'll find everyone has a ton of them. This is in part because Windows 10 (and Windows 8 and 8.1 apparently) comes right out of the box with at least two DCOM services that have insufficient permissions to start. One of them is "RuntimeBroker" and the other one has something to do with Cortana (I can't remember the specifics). Heaven help you if you turn on Cortana, by the way - that will be the start of a new series of headaches that I don't even want to discuss here.

The thread I referenced in my earlier post on this thread has some instructions for eliminating these service-permission problems (and the system errors they cause), but the procedures are very dangerous because they involve changing ownerships and permissions on crucial registry keys and on the services themselves. So you really need to know what you're doing and even then it's dangerous and parts of the instructions are vague so you have to improvise. I managed to eliminate the startup errors associated with "RuntimeBroker" and since then my machine has not logged me in with a temporary profile but I've only tried it a few times so there's nothing conclusive here.

That infamous "temporary profile" problem dates back to at least Server 2003 though. You can remedy it with Method 1 here. There's no data loss, it goes back to the way it was.