Runtime Broker Process

Hello guys! I'm not sure what works for me will work for you too but the way I get rid of this problem I have on every startup (not always though) is simply clicking on a photo (in order to open the photo app). I probably should also mention that backgroundTaskHost.exe is also consuming "almost" the same amount of CPU as RuntimeBroker.exe does on my PC simultaneously along with Runtime Broker!

fergiet said:

I thought it was fixed but today it's off and running again so had to stop it in the registry again. Using 37% to 40% of cpu.
With it switched off I see no issues, so it will remain off 'till MS fixes it once and for all.

IDK, it still seems to be working pretty good for me

after disabling "Show me tips about Windows" found on Settings -> System -> Notifications as described by
@xeroichi

a few posts above. I had completely disabled the runtime broker service before that, but this works just as well

tracerman said:

I created this account so I can share the answer to the riddle.

http://lifehacker.com/windows-10-uses-your-bandwidth-to-distribute-updates-d-1721091469

1. Search for “Check for updates” in the Start menu.
2. Under “Windows Update” choose “Advanced options.”
3. Under “Choose how updates are installed” click “Choose how updates are delivered.”
4. Disable the toggle under “Updated from more than one place.”

It's been sharing updates with the world, using a lot of resources. It was using 40%+ on my brand new dell xps 13 i7.

Switched it off and bam.

Edit: It worked initially for me then I launched a twitch app and it went back.

I was having this problem with Runtime Broker as well. I followed your instructions above and it reduced its memory usage from 90% to 2.4%, which is rather absurd on a machine with 16GB. It's been fine for the past 5 minutes. I'll let you guys know if it starts acting up again. Not a fan of sharing Windows 10 making my laptop a community machine to download shared files by default. Urgh. Other than that, I've been enjoying my Windows 10 Pro experience so far.

Antilope said:

Runtime Broker kept thrashing my system, usually using 40% of my CPU although memory use wasn't much, according to the Task Manager. I'm currently using Windows 10 Pro x64 version 10240.

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.)

It worked for me, many thanks. My computer is now as fast as ever. Most helpful.

After reading this topic i was looking at the possibility that windows search causes this problem.

I typed "search" in the search icon.
My language is Dutch so it is possible that het English text is not correct.

First item was: "Searching problems and solving with Windows search"
Click
Next screen: "Solve and help prevent computer problems"
"search and indexing - searching problems and solving with windows search"

Click on NEXT

then windows showed that some problems can be caused by indexing service not having the correct rights to read all files.
Then it asks to run the solution in administrator mode.

This seems to solve my problem so far 2 days later all fine.

This is my contribution.

According to MS answers by Forum moderator, Support Engineer "RuntimeBroker.exe is a Microsoft process to assist Modern UI app permissions". Surely it has relationships with system privileges, that's why we find users that report different causes: photos, searches/indexing, store, apps..
For example, someone else found that Windows Phot App is the culprit:
http://answers.microsoft.com/en-us/i...71751d1?page=2

I found this process running for a few seconds in Windows 10 LTSB (which as you may know it's still in the 10240 build) where the metro, store do not exist; also the Windows Search has been disabled.
However a simple update of Malwarebytes Anti-Malware Corporate 1.80 from the previous release to the up-to-date release (not just the signatures update), triggered that process to appear. However it did not lock the system probably because meanwhile some patch fixed it or the processes in the LTSB does not trigger it heavily in the Corporate edition of that software.

To everyone experiencing delays with this process, I am not sure that disabling the service is the correct procedure.
At least use TaskManager combined with 'What's my computer doing' free utility in order to establish the kind of activity that triggers that process. That utility tracks in realtime which process is using the PC and slowing fades the process name from black to grey over time when the process is no more in use but telling you that it was used 7..8..9.. seconds ago.

As someone else wrote in the MS answers Runtimebroker is just a symptom, not the disease.
So if you have loosely suspects that this or other process is using CPU cycles when you are not supervising the system, enable the CPU Time column under the Task Manager in the Datails tab \ right click one of the head columns such as Name, ID, Status... and choose Select columns; add CPU Time. Then look for a correlation between the processes listed in What's my computer doing, Task Manager and the CPU Time/ RAM used.

Edit: after installing that utility, it will boot at the next computer restart, so if you want to disable it ->> msconfig or another startup manager.

[QUOTE=Antilope;291643]Runtime Broker kept thrashing my system, usually using 40% of my CPU although memory use wasn't much, according to the Task Manager. I'm currently using Windows 10 Pro x64 version 10240.

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.)

I just wanted Antilope to know that I found his instructions above. Thanks dka

What fixed my Runtime Broker problem was:

1. Start "Photos" app
2. Select "Settings" (bottom left corner)
3. In the Sources section remove any network URLs.

Mine was traversing an old ReadyNAS NV+ box that has a bunch of photos. I discovered this by running SysInternals Process Monitor and filtering to show "RuntimeBroker.exe" only. I could see it was traversing each of the directories containing photos.

BTW, I have not tried the registry setting but that seems like a clumsy fix. Turning off the windows update sharing had no effect.

Hope this helps.

John

Thanks for pointing out the Sources setting.