10016 Warnings for PerAppRuntimeBroker but Windows Security warnings

Page 3 of 3 FirstFirst 123
  1. csmdew's Avatar
    Posts : 156
    10 Ent 64
       #21

    Try this: go to component services, computers, mycomputer, dcom-conf, and look for perappRuntimeBrooker, properties; go to security and under launch and activation you make the changes under edit. You will add to the list users\computer name. Hope this helps and yes chrome make it come up every time opened.
      My Computer


  2. Posts : 201
    Windows 10 Pro 64-bit
       #22

    csmdew said:
    Try this: go to component services, computers, mycomputer, dcom-conf, and look for perappRuntimeBrooker, properties; go to security and under launch and activation you make the changes under edit. You will add to the list users\computer name. Hope this helps and yes chrome make it come up every time opened.
    Many thanks. Unfortunately, when I try to launch it, I get a message "One or more of the permission entries attached to Registry Value has an unrecognized type and cannot be displayed".
    10016 Warnings for PerAppRuntimeBroker but Windows Security warnings-one-more-permission-entries-attached-registry-value-has-unrecognized-type-ca.jpg10016 Warnings for PerAppRuntimeBroker but Windows Security warnings-greyed-out.jpg
    And then when I launch this activation permission tab, it is completely greyed out! I can't do any editing inside to add or tick the check boxes. Is there a solution for this? Did you have this issue. I believe I tried checking this last year and it was also greyed out and I gave up trying any further.
      My Computer

  3. csmdew's Avatar
    Posts : 156
    10 Ent 64
       #23

    Did u change the ownership in registry first like posted earlier; then u can do the edit.
      My Computer

  4. glnz's Avatar
    Posts : 221
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
    Thread Starter
       #24

    Blazing - after you change the ownership and then do the fix, please advise as to my first post at the very top of this thread. Thanks.
      My Computer


  5. Posts : 201
    Windows 10 Pro 64-bit
       #25

    Absolutely magic, problem solved!
    I followed @FreeBooter steps by changing reg to Administrators (DESKTOP-22C5PHI\Administrators) for both
    CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}

    Then clicked the check boxes for all of them, including Users, just for the benefit of the doubt and Apply.

    After that, next important step is to run Component Services as an Administrator otherwise it may show up as an error in Event Viewer. Then go to DCOM Config PerAppRuntimeBroker and when the Windows Security box pops up you must click Remove for the editing to work! 10016 Warnings for PerAppRuntimeBroker but Windows Security warnings-launch-activation-permission-fix-guide.jpg
    Then after that all you have to do is add Users (DESKTOP-22C5PHI\Users) like shown in my case and then tick all 4 check boxes to Allow and hit ok.

    Immediately, you'll notice the problem goes away, without even needing to restart your PC! I was having previously these warnings not just with Google Chrome and Opera GX but they were triggered with Steam, Zoom App and Lichess unofficial application. And now I have tested that the warnings no longer show up in Event Viewer.

    I also did an SFC /Scannow after this and Windows Resource Protection did not find any integrity violations. Rest assured, this will not mess up your computer! If you have any fears, create a Windows System Restore Point before you proceed. So that way if you do mess up you can always return back to the previous state before any changes were made. Once successfully done, you can now create another manual system restore point so you don't mess up your hard work, in case you need to restore your computer again in future should a new problem arise.

    I'm so glad to have found this proper fix because my advice last year from post #12 to go to WMI\Autologger APPID and setting "Enabled"=dword:00000000 was basically crap! This wasn't the right way of hiding the error as it wasn't correcting the erroneous behaviour. Now I safely returned this back to "Enabled"=dword:00000001 since the problem is now properly fixed and warnings are no longer getting triggered!
      My Computer

  6. glnz's Avatar
    Posts : 221
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
    Thread Starter
       #26

    Blazing - thank you.

    Do we have any idea what the PerAppRuntimeBroker is running?
      My Computer



  7. Posts : 201
    Windows 10 Pro 64-bit
       #27

    Ok, so I have detected that while this certainly fixes the 10016 warnings. I have noticed that ever since doing this, it triggers a third RunTimeBroker.exe to run in the Task Manager background processes.

    But exiting the browser means that this third RunTimeBroker.exe with 0.8Mb does not disappear, it remains there.

    But if I launch Waterfox Classic Web Browser that also triggers RunTimeBroker.exe but after 20 seconds it will at least leave and return with 2x RunTimeBroker.exe. Also after launching anything Chromium, only later after launching Waterfox will the 3rd RunTimeBroker.exe disappear. In other words only Waterfox is able to send the signal for it to leave after 20+ seconds.

    This is a result of this change. As I have experimented that if I remove the Users from Launch and Activation permission in PerAppRunTimeBroker. Then 10016 warning will return, but this time RunTimeBroker.exe will not be triggered with launch of Chromium web browsers, including Steam. I know that this is negligible and doesn't consume much RAM. But why doesn't it disappear from Task Manager? Why does it remain there infinitely?!

    At least with Waterfox/Firefox after exiting the browser the 3rd RunTimeBroker.exe eventually disappears from Task Manager. But with Chromium, Steam, etc this does not.
    @glnz I have no idea why it is running, that's my question. Frankly even Waterfox/Firefox does the same, but it will release from background processes.
      My Computer


  8. Posts : 34
    windows 10
       #28

    BLaZiNgSPEED said:
    Many thanks for finding the solution! I didn't know it is Chromium web browsers that trigger this error/warning.
    Yes, I am getting this. 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-22C5PHI\Rahul SID (S-1-5-21-676720327-1014658904-1421798105-1001) 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.

    I can attest that using Opera GX, does trigger these warnings. But using Waterfox Classic does not cause the error to trigger!
    Can you explain where I have to select the local activation Users name? Is it from the Google Chrome/Opera GX Browser or do I go to Component Services administrative tool area?

    It would be useful if there were illustrations made through print screen pictures or a youtube video that show us how to do this, as not many of us are technically knowledgeable on how to follow these steps. From where do I select generic username for the local activation?

    Kind regards.
    waterfox is based on old firefox so there i no chance it triggers this error. Opera is reskin of chrome so it's expected that it triggers the error.

    to fix the error, there is a tutorial on the first page
    10016 Warnings for PerAppRuntimeBroker but Windows Security warnings

    https://www.tenforums.com/performance-maintenance/107625-distributedcom-error-2.html#post1368395

    do first the registry fix, to grant the rights to edit the configuration to your user
    then open a command prompt
    type dcomcnfg.exe
    then select the view '' details'' for easy reading
    then click on ''computer something'' on the left, until you can select DCOM stuff
    then you search for 'the first ''runTime'' stuff,
    then right click properties and then tab ''security''
    then you modify the configuration to allow hostname\USERS to ''Local Activation permission''
    10016 Warnings for PerAppRuntimeBroker but Windows Security warnings-2021-10-22-14_13_12-services-de-composants.png
      My Computer


  9. Posts : 201
    Windows 10 Pro 64-bit
       #29

    Dear lqlaow,

    Yes, I have mentioned in my previous 2 posts that I have finally solved these warnings following these instructions.

    I'm talking about a new issue, since doing that.. 10016 Warnings for PerAppRuntimeBroker but Windows Security warnings-extra-runtime-broker.jpg

    Basically now as you can see, while launching Opera GX a new Runtime Broker is now running in the background. Something that previously did not occur. Now of-course, this is normal as previously the permission to the COM Server wasn't granted.

    But now the 3rd Runtime Broker is running in the background infinitely without disappearing. Why is this happening? I mention Waterfox and yes you are right that Waterfox does not trigger the error. What I am saying is that when Waterfox launches Runtime Broker will disappear normally after closing the web browser!

    But here with Opera GX or Steam, closing them doesn't end that extra Runtime Broker? Do you notice that? There are no 10016 errors anymore in Event Viewer, that is now solved!! But I am talking about the extra Runtime Broker that gets triggered and do not disappear when ending Steam or Chromium web browsers.
      My Computer


 
Page 3 of 3 FirstFirst 123

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:56.
Find Us




Windows 10 Forums