I've been getting errors 10016 and 10010 since the Anniversary Update. I found a variety of potential fixes but they either require me to give more permissions to DCOM or suggest (maybe) turning off DCOM would fix it. My problem is 2 fold; I have no idea if I want it on or off. Forgive my ignorance. From what I read, turning it on connects me to a network of some kind which I'm not sure I want to be connected to with my copy of Windows... Although, if I understand right, it shouldn't matter. It's more of a local network meant for businesses. I still fear what I cannot understand, though, which brings me here. Or, I worry that if I turn it off entirely it will shut down some necessary system service or something. I figured I'd reach out to you guys to see if we could figure it out. The last thread I started brought about a lot of helpful answers and discussion to my problem. Event ID 10010: Spoiler The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Event ID 10016: Spoiler The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
You're right, all the (epic) threads on this never-ending issue involve things like permissions changes. These changes are obscure enough that they could cause unforeseen problems down the road that you'd never realize were related. I'd rather avoid that, so I just created a custom view of the System log that filters out these unimportant 10016's so that I never have to see them.
I disabled DCOM yesterday and the computer wouldn't boot up just went to a black screen with spinning dots. Once re-enabled it booted in fine so make sure you have an image or a restore point or you know how to re-enable it from cmd using an installation disk