I have exactly the same issue with DCOM Event ID 10016 DistributedCOM.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-JU46CAH\Rahul SID (S-1-5-21-3103493426-1909410407-3242254243-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.
Now I tried fixing this issue using the same method from the Windows 8 forums.
https://www.eightforums.com/threads/...1/#post-135109
This fix worked for Windows 8.1 when I previously had this issue.
However, be warned that when I tried making the exact same attempt in fixing this issue in Windows 10 it completely dismantled my Cortana SearchUI.exe functionality.
I ended up having to do a Windows System Restore as SFC /Scannow did not fix the problem.
In both attempts I tried to modify the registry to add permission in the space of a few days. And then I went to Computer Services and searched for {15c20b67-12e7-4bb6-92bb-7aff07997402} which is associated with the RuntimeBroker. I tried modifying the permissions but it won't let me as it will be greyed out. I tried to force it to work by going to Default option and then back to Customise.
And even when I added my Administrators username the error still showed up in Event Log. Upon restart of the PC SearchUI.exe will fail to work.
Fortunately for me Windows System Restore fixed it for me. In fact I made a system restore point prior to the experiment because I knew if this were to break again at least I can fix it by restoring the computer again.
So far this particular error in the Event Log is incurable. My event log is flooded with this error and this error only. I don't know whether this issue happens across all Windows 10 OS versions. But it is definitely something Microsoft need to fix with a Windows Update hotfix.
This is actually very disappointing. I had a problem with Windows 8.1 Event Log Kernal Error Event ID 2 being triggered when accessing Network Sharing Center. I fixed this with a reformat and installation of Windows 10 only so that I now have DCOM Event ID 10016 error...