Windows 10: Runtime Broker Process

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.

 

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.

 

The first and only install on my systems was from the latest distro; 2 of my systems seem to be running fairly well, one desktop, one Lenovo laptop. (Both running Windows 10 Home)After the last update from Microsoft they seem to have settled down a bit. But the other Lenovo ( running Windows 10 Pro) just wouldn't behave. No matter what I tried the runtime broker would run up CPU time in an out of control manner until I ended the task in task manager. Then the cycle would begin again. I had to go back to windows 7 to get any use out of the machine at all.

 

That wasn't my experience. I immediately did a clean install after I did the initial validation upgrade from Win 8.1 on Jul 29. I still had trouble with the runtime broker. It's still disabled

 

In all fairness, and keeping the record straight, I still have 2 systems running Windows 10, and after the last MS downloaded update seem to run fairly well. Runtime broker on those 2 systems behaves much better. Of those 1 is a Lenovo T500, and another home built desktop based on an ASUS P7H55-M mobo, and running Windows 10 home. But this one *#%&! Lenovo T500, (why they call them both T500 is confusing since the hardware is completely different) running Windows 10 pro, just wouldn't behave, and I went back to Windows 7. Just as a precautionary note to anyone reading this thread, The restore back to windows 7 went as badly as the upgrade did. In short 2 bsod's and a failed attempt to repair the startup function. Thank goodness I had the foresight to back the system up using several various methods before upgrading.

 

Thanks for reporting, it seems, that mostly people running Pro have the problem.
That would only confirm my theory, that Home performs much better in various tasks.

 

Using home here on my pc and had to disable runtime broker.

 

i doubt that. i installed Pro on 6 different machines, all system experienced high temp due to runtime broker's high usage (60-80% cpu). but all i did was simply disable "Show me tips about Windows" found on Settings -> System -> Notifications, and everything went back to normal.




btw, 52% cpu usage is by ESET running smart scan.

 

Think it's solved with latest Win updates KB3081444 and 3081441. See: Runtime broker "eats" a lot of CPU in Windows 10

 

For me it is still not solved.
I tried all solutions suggested here.
Done registry editing, checked the windows-update
installations and they are in place.
RunTime Broker still starts.
Cannot find which files are open with OpenFileView
Any new suggestions?

 

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.

 

I'm not a very advanced 'techie' but this Runtime broker problem was driving me bonkers because the various suggestions on this thread seemed to work to start with but then the problem would return. I had the feeling that the problem was connected with the Windows search indexing service because the little indicators of hard disc activity I have showing on my monitor always showed constant read activity whenever the broker problem returned.

So I just switched off the service by right clicking on the Start button, selecting 'Run', entering services.msc and then disabling 'Windows Search' from the list. Then re-boot.

This has completely resolved the problem for me.

 

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!

 

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

 

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.