How to fix Runtime Broker High CPU usage in Windows 10

Before Windows 10 came along, Dave’s Computers was awash with customers experiencing Runtime Broker High CPU issues with Windows XP, Windows ME, Windows 7 and Windows 8. It seemed to follow Windows throughout its development but finally seems under control in Windows 10.

That doesn’t mean it isn’t still happening because it is. We saw a Windows 10 laptop in the store yesterday with this very issue, which prompted this post.

What is Runtime Broker and why does it cause high CPU usage?

The Runtime Broker is a middleman process that controls permissions between Windows, your profile settings and apps. As you use an app or an app is triggered by an event, the Runtime Broker will check to see what that app is allowed to do on your device and what it is not allowed to do.

In previous versions of Windows, if the Runtime Broker couldn’t get the answer it expected or couldn’t find an answer, it would get itself tied up in a cycle and gradually use up more and more of your CPU. While this happens less now, it still happens, hence this tutorial.

Fix Runtime Broker High CPU usage in Windows 10

There are three ways I know of to fix Runtime Broker High CPU usage in Windows 10.

Turn off Windows 10 suggestions

Turning off Windows 10 suggestions can fix Runtime Broker high CPU usage because this feature is a common cause of the issue. To do this, right-click the Windows Start button, select Settings, then System, and then Notifications & actions. Locate ‘Get tips, tricks and suggestions as you use Windows’, toggle it to off, and monitor CPU utilization. This is the first recommended fix; if it doesn't resolve the problem, proceed to the next solution.

1. Right click the Windows Start button and select Settings.
2. Select System and then Notifications & actions.
3. Locate ‘Get tips, tricks and suggestions as you use Windows’.
4. Toggle it to off and monitor CPU utilization.

This is apparently a common cause of Runtime Broker High CPU usage issues in Windows 10. If is stops the problem on your computer great. If it doesn’t move on to the next fix.

Can changing desktop wallpaper to a picture fix Runtime Broker high CPU usage?

Yes, changing your desktop wallpaper to a static picture can fix Runtime Broker High CPU usage in Windows 10, as having a slideshow background is a known cause. To implement this fix, right-click the Windows Start button, select Settings, then Personalization and Background. Under Background, change the dropdown to 'Picture'. This fix is only applicable if you currently use a slideshow background. If the problem persists or you don't use a slideshow, consider the next solution: disabling background apps. To do this, go to Settings, then Privacy, scroll to Background apps, and toggle ‘Let apps run in the background’ to off. While background apps are useful, disabling them means they'll check for updates only when opened, potentially reducing CPU load. For registry fixes, it's recommended to consult Dave's Computers.

1. Right click the Windows Start button and select Settings.
2. Select Personalization and Background.
3. Select dropdown under Background in the center and change it to Picture.

Once you have made the change, monitor your computer for a while to see if it fixed it. If you’re setting seeing the problem or don’t use a slideshow as a background, try this third fix.

1. Right click the Windows Start button and select Settings.
2. Select Privacy and scroll down the left to Background apps.
3. Toggle ‘Let apps run in the background’ to off.

While Background apps can be useful, it isn’t essential and just means the apps will check for updates and new content when you open them rather than run in the background.

There are registry fixes that can fix the Runtime Broker High CPU usage in Windows 10 but I would much rather you brought your computer to Dave’s Computers for that!