- The Runtime Broker is a Windows process that helps manage app permissions on your PC.
- Sometimes your antivirus can cause problems with Runtime Broker and lead to issues with high CPU usage. To fix this problem, try to disable certain antivirus features and check if that helps.
- The CPU is your computer's brain so it's the most important part. If you want to know everything about it, visit our CPU section for news, guides, and tips.
- Should you encounter another Windows 10 error, don't hesitate to hit our Windows 10 errors hub for plenty of expert solutions.
The Runtime Broker is a Windows process that helps manage app permissions on your PC.
It normal circumstances, 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.
Such unusual CPU usage affects the processor’s performance and, 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 causes high CPU usage, try out the workarounds listed below to fix this issue.
How can I fix Runtime Broker high CPU usage on Windows 10?
Runtime Broker problems can negatively impact your performance, and speaking of this process, here are some common problems that users reported:
- Runtime Broker high disk usage, memory, RAM – This process can negatively impact your performance, but in order to fix the issue, you just have to disable certain Windows features.
- Runtime Broker error – Sometimes Runtime Broker errors can appear on your PC. This is usually caused by your antivirus, but you can fix that issue by changing your antivirus settings.
- Runtime Broker multiple instances – If multiple instances of Runtime Broker appear on your PC, be sure to end all processes from Task Manager and the issue will be resolved.
- Runtime Broker keeps running – Sometimes this process can keep running on your PC and negatively impact your performance. To fix that, simply change your Windows Update settings and the issue will be resolved.
Solution 1 – Check your antivirus
Sometimes your antivirus can cause problems with Runtime Broker and lead to issues with high CPU usage.
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 your antivirus or even uninstall it.
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 for an antivirus that won’t interfere with your system, you should definitely try out Bitdefender.
Bitdefender has lots of improvements in its newest version.
Now you have a better Auto-Pilot user experience, you have an extra-protection layer that encrypts immediately every file that is threatened by malicious programs and great optimization.
If you think about an antivirus, we strongly recommend you Bitdefender, the best security solution in the world.
Solution 2 – Stop the Runtime Broker
According to users, sometimes you can fix the problem with 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:
- Open Task Manager. You can do that quickly by pressing Ctrl + Shift + Esc.
- Now locate Runtime Broker process on the list. Right-click it and choose End task from the menu.
After disabling all Runtime Broker processes, check if the problem is still there. Keep in mind that this might be just a temporary workaround, but you might want to try it out.
Solution 3 – Hack the Registry
If you’re having problems with Runtime Broker and high CPU usage, then you might be able to fix the problem simply by making a couple of changes in your registry.
This is relatively simple to do, and you can do it by following these steps:
- Press Windows Key + R and enter regedit. Press Enter or click OK.
- Go to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTimeBroker.
- Change Start=dword:00000003 to dword:00000004. However, this action affects parts of Cortana’s reminders.
After making these changes, check if the problem with high CPU usage is resolved.
Solution 4 – Disable the tips about Windows
According to users, sometimes certain features of Windows can cause problems with Runtime Broker and high CPU usage.
However, you can fix the problem simply by disabling the Windows tips. To disable this feature, just do the following:
- Open the Settings app. The quickest way to do that is to use Windows Key + I shortcut.
- When the Settings app opens, head over to the System section.
- Now choose Notifications & actions from the left pane. In the right pane, locate and disable Get tips, tricks and suggestions as you use Windows.
After doing that, the issue with Runtime Broker and high CPU usage should be resolved.
Solution 5 – Switch your lock screen background Windows Slideshow to Picture
ew users reported that Runtime Broker high CPU usage issue is caused by your lock screen background.
It seems that slideshow background on your lockscreen 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:
- Open the Settings app and navigate to the Personalization section.
- Go to the Lock screen section in the left pane. In the right pane, set Background to Picture.
After doing that, the issue with Runtime Broker should be completely resolved.
Solution 6 – Customize the advanced update settings
In some cases, your update settings can cause Runtime Broker high CPU issues 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 high CPU usage, but you can fix the problem by doing the following:
- Open the Settings app and navigate to the Update & Security section.
- In the right pane, click Advanced options.
- Scroll all the way down and click on Delivery Optimization.
- Locate the Allow downloads from other PCs option and disable it.
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.
Solution 7 – Disable background apps
According to users, sometimes background applications can lead to this problem.
If your having issues with Runtime Broker and high CPU usage, 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:
- Open the Settings app and go to the Privacy section.
- Navigate to the Background apps in the left pane. In the right pane, disable Let apps run in the background option.
After disabling this feature, the problem with high CPU usage should be resolved. Keep in mind that by disabling this feature you might miss certain notifications from Universal apps.
Solution 8 – Delete Groove music using Powershell
If you’re having problems with high CPU usage, the problem might be the Groove Music app.
Several users reported that this application is responsible for Runtime Broker high CPU usage, and in order to fix this problem, you need to remove it.
Since this is a Universal application, you’ll need to remove it with PowerShell. To do that, just follow these steps:
- In the Search bar, enter powershell. From the list of results right-click Windows PowerShell and choose Run as administrator.
- Copy the following commands one at a time: Get-AppxPackage -name Microsoft.ZuneMusic | Remove-AppxPackage Get-AppxPackage -name Microsoft.Music.Preview | Remove-AppxPackage
After removing Groove Music, check if the problem is still there.
Solution 9 – Remove OneDrive
In some cases, Runtime Broker and high CPU usage can occur due to OneDrive.
To fix this problem, it’s advised to disable OneDrive or to remove it. To remove OneDrive from your PC, you just need to do the following:
- Open Command Prompt as administrator. To do that, press Windows Key + X and choose Command Prompt (Admin) from the list. If Command Prompt isn’t available, you can use PowerShell (Admin).
- Type the command taskkill /f /im OneDrive.exe to end all OneDrive processes.
- Type the command %SystemRoot%System32OneDriveSetup.exe /uninstall for 32-bit Windows or %SystemRoot%SysWOW64OneDriveSetup.exe /uninstall for 64-bit Windows to uninstall OneDrive.
After removing OneDrive from your PC, check if the problem with Runtime Broker and high CPU usage is still there.
Problems with Runtime Broker and high CPU can cause many problems, such as reduced performance, but we hope you managed to solve this issue using the solutions from this article.
FAQ: Read more about Runtime Broker
- What is runtime broker?
The Runtime Broker is a Windows process that helps manage app permissions on your PC. Although it runs in the background all the time, you will see it in action when you launch a universal app.
- What is a runtime broker error?
In some cases, the Runtime Broker uses even 1GB of RAM or more. Such unusual CPU usage affects the processor’s performance and, in time, it can shorten its lifespan. Here’s a guide on how to fix Runtime Broken errors in Windows 10.
- What is runtime broker in task manager?
Runtime Broker shouldn’t use more than a few megabytes of RAM, but due to a faulty app or antivirus software, it starts using a lot more. If it exceeds that memory usage read our short but effective guide to fix this problem.
- How to disable runtime broker?
You shouldn’t disable Runtime Broker because it’s important for protecting your security and privacy when running universal apps. If it malfunctions and uses too many resources, you can kill its process.
Editor’s Note: This post was originally published in October 2018 and has been since revamped and updated in April 2020 for freshness, accuracy, and comprehensiveness.Editor's Note: This article was originally published in July 2016 and was revamped and updated in November 2020 for freshness, accuracy, and comprehensiveness.