Runtime Broker is a standard Windows background process that manages app permissions, specifically the permissions that Modern UI (UWP) apps request, such as access to your camera, microphone, and location. When you see it in Task Manager, it’s not a virus or a sign of a problem—it’s a core part of Windows 8, 8.1, and 10 that ensures apps only use the permissions you’ve granted. This article explains what Runtime Broker does, why it sometimes uses high CPU or memory, and how to safely manage it.
What Exactly Is Runtime Broker?
Runtime Broker (file name: RuntimeBroker.exe) is a legitimate Microsoft Windows system process. It was introduced with Windows 8 and continues to be present in Windows 10 and Windows 11. Its job is to act as an intermediary between UWP apps (the ones you download from the Microsoft Store) and the operating system’s permission system. When a UWP app wants to access a protected resource—like your webcam, contacts, or file system—Runtime Broker checks whether you have granted that permission. If you have, it allows the app to proceed; if not, it blocks the request. This prevents apps from silently accessing your personal data without your knowledge.
How Runtime Broker Works
Runtime Broker runs in the background for each user session. When you launch a UWP app, Windows starts a new instance of RuntimeBroker.exe for that app. The broker then monitors the app’s permission requests in real time. It also tracks which apps are using which permissions, and it can revoke access if you change a permission setting while the app is running. This is why you might see multiple Runtime Broker processes in Task Manager—each one is tied to a different app or group of apps. The process is lightweight by design, but it can occasionally consume more CPU or memory than expected, which leads to user concern.
Why Does Runtime Broker Use High CPU or Memory?
Most of the time, Runtime Broker uses very few resources—often less than 10 MB of memory and near-zero CPU. However, there are a few common reasons why it might spike:
- Many UWP apps running simultaneously: Each app gets its own broker instance, so having multiple Store apps open can increase total memory usage.
- A misbehaving app: A buggy or poorly coded UWP app might make repeated permission requests, causing the broker to work harder.
- Permission prompts: When an app requests a new permission, the broker briefly uses more CPU to show the prompt and wait for your response.
- Windows 10 version 1809 and earlier bugs: Some older builds had a known issue where Runtime Broker would leak memory over time, especially when many apps were used. This was fixed in later updates.
If you see high CPU usage (above 20-30%) persistently, it’s usually a sign that a specific app is misbehaving, not that the broker itself is faulty.
Is Runtime Broker Safe? (Virus or Malware?)
Runtime Broker is safe and is a genuine Microsoft component. It’s located in the C:\Windows\System32 folder. However, malware can sometimes disguise itself with the same name. To verify that the process you see is legitimate, right-click it in Task Manager and select “Open file location.” If it opens the System32 folder, it’s almost certainly the real one. If it opens a different folder (like AppData or Temp), that’s a red flag. You can also check the digital signature: right-click the process, go to Properties, and check the “Digital Signatures” tab—it should show “Microsoft Windows.” If you’re still unsure, run a full antivirus scan.
Can You Disable or Stop Runtime Broker?
You should not disable Runtime Broker. It is not optional—it’s a core part of Windows security and app management. If you force-stop it (via Task Manager), it will simply restart automatically, and any UWP apps that rely on it may crash or fail to open. There is no official way to permanently disable it without breaking Windows functionality. If you’re concerned about its resource usage, the better approach is to identify which app is causing the issue and either update it, reset it, or uninstall it. You can also restart your PC to clear any temporary memory leaks.
How to Troubleshoot Runtime Broker Issues
If you’re experiencing persistent high CPU or memory usage from Runtime Broker, here are steps to resolve it:
- Update Windows: Go to Settings > Update & Security > Windows Update and install all pending updates. Many Runtime Broker bugs have been fixed in cumulative updates.
- Identify the culprit app: Open Task Manager, look at the Runtime Broker processes, and note which apps are using the most resources. You can also use the “Details” tab to see the PID and then use PowerShell to trace it.
- Reset or reinstall the problematic app: Go to Settings > Apps > Apps & features, find the app, and choose “Advanced options” > “Reset.” If that doesn’t help, uninstall and reinstall it from the Microsoft Store.
- Run the Windows Store Apps troubleshooter: Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Store Apps, and run it.
- Check for malware: Run a full system scan with Windows Defender or a trusted third-party antivirus to rule out a fake Runtime Broker.
These steps usually resolve any abnormal behavior.
Runtime Broker vs. Other Windows Processes
Runtime Broker is often confused with other background processes like Service Host (svchost.exe) or Windows Explorer. The key difference is that Runtime Broker is specifically for UWP app permissions, while svchost.exe hosts various Windows services, and Explorer.exe handles the desktop interface. Unlike svchost.exe, which can have dozens of instances, Runtime Broker typically has only a few. Also, Runtime Broker is not a service—you won’t find it in the Services console. It’s a per-user process, which is why you see it under your username in Task Manager.
Frequently Asked Questions
Is Runtime Broker a virus?
No, the genuine RuntimeBroker.exe is a legitimate Microsoft process. However, malware can masquerade as it. Always verify the file location and digital signature if you’re suspicious.
Why are there multiple Runtime Broker processes running?
Each UWP app that uses permissions gets its own Runtime Broker instance. Having several running at once is normal, especially if you have multiple Store apps open.
Can I end Runtime Broker from Task Manager?
You can end it temporarily, but it will restart automatically and may cause UWP apps to malfunction. It’s not recommended.
Why does Runtime Broker use so much memory in Windows 10?
This was a known bug in older Windows 10 versions (1809 and earlier). Updating Windows usually fixes it. If it persists, a specific app might be misbehaving.
Does Runtime Broker slow down my PC?
Normally, no. It uses minimal resources. Only when there’s a bug or a problematic app does it cause noticeable slowdowns, which can be fixed with the troubleshooting steps above.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Google Photos Backup Stuck? Fixes That Work
- Record Your Own Alarm Sound on Android
- Transfer Music from ZTE to iPhone: Full Guide
- Angel Investor vs Venture Capitalist: Key Differences
- Sync Apps Between Android Devices Using Google Play
- Find What Drains Your iPhone Battery Fast