ThisCalculator

Everyday

Runtime Broker Process: What It Is & How to Fix High CPU

Updated · Standard formula, shown below

Runtime Broker Process: What It Is & How to Fix High CPU

The Runtime Broker process (RuntimeBroker.exe) is a core Windows component that manages permissions for apps from the Microsoft Store, and it normally uses very little CPU or memory. If you see it consuming high CPU or RAM, it is usually a sign that a Store app is misbehaving or a system issue needs attention, and there are safe ways to fix it.

What Is RuntimeBroker.exe?

Runtime Broker is a background process that was introduced with Windows 8 and continues in Windows 10 and 11. Its job is to act as a middleman between the operating system and the apps you install from the Microsoft Store (UWP apps). When a Store app wants to access a system resource like your camera, microphone, contacts, or file system, the Runtime Broker checks the app’s declared permissions and either grants or denies the request. It also helps isolate apps so that one app cannot read another app’s data.

You will typically see several RuntimeBroker.exe instances running at once—one per app that is currently using it. This is normal. Each instance is lightweight, using just a few megabytes of memory and near-zero CPU when idle.

Why Does Runtime Broker Use High CPU or Memory?

High CPU usage (above 20-30% consistently) or memory usage (hundreds of megabytes) from Runtime Broker is not normal. The most common causes are:

  • A Store app that is stuck or misbehaving—an app that fails to close properly or keeps requesting permissions in a loop can make the broker work overtime.
  • Too many Store apps running at startup—each app that launches at boot creates a broker instance, and if many are running, the total memory adds up.
  • Corrupted app cache or data—a broken app installation can cause the broker to repeatedly try to resolve permissions.
  • Windows system file corruption—rarely, a damaged system component can cause the broker to malfunction.
  • Antivirus or security software interference—some third-party security tools may conflict with the permission-checking mechanism.

It is also worth noting that a single RuntimeBroker.exe process using 100-200 MB of RAM is not necessarily a problem if you have many Store apps open. The issue is when it stays high even after you close all Store apps.

How to Check If Runtime Broker Is a Problem

Before you try any fixes, confirm that the process is actually causing the issue and not just a symptom of another app. Open Task Manager (Ctrl+Shift+Esc), go to the Processes tab, and look for Runtime Broker under the Apps section. Sort by CPU or Memory to see which instance is using the most resources.

Then, close all Store apps (including those running in the background) and see if the usage drops. If it does, the problem is with one of those apps. If it stays high even with no Store apps open, the issue is more systemic.

How to Fix High CPU or Memory Usage

Here are the steps to resolve Runtime Broker problems, from simplest to most thorough:

  1. Restart the process—Right-click the Runtime Broker entry in Task Manager and select End task. Windows will automatically restart it when needed. This often clears a temporary glitch.
  2. Restart your PC—A clean reboot clears all background processes and resets the permission broker.
  3. Run the Windows Store Apps troubleshooter—Go to Settings > System > Troubleshoot > Other troubleshooters, select Windows Store Apps, and run it. This tool detects and fixes common app issues.
  4. Reset the problematic app—If you know which app triggers the high usage, go to Settings > Apps > Installed apps, find the app, select the three-dot menu, and choose Advanced options. Then click Reset (this clears the app’s data, so you may need to sign in again).
  5. Clear the Microsoft Store cache—Press Win+R, type wsreset.exe, and press Enter. A command window will open and close automatically once the cache is cleared.
  6. Check for Windows updates—Go to Settings > Windows Update and install any pending updates. Microsoft regularly fixes bugs in the permission system.
  7. Run System File Checker—Open Command Prompt as administrator (search for “cmd�, right-click, and select Run as administrator), then type sfc /scannow and press Enter. This scans and repairs corrupted system files. If it finds issues, restart and then run DISM /Online /Cleanup-Image /RestoreHealth.

Is It Safe to Disable or Delete Runtime Broker?

No. Runtime Broker is a legitimate Microsoft system process, and you should never delete or permanently disable it. If you end the process in Task Manager, it will restart automatically. If you try to disable it via services or registry edits, you can break the ability of Store apps to access permissions, and in some cases prevent them from launching at all. The process is digitally signed by Microsoft and is located in the C:\Windows\System32 folder. If you see it running from any other location, that could be malware, but that is extremely rare.

If you are worried about malware, you can verify the file location: right-click the process in Task Manager and select Open file location. It should open the System32 folder. If it opens anywhere else, run a full antivirus scan.

Common Misconceptions

One common myth is that Runtime Broker is a virus or unnecessary bloat because it appears in Task Manager multiple times. In reality, multiple instances are by design—each Store app that needs permission checking gets its own broker instance. Another misconception is that ending the process will speed up your PC. While it may free a small amount of memory temporarily, it will restart on its own and any Store app that was waiting for a permission will hang until it does.

Another thing people often confuse is Runtime Broker with RuntimeBroker.exe vs RuntimeBroker (32-bit)—these are the same process, just showing the architecture. The 32-bit label simply means the process is running in 32-bit mode on a 64-bit system, which is normal for many Windows components.

Frequently Asked Questions

Is Runtime Broker a virus?

No, the genuine RuntimeBroker.exe is a core Windows component. However, malware can disguise itself with the same name. Check the file location—if it is not in C:\Windows\System32, run a security scan.

Why are there multiple Runtime Broker processes?

Windows creates one instance per Store app that is currently requesting or using permissions. Having several running at once is normal and not a cause for concern by itself.

Can I disable Runtime Broker to save memory?

You should not. Disabling it will break permission checks for Store apps, which can cause apps to crash or fail to open. The memory savings are negligible—each idle instance uses only a few MB.

Why does Runtime Broker use high CPU after waking from sleep?

This can happen when apps that were suspended during sleep try to resume and re-establish permissions. It usually settles down within a minute. If it persists, restart the PC or update your drivers.

Does Runtime Broker affect gaming performance?

Only if it is stuck in a loop using high CPU. In normal operation, it uses near-zero CPU, so it does not impact gaming. If you see high usage while gaming, close background Store apps like Xbox or Game Bar.

What should I do if none of the fixes work?

If high usage continues after all the steps above, consider performing a Windows repair installation using the Media Creation Tool, which keeps your files but reinstalls the system. Alternatively, create a new user account—if the problem disappears there, the issue is tied to your user profile.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.