Windows 10: Runtime broker "eats" a lot of CPU in Windows 10

Hey all, First of all I would like to apologize about the topic, I know, that there are a lot of topics with the similar problem. I have tried all the stuffs, that was explained there, but none of them helped me at all. I still have problem with the runtime broker, which uses a lot of CPU and so on, even if nothing is running on the computer. Because of it, when I close the laptop, it can't turn of by itself and still uses a lot of CPU, which will cause a problem one day... I know the idea of the application or whatever it is called (runtime broker) and it is supposed to take just a one or maximum two-three percentages of CPU, but it is not like that with me. I have tried this one:
How to disable runtime broker on Windows 8 RTM - YouTube
and as well to go in the registry and set some value from 3 to 4, I don't really remember the exact things, I just saw a topic in some forum about it and the people there said, that it works. BUT not really for me..
I will add a screenshot of my task manager to see, what do I mean:




:)

 

Runtime Broker high CPU usage

Does your music library include a network location, e.g. a shared folder on a server or on a NAS?

 

Runtime Broker high CPU usage

Does your music library include a network location, e.g. a shared folder on a server or on a NAS?

No I don't have anything like that. My library is just a folder that contains music and none of the subfolders are shared.

 

Of all the fixes described in many posts on the internet, I could not find one to work. However, and I don't want to be premature, after installing KB3081444 and KB3081441, Runtime Broker is not hogging CPU time. This has proved true for several hours after installing the two updates I received and installed on 8/19/2015. Hope it holds true.

 

If the KBs that lagunasrfr mentioned do not help, try this

Turn off those apps you do not want running in the background (I turned them all off, but you might want mail or some other apps to work behind the scenes).

Settings > System > Battery saver > Battery use > Change background app settings

This control might also be in
Settings > Privacy > Background apps

Also turn off Settings > System > Offline maps (unless you want those updates).

I'm sure there are more settings - check Privacy (don't let apps use your camera or mic unless they need those)

Consider turning off Cortana and Not Search online ... web results

 

I installed above updates at 3:00 pm today and it is now 8:45 pm. Haven't seen Runtime Broker. Have been running mix of programs and metro apps. Have not rebooted or restarted, but restart was done as part of the KB installations earlier. So it is now running with a restart after KB installation. CPU is running under at 3-5% now while I'm typing this. Will update this post tomorrow with status of CPU %.

 

It's 9:30 am the day after installation of KB3081444 and KB3081441. After installation and reboot, high CPU usage by Runtime Broker stopped. Computer was left in Sleep overnight and did wake to run maintenance and scheduled tasks. I did a shutdown little while ago. After reboot, Runtime Broker continues to show as 0% in Task Manager and CPU load as I type is 3 to 4%. If I see any reversion to the high CPU usage of Runtime Broker, I will post, but I'm hopeful I will see no return.
I

 

I would take a look and try to install the updates and hopefully it will work. Thank you for your answers.*Smile

 

Ahm.. I am sorry for the stupid question, but I don't really know how to install the updates. Can someone give me a hint? Thanks in advance
PS: I turned off all application that I don't use, but Runtime broker still uses the same percentages of CPU and I believe it goes even worst, than before.. I really reconsider to go back to Windows 7

 

Settings-Update & security

 

Thank you for your answer, I know about it, but it is written, Waiting to install and to few other waiting to download, but it doesn't download anything... It's staying at 8% for forever...

 

Give it time. Sometimes takes a looong time.