Windows 10: Runtime Broker Process

I don't use Windows Search, and have Defrag and Optimize drives Scheduled Optimization turned off.

I just upgraded to the new Windows 10 Threshold 2 v1511 build 10586 and it set Windows Search and Drive Optimization back on.
This started RuntimeBroker.exe running constantly at 20% CPU.

I disabled Windows Search and unticked Scheduled Defrag, rebooted, and while the RuntimeBroker.exe started, it is no longer thrashing the CPU.

 

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.

 

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.

 

Hi,

I'm no techie, however I 'upgraded' to windows 10 some time ago. I noticed that my machine was locking up. Eventually I discovered that Runtime Broker was upping my CPU to 100% thereby making my PC freeze.
I got into the habit of ending the process many times a day. I also worked my way through all the 'solutions' outlined. Some worked in the short term, one worked until an update changed things again.
I eventually went back to windows 7.
I also have a NAS server and thousands of photos. IF it was simply a matter of let it index everything then it would be ok, that would have been ok. I gave it chance, didn't help.
People mention various cures and various symptoms. In my case a 4ghz CPU was at full throttle, 16GB of RAM was coping.
This is beyond understanding, how can MS not be doing something? IF they blame some errant app, then tell us and let us switch it off.
My only fix was disabling all the apps. What is the point then?

 

Hei friends, I am really in panic! My computer is always doing something when is idle. I can hear the fan, but when I logon and check the processes I see only WMI Provider Host and Runtime Broker going down from high CPU load to 25%. But it is still a lot when I do nothing.... I really need monitor and log activity and connections of my Windows 10 laptop. I did many many many steps to avoid runtime broker bug, but this nightmare still continue. I am going to be really paranoic of it. Could somebody collect the list of steps what to do in my case?
I also want to try move to new profile, but it is a lot of work to move all setting and files.
I uninstalled all metro apps but I didn't disabled runtime broker as a service because this step is discutable.
Why Microsoft is not able to solve this serious bug?????

 

Ok guys, I have done crazy two days debug hunting in my installation and solved my problem!
What I used to process analyze:

• Resource monitor
• Event viewer
• Windows Sysinternals Process Explorer
• Farbar Recovery Scan Tool
• HijackThis
• msconfig + clean boot
• Windows Performance Recorder
• Windows Performance Monitor
• WMI: wbemtest.exe
• WMI: WMIDiag

Commands: net sc logman wmic openfiles netstat iphlpsvc wscsvc

The main problem was installed Hyper-V and PowerShell.
I analyzed, that Avast is causing some load of WMI, I had to unistall older Java version.
I disabled TimeBroker but I still mean that is nonsence because the process is active anyway.
I resolved some errors in event log.

Definitely solved.

 

Thank you so much for this tip! I had a folder on my cloud drive in the sources list for Photos. Once I removed it, Runtime Broker dropped to 0%! I had to make an account just to say thank you!

 

And now you have an account, feel welcome to use it more*Smile

 

I had 40%-60% in my Win10 pro 1511 build 10586.218, crazy bad, then all I did was disable "Show me tips about Windows" and immediately the cpu dropped down to near zero.

What I could see is that RuntimeBroker.exe was scanning all of my dropbox images from photo upload, tens of thousands of them.

Thank you.

 

Can I have you all run this program and ignore my posted comment there:

Aegis for Windows 7/8.x - Block all known Microsoft spying and Windows 10 upgrade elements | technology

DO NOT follow my instructions in the comments, ONLY run Aegis and please post your status on RuntimeBroker running. IF Aegis prevents RuntimeBroker from "being needed", then YOU DO NOT need to do all the crazy things I did.

HOWEVER, if you want to be crazy like me: please do as I in the comments *Biggrin

 

THANK YOU! THANK YOU! THANK YOU!
Easiest fix in the world. Took me all of 10 seconds to do... and Runtime broker immediately dropped from 30% to less than 1%
Once again... THANK YOU! *Smile