Run-time broker Windows 10 Event ID 10016 Errors

I've been having problems for a few months now, sometimes when trying to open any traditional application, have to wait a few seconds like 5 or 10 before the application launches. At the beginning didn't pay much attention, but started checking the Task Manager which i was able to launch and I could see the application(s) listed on the processes running and then some seconds later the application will launch correctly.
The issue started becoming more common it didn't matter the application, i think just Task manager and the new Windows Apps (Metro) were able to open on that state. I checked the Event Viewer and the only thing showing Error specifically around the same time i was trying to open the application is the Event ID 10016.
I've started doing some research and found several websites and forums reporting similar symptom and some workaround to solve the problem, I was able to identify the application as the Run-time Broker. Basically the same information on must of them as it shows in here: Windows 10 error 10016 from Run-time broker - cannot change - Microsoft Community
I did try that I was able to change Ownership on the Reg keys and able to set the security permission on The Component Services as listed. in my case the Run-Time Broker shows twice and i was able to change the security permission on both to add my user with access to Local Activation marked. But still getting the errors.
Tired of trying to fix it I did reinstall Windows, a fresh Installation. I did it using a new downloaded image with the latest Fall Creators Update as in some forums they notice the problems when they performed update from one Windows Version to another, but surprise the error is still showing in there not even completed installing all the drivers i checked the Event Viewer and keeps popping from time to time, same related to Run-time Broker.
"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}....."
I did try to set the workaround all ran fine still no changes.
Don't know what to do it seems that for must people the workaround just works fine and the Windows Re-installation also works, but not in my case.

Any help will be appreciated

Those Distributed COM errors are a "feature" of Windows 10 (and typical of the quality to expect from this product, one might add). You will see those on any fresh install of Windows 10. There's more than one of these, too. I think it's roughly three or four of those on virgin WinX installs. Note that you can resolve the error by adding proper security permissions. If you look at the full event log entry, you'll see that it's the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) that's denied launch permissions, so that's the user you need to add permissions for.

HOWEVER, while actions like the above work fine to resolve most of those DCOM errors, the situation with this particular one is not so simple: Notice that when you try to edit launch permissions for RuntimeBroker, you'll be greeted with a warning saying that this object has unrecognized or callback security descriptors set, and the only way to edit permissions is to remove those unrecognized objects. The issue here is that heaven only know what the consequences of doing so might be. I have gone down that road at one point, which did indeed resolve the DCOM errors, but instead I saw COM Surrogate crashes popping up at random times that I could not correlate with any activities on the machine. And, no, I am not sure those crashes are in any way related to RuntimeBroker now being allowed to launch. Again, this is Windows 10 we are talking about.

Anyway, long story short, my recommendation would be to leave well enough alone. The issues you are seeing are almost certainly unrelated to those DCOM errors, and there is even a chance that those DCOM errors have no consequences of any sort at all.

Thanks for the reply, it might be true what you said and the error that i have might not be related with the Run-time broker event.
I'll be keeping digging on the system to see if i can find something else.

Regards!

There are many posts on the forum about how to fix these errors. However, I doubt whether people really understand what causes the 'errors' or what are the unknown consequences of trying to fix them. My approach is to ignore these 'errors' and leave it to MS to fix them (if they are capable of doing so).