Runtime Broker Process

Page 3 of 7 FirstFirst 12345 ... LastLast

  1. Posts : 10
    Win10
       #21

    Runtime Broker


    After messing with this for days, disabling everything suggested, (and more) on 3 different machines this thief still keeps stealing CPU time and memory. If a system sets idle for about an hour, task manager reports that it is using up to 99% of CPU time and over 300MB of memory. Like I said everything conceveable has been disabled; cortana, live tiles, notifications, just to name a few. This is on 3 distinctively different machines. Considering todays article in Forbes that reports that Microsoft is planning to take away all user control of updates I'm thinking it may be time to abandon ship and head back to the port of Win7.
    Last edited by flagtrax; 14 Aug 2015 at 20:16. Reason: typo
      My Computer


  2. Posts : 30
    windows 10
       #22

    well i turn the bandwidth thing off to not feed computers on the net
    but the broker still consumes %15 to %20 of CPU cycles
      My Computer


  3. Posts : 7
    Windows 10 Pro x64
       #23

    Win10Pea said:
    well i turn the bandwidth thing off to not feed computers on the net
    but the broker still consumes %15 to %20 of CPU cycles
    Disable it in the registry. It does nothing on mine now.
      My Computer


  4. Posts : 10
    Win10
       #24

    shinitaru said:
    Disable it in the registry. It does nothing on mine now.
    @shinitaru
    I've thought of that, and may try it on one machine, but to me that's akin to a doctor treating the symptom and not the disease. I'd like to know more about the what how and why, and understand it's function, and why Microsoft isn't dealing with the issue, I've seen countless posts on the internet about shutting it down, and I understand that gives some relief, what I'd like to know is what it's purpose is (beyond the articles we've read) if the system can run without it, why does it exist.

    So in the time it took to write this post on the desktop, the laptop task manager showed runtime broker going from 0 (when I ended the task) to 64% CPU time just sitting idle.
      My Computer


  5. Posts : 7
    Windows 10 Pro x64
       #25

    flagtrax said:
    @shinitaru
    but to me that's akin to a doctor treating the symptom and not the disease.
    It is exactly that, but I'm less concerned with the why as I am with the how. When I hear that MS has addressed the issue, I will rethink this solution. Till then, my system is running better and I'm not running the risk of frying my CPU, which was a real possibility. I'm not curious enough to risk my gear.
      My Computer


  6. Posts : 10
    Win10
       #26

    shinitaru said:
    It is exactly that, but I'm less concerned with the why as I am with the how. When I hear that MS has addressed the issue, I will rethink this solution. Till then, my system is running better and I'm not running the risk of frying my CPU, which was a real possibility. I'm not curious enough to risk my gear.
    @shinitaru
    I totally get that. Feeling the heat coming out of the vent on the laptops, and the case fan on the desktop is evidence that more is going on than need be. In the mean time, I have work to do and my systems were working, doing their jobs quite well with win7. For me I think that I need to be assured that all work won't be lost in the shuffle....cheers
      My Computer


  7. Posts : 5,443
    Windows 11 Home
       #27

    shinitaru said:
    When I hear that MS has addressed the issue, I will rethink this solution.
    Well, good luck, this issue exists since Windows 8. Microsoft's solution is to close it and hope for the best.

    Runtime Broker is using too much memory - Microsoft Windows
      My Computer


  8. Posts : 10
    Win10
       #28

    Runtime Broker takeover


    TairikuOkami said:
    Well, good luck, this issue exists since Windows 8. Microsoft's solution is to close it and hope for the best.

    Runtime Broker is using too much memory - Microsoft Windows
    While this adds credence to the fact that this is truly an issue, Even the Microsoft response is incomplete. To quote their page:

    "•Runtime Broker is a Windows process in Task Manager that helps manage permissions on your PC for apps from Windows Store. It should only use a few megabytes of memory, but in some cases, a faulty app might cause Runtime Broker to use up to a gigabyte of RAM or more.
    •If your RAM use is high and your PC is running slowly, an app may be the cause of the problem. Press Ctrl+Shift+Esc to open Task Manager and then, on the Processes tab, check to see how much memory Runtime Broker is using. If it’s using more than 15% of your memory, you probably have an issue with an app on your PC. To stop Runtime Broker from using so much memory, select Runtime Broker in the list, select End task to close Runtime Broker, and then restart your computer."

    1. They address high memory usage, and don't even talk about CPU time. And of course it's not their fault, it's an apps fault. There should be a "trap" for that app!
    2. As I've said before (in many different ways) why deploy an OS with such a horrible bug. This issue has been reported since windows 8! Microsoft deployed windows10 claiming to fix much of previous OS issues.
    3. If their answer is to disable it, or as in this instruction restart it, why is it needed in the first place.
    4. Restarting the pc every 10-15 minutes is absurd, which is what I'd have to do to keep up with Runtime broker's hunger.
    5. If one has to disable key attributes of windows 10, like Cortana, Live tiles, notifications, and more, to keep the system running, what's the point of having it in the first place? Those are the things people are upgrading for.

    For me this OS has gotten way more hype than it deserves. When I first loaded Ubuntu as a dual boot system, (not there now, just so there is no misunderstanding) I had absolutely no issues running it. I'm not saying it was perfect but then again the Ubuntu community is not Microsoft!
    Last edited by flagtrax; 15 Aug 2015 at 08:58. Reason: add a comment
      My Computer


  9. Posts : 34
    Windows 10 Home 64
       #29

    Running at 40% cpu usage here. Just tried the reg edit so will see if that helps. No very impressed with the response from Microsoft.

    Fingers crossed.
      My Computer


  10. Posts : 360
    Windows 10 Pro x64
       #30

    The Runtime Broker was giving me trouble with the last couple of insider builds (10162 & 10240), but once I installed the July 29 release (did an clean Windows 7 install and then upgraded to the July 29 Windows 10 release to get rid of all insider build remnants), my computer is fine and idles most of the time with 0% to 2% CPU usage. For me, Runtime Broker seems well behaved in the July 29 release.
      My Computer


 

  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 08:38.
Find Us




Windows 10 Forums