Runtime Broker (RuntimeBroker.exe): What It Is and How to Fix High Memory Usage

Runtime Broker, shown as RuntimeBroker.exe, is a Microsoft Windows process that helps manage permissions for Microsoft Store and modern Windows apps. It is normal to see it in Task Manager. It should usually use only a small amount of memory, but a problematic app can make Runtime Broker consume much more RAM or CPU.

What does Runtime Broker do?

Runtime Broker sits between Windows apps and sensitive permissions such as camera, microphone, location, notifications, and background activity. Microsoft describes it as a Task Manager process that helps manage permissions for apps from Microsoft Store. In normal conditions it is lightweight.

If it starts using a large portion of memory or CPU, the process is usually reacting to an app, notification loop, background permission issue, or broken Store app behavior. The fix is to identify the app or setting that triggers it, not to delete RuntimeBroker.exe.

What is normal?

Normal	Needs checking
A few megabytes of memory while idle.	Hundreds of MB or more for long periods.
Brief CPU activity when launching Store apps.	CPU usage continues while no modern apps are open.
File is in C:\Windows\System32.	RuntimeBroker.exe appears in AppData, Temp, Downloads, or another user folder.
Usage drops after closing the problem app.	Usage returns immediately after boot with no clear trigger.

Verify the file location

Open Task Manager, right-click Runtime Broker, and choose Open file location. The legitimate file should be in C:\Windows\System32 and signed by Microsoft. A file with the same name somewhere else is not the normal Windows component.

Fix high memory or CPU usage

1. Open Task Manager and confirm how much memory Runtime Broker is using. Microsoft notes that unusually high memory use can point to an app issue.
2. Select Runtime Broker and choose End task, then restart Windows. This is safe as a temporary reset.
3. Close Microsoft Store apps one by one and watch whether usage drops.
4. Disable unnecessary background app permissions in Windows Settings.
5. Turn off noisy notification sources temporarily if the spike follows notifications.
6. Update Microsoft Store apps and Windows, then reboot.
7. Repair, reset, or uninstall the app that makes Runtime Broker spike repeatedly.

When to scan for malware

The real Runtime Broker is not malware. Scan the system if the file path is not System32, there are multiple oddly named copies, startup entries point to RuntimeBroker.exe outside Windows, or the issue appeared after an unknown installer. Do not remove the Microsoft-signed System32 file.

How to find the app behind the spike

Runtime Broker does not usually create the problem by itself. It reacts to app permissions and background activity. Open Task Manager, sort by CPU or memory, and watch what changes when you close Microsoft Store apps, widgets, chat apps, weather/news panels, and notification-heavy apps. If Runtime Broker drops after one app closes, repair or reset that app first.

Next, open Windows Settings and review privacy permissions. Camera, microphone, location, notifications, background app activity, and account access are the common areas to test. Turn off permissions you do not use, reboot, and check whether Runtime Broker remains quiet. This is more useful than trying to remove the Windows component.

When ending the task helps

Microsoft’s own guidance for high Runtime Broker memory use is to end the task and restart the device when it consumes an unusually large portion of memory. Treat that as a reset, not a cure. If the same app triggers the spike again, the underlying fix is to update, repair, reset, or uninstall that app.

What not to do

Do not download random “Runtime Broker remover” tools, do not delete the System32 file, and do not disable Windows services without knowing what app depends on them. Those steps can create more instability than the original memory problem. The safe path is file verification, app isolation, permission cleanup, Windows update, and targeted repair of the app causing the spike.

Fast checklist

• Real Windows file: C:\Windows\System32\RuntimeBroker.exe.
• Normal behavior: low memory, brief CPU use when Store-style apps open.
• Common trigger: a Microsoft Store app, notifications, widgets, or background permissions.
• Unsafe sign: RuntimeBroker.exe running from a user profile, Temp, Downloads, or a random folder.

Why this process is often misunderstood

Runtime Broker is not a classic standalone application. It is a broker between Windows apps and permissions. That is why “remove Runtime Broker” advice is usually wrong. If it uses resources, the better question is which app or permission request is causing it to stay active.

This also explains why the problem can return after ending the task. Ending Runtime Broker resets the symptom, but the same app can request permissions again after reboot. A useful fix must include app isolation, notification cleanup, background permission review, and Microsoft Store app repair.

FAQ

Can I disable Runtime Broker permanently?

No practical permanent disable is recommended. It is part of how Windows manages Store app permissions.

Is it safe to end Runtime Broker?

Yes. Ending the task can temporarily stop high memory use; Windows will start it again when needed.

Why does it use a lot of RAM?

Usually because a Store app, notification, or background permission is stuck. Find and repair the app rather than deleting RuntimeBroker.exe.