Share this article

Improve this guide

[Fixed] Runtime Broker High CPU Usage: 9 Quick Solutions

Discover tried-and-true strategies vetted by our team of specialists

8 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

The Runtime Broker is a Windows process that helps manage app permissions on your PC. Usually, this tool shouldn’t use more than a few MB of memory, but in some cases, the Runtime Broker uses even 1GB of RAM or more.

Suchunusual CPU usageaffects the processor’sperformanceand in time, it can shorten its lifespan. In the majority of cases, the Runtime Broker uses too much RAM due to a faulty app.

If your Runtime Broker causeshigh CPU usage, try the workarounds below to fix this issue.

What is Runtime Broker?

Runtime Broker is a Windows process that can be managed through Task Manager and assists in administering permissions for software obtained from the Microsoft Store.

RuntimeBroker.exe is a process that is initiated by Universal programs, and if that process terminates, all apps that are presently active will close immediately.

Why is Runtime Broker using so much CPU?

According to Microsoft, high CPU usage is typically caused by incompatible or defective applications on your machine.

After installing a certain application, if you are experiencing High CPU Usage, you canuninstall the applicationto see if this solves the problem.

Additionally, if you have multiple Runtime Broker instances going on simultaneously, you will experience high CPU usage.

How can I fix Runtime Broker high CPU usage on Windows 10?

1. Stop the Runtime Broker from Task Manager

According to users, sometimes you can fix the problem with the Runtime Broker and high CPU usage simply by ending the Runtime Broker process.

This is quite simple to do, and you can do it by following these steps:

After disabling all Runtime Broker processes, check for the problem. Keep in mind that this might be just a temporary workaround, but you might want to try it out.

You can apply the same approach to other processes, such asMicrosoft Common Language Runtime Native Compiler High CPU Usage.

2. Hack the Registry

If you’re having problems with Runtime Broker and high CPU usage, you might be able to fix the problem simply by making a few changes in your registry.

This is relatively simple to do, and you can do it by following these steps:

After making these changes, check if the problem with highCPUusage is resolved.

3. Disable the tips about Windows

According to users, sometimes certain features of Windows can cause problems with Runtime Broker and highCPUusage.

However, you can fix the problem simply by disabling the Windows tips. To disable this feature, do the following:

After doing that, the issue with Runtime Broker and highCPUusage should be resolved.

4. Switch your lock screen background Windows Slideshow to Picture

A few users reported that Runtime Broker highCPUusage issue is caused by your lock screen background.

It seems that the slideshow background on your lock screen is causing this problem, and to fix this issue, you need to disable it and switch to a single picture.

This is rather simple, and you can do it by following these steps:

After doing that, the issue with Runtime Broker should be completely resolved.

5. Check your antivirus

Sometimes, your antivirus can cause problems with Runtime Broker and lead to issues with highCPUusage.

To fix this problem, we advise you to disable certain antivirus features and check if that helps. If the problem is still present, you might have to disable or uninstall your antivirus.

If removing the antivirus solves the problem, perhaps this is a good time to consider switching to a different antivirus.

There are many great antivirus tools on the market, but if you’re looking foruseful antivirus softwarethat won’t interfere with your system, you should definitely look through the list and choose a better option for you.

You would have a better Auto-Pilot user experience, an extra-protection layer that encrypts immediately every file that is threatened by malicious programs, and better optimization for your PC.

6. Customize the advanced update settings

Sometimes, your update settings can cause Runtime Broker highCPUissues to appear. To fix this problem, you need to disable peer-to-peer updates.

This feature can be useful since it allows you to download updates from other PCs on the Internet and your local network.

However, sometimes that can lead to highCPUusage, but you can fix the problem by doing the following:

After turning this feature off, you won’t download updates from other PCs, instead, you’ll download them only and directly from Microsoft.

By turning this feature off the problem with Runtime Broker should be resolved.

7. Disable background apps

According to users, sometimes background applications can lead to this problem.

If you’re having issues with Runtime Broker and highCPUusage, perhaps you might be able to fix this problem by disabling the background applications.

This is simple to do, and you can do it by following these steps:

If you’re having problems with highCPUusage, the problem might be theGroove Musicapp.

After disabling this feature, the problem with highCPUusage should be resolved. Keep in mind that by disabling this feature you might miss certain notifications from Universal apps.

8. Delete Groove music using Powershell

Several users reported that this application is responsible for Runtime Broker’s highCPUusage, and in order to fix this problem, you need to remove it.

Since this is a Universal application, you’ll need to remove it withPowerShell. To do that, just follow these steps:

After removing Groove Music, check if the problem is still there.

9. Remove OneDrive

In some cases, Runtime Broker and highCPUusage can occur due toOneDrive.

To fix this problem, it’s advised to disable OneDrive or to remove it. To remove OneDrive from your PC, you need to do the following:

After removing OneDrive from your PC, check if the problem with Runtime Broker and highCPUusage is still there.

How to fix Runtime Broker high CPU in Windows 11?

Besides the solutions above, which are also applicable in Windows 11, you can follow the next steps:

You can find out more solutions by checking out our guide on what to do tofix high CPU usage in Windows 11.

Runtime Broker problems can negatively impact yourperformance, and speaking of this process, here are some common problems that users reported:

For additional troubleshooting steps, check out how tofix CPU at 100% for no reason.

Problems with Runtime Broker and highCPUcan cause many problems, such as reducedperformance, but we hope you managed to solve this issue using the solutions from this article.

[Fixed] Runtime Broker High CPU Usage: 9 Quick Solutions#

What is Runtime Broker?#

Why is Runtime Broker using so much CPU?#

How can I fix Runtime Broker high CPU usage on Windows 10?#

1. Stop the Runtime Broker from Task Manager#

2. Hack the Registry#

3. Disable the tips about Windows#

4. Switch your lock screen background Windows Slideshow to Picture#

5. Check your antivirus#

6. Customize the advanced update settings#

7. Disable background apps#

8. Delete Groove music using Powershell#

9. Remove OneDrive#

How to fix Runtime Broker high CPU in Windows 11?#