How To Fix The Runtime Broker High CPU Usage Error In Windows 10

This tutorial was written by Tom's Hardware Community member JamieKavanagh. You can find a list of all their tutorials here.

The runtime broker in Windows 10 is a process that helps manage app permissions and ensures apps are behaving themselves. Unfortunately, the broker itself can throw a fit every now and then and consume system resources. Here’s how to fix the runtime broker high CPU usage error in Windows 10.

As the runtime broker is a middleman, it isn’t the process itself causing high CPU usage but the application that is utilizing it. This is often Windows default apps or system notifications.


Fix runtime broker high CPU usage error in Windows 10
Some Windows 10 users have found that disabling Windows tips immediately drops CPU utilization.

1. Navigate to Settings, System, Notifications & actions.
2. Disable ‘Show me tips about Windows’.
3. Monitor CPU utilization to see if it works.

If you still see runtime broker taking up too many resources, try uninstalling Windows apps.

Uninstall apps that use runtime broker
One particular culprit is the Photos app within Windows 10. If you have lots of images stored on your machine, Photos will try to index them all for future use. This can cause your computer to show the error.

1. Type or paste ‘PowerShell’ into the Search Windows box and open as an administrator.
2. Type or paste ‘Get-AppxPackage *photos* | Remove-AppxPackage’. This will uninstall the Windows Photo app from your machine.
3. Monitor CPU utilization to see if it works.

Chances are, once you remove this app, the high CPU usage error will disappear. If it doesn’t, consider uninstalling other apps by using one of the following commands:

Get-AppxPackage *windowscommunicationsapps* | Remove-AppxPackage
Get-AppxPackage *windowscamera* | Remove-AppxPackage
Get-AppxPackage *xboxapp* | Remove-AppxPackage
Get-AppxPackage *zunemusic* | Remove-AppxPackage
Get-AppxPackage *windowsmaps* | Remove-AppxPackage
Get-AppxPackage *zunevideo* | Remove-AppxPackage
Get-AppxPackage *messaging* | Remove-AppxPackage
Get-AppxPackage *phone* | Remove-AppxPackage
Get-AppxPackage *bingweather* | Remove-AppxPackage
Get-AppxPackage *windowsstore* | Remove-AppxPackage
Get-AppxPackage *windowsalarms* | Remove-AppxPackage
Create a new thread in the News comments forum about this subject
This thread is closed for comments
5 comments
Comment from the forums
    Your comment
  • teardroop
    Do not remove Windows Store (*windowsstore*), if you do, you will not be able to install apps again.
  • firefoxx04
    LOL, Windows 10 is such a piece of crap. Ive moved onto Server 2012 R2 (when I have to use Windows) but once its out of support I guess ill just be out of luck because I will never willingly use such a garbage operating system. I don't know how you people do it.

    Debian 9 with Server 2012 R2 virtualized for gaming. The future is going to suck.
  • mrmez
    Windows market share has been steadily declining for a long time:
    http://gs.statcounter.com/os-market-share#monthly-200901-201801

    A big part is that people are using computers differently, but a big part is also that Windows IS a POS.
    Even ramming free W10 down peoples throats has barely registered a blip.