what is runtime broker, and why does it use so much memory?

Anonymous
2012-10-28T14:43:19+00:00

in task manager there is process called Runtime Broker. and it uses over 600 MB of my ram. putting my average usage at 60% on my 4 gig laptop. not noticed any performance issues yet. just a lot memory being used. makes me think of windows vista almost bc it had same issue in past. it would use all system resources.

Windows for home | Previous Windows versions | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

134 answers

Sort by: Newest
  1. Anonymous
    2015-08-28T07:53:35+00:00

    Hi,

    Things have moved on, (three years for a start), I have just installed Windows 10 and 'runtime broker' is hogging and using massive amounts of CPU and memory. I have 4ghZ of CPU and 12 GB of RAM.

    I have now had to 'end process' of this twice. In each case my overtaxed system came back to life with no noticeable side effect.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-08-23T07:32:31+00:00

    in task manager there is process called Runtime Broker. and it uses over 600 MB of my ram. putting my average usage at 60% on my 4 gig laptop. not noticed any performance issues yet. just a lot memory being used. makes me think of windows vista almost bc it had same issue in past. it would use all system resources.   

    Found the solution to the problem:

    http://www.tenforums.com/general-discussion/7907-runtime-broker-process.html

    Runtime Broker is a service called Time Broker, which can be disabled through editing the registry.

     Right-click on the Start Menu Icon. Go to RUN and type regedit.exe and select OK.

    Find the following entry:

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000003

    Change the 3 to a 4.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000004

    4 is Disabled, 3 is Manual and 2 is Automatic startup.

    Before editing, the original value was 3. Set to 4 to disable. Just change the 3 to a 4 through the MODIFY menu selection, exit regedit and reboot your system.

    After this edit, Runtime Broker no longer runs and the CPU at idle is now only 0 to 1 or 2 percent.

    No adverse affects after disabling Runtime Broker on my system. (ADDITIONAL NOTE: Disabling Runtime Broker will prevent apps from the Microsoft Store from running.)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-08-11T04:49:47+00:00

    I have the same problem with Runtime Broker in ODS windows 10. I just closed it and I'm going to restart. I figure it is my security software that triggers it also as others have discovered.

    The thing is that windows has its own security software. Another app like Norton or McAfee is superfluous. I got McAfee free with my ISP. I'd had issues with the Norton and didn't renew.

    Even if you close it in the task manager window Runtime broker starts itself again burning more CPU than before.

    I guess the only thing to do is uninstall my McAfee, or perhaps return the computer to 8.1 before the month trial is over and OS 10 becomes permanent.

    Actually I just developed this problem with Runtime Broker after upgrading to Windows 10. I find window 10 ripe with problems. Despite the fixes for them that make them selves available with a search on the internet, more problems apparently keep popping up.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-08-09T19:03:46+00:00

    in my case, this solution is not helpful.

    Whenever I interrupt the process "Runtime Broker", it after a few minutes back running again bringing the memory usage and CPU usage increases to maximum levels, making the system unstable and terribly slow.

    Please fix! This issue is becoming very annoying ... rather I go back to the old 8.1

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-08-08T02:57:47+00:00

    I see this problem is older than I thought. I never had a problem with this until my WIN 10 upgrade any ideas?

    Was this answer helpful?

    0 comments No comments