no i use just start10 without UxTheme Signature Bypass, there's no aeroglass yet for 1709 version

i fixed 1709 FCU 10016 runtimebroker error with this utility: PowerRun v1.1 (Run with highest privileges)

163862

adding just system doesn't help, it fixes opera,chrome,vivaldi launching error...

i fix DCOM 10016 rantimebroker permission error but new FCU update performance wasn't perfect and i switched to old 1703 build which is working more than fine without any bugs, i will wait 1-2...

i tried every possible combination and only adding users or everyone in runtimebroker launch and activation permissions fixes dcom 10016 runtimebroker error, at least for my system, here's more...

because there's some registry permission errors in new build, every chromium based browser starting from 59 chromium build gets 10016 errors after every launch, i still use 38 opera because Direct...

without adding Users in Launch and activation permission tab gives DCOM errors, after installing opera 49 beta build and adding users problem is fixed, i think it's microsoft fault and new update is...

i also have two runtime broker since 15063 build, now i changed Launch and activation permission and see how system will behave in long run ,also system file in task manager makes heavy disk scanning...

there's lots of DCOM 10016 runtimebroker errors in new Windows 10 FCU build:
159190

it mainly appears after opening all the latest chromium browsers (opera, chrome,vivaldi) i think Unavailable...