Getting this error even after clean install!

There seem to be no way getting rid of this error. I even did a clean install tonight with the latest windows 10 iso!
Any idea why?

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
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.

Sorry to bump this up again, but at least need to know if this is a general problem in win10 or if its just me!

I can confirm it is a general problem in W10. Seems to happen once on every restart, even from sleep. I've decided to ignore it and eventually it will be sorted.

In general, I find the latest build to be much less error prone, several of the errors I used to get in Event viewer have simply gone away.

rezpower said:

Sorry to bump this up again, but at least need to know if this is a general problem in win10 or if its just me!

Hate to say it but it may be your computer. I've Upgraded 4 Desktops and several Notebooks to Win10 and not seen that issue. Newest machine is from April 2014 and oldest about 2008. A couple were 32-bit and the rest 64-bit. Three were Pro and the rest Home.

rezpower said:

Sorry to bump this up again, but at least need to know if this is a general problem in win10 or if its just me!

Yes, it is a general problem in Windows. (In fact, it existed in Windows 7 as well.)

At this time all Windows 10 installs (no exceptions) suffer from at least three problems:

1. Error 10016, Distributed COM (the one you mention)
2. Schannel error 36870 "A fatal error occurred when attempting to access the TLS server credential private key. "
3. Error 7031, crashing Sync Host services.

They might be triggered by using some windows feature, meaning that machines that don't use that feature might not manifest this issue, but the problems are there nevertheless.

The first two trace back to pre-Windows 10 times. The Internet seems to be ripe with numerous "solutions" for these problems, but most of them simply don't work.

Well I killed my older windows trying to repair this error. The problem seem to be coming from RuntimeBroker.
After I tried to fix the start menu and search would not work and I decided to do a clean install. Bump the same errors
were back after clean install! weird!

@AndreyT

Thanks for your reply in fact I also have the error 7031, crashing Sync Host services.
now that I know they are not only on my system I will let them alone :)

AndreyT said:

At this time all Windows 10 installs (no exceptions) suffer from at least three problems:

1. Error 10016, Distributed COM (the one you mention)
2. Schannel error 36870 "A fatal error occurred when attempting to access the TLS server credential private key. "
3. Error 7031, crashing Sync Host services.

The first two trace back to pre-Windows 10 times. The Internet seems to be ripe with numerous "solutions" for these problems, but most of them simply don't work.

I haven't yet seen those problems on the machines I've Upgraded.

Berton said:

I haven't yet seen those problems on the machines I've Upgraded.

That probably means exactly that: you haven't yet seen them. The Sync_Host error is such a prominent, mainstream, signature "feature" of Windows 10 that it is probably safe to say that if your machine does not have it, there must be something very very very wrong with the install.

And as I said, they might be triggered by using some Windows feature or some specific set off settings. OneDrive, Fast User Switching, Remote Desktop, network sharing type (Homegroup vs. passwords), signing in with local account vs. online account etc. etc. etc. The possibilities are too numerous to say for sure.