sodcalculator

10 Tech How-To

Fix Runtime Broker Has Stopped Working in Windows 10

Guide 10-53326 · Updated · Step by step

If you see the “Runtime Broker has stopped working” error in Windows 10, the quickest fix is to restart the Runtime Broker process in Task Manager, then run the Windows Store Apps troubleshooter. This usually resolves the crash immediately, but if it keeps recurring, you need to repair the app that triggered it or reset the Windows Store cache. Below is a detailed guide covering the causes, step-by-step fixes, and answers to common questions.

What Is Runtime Broker?

Runtime Broker (RuntimeBroker.exe) is a core Windows 10 system process that manages permissions for apps from the Microsoft Store. It acts as a middleman between those apps and the operating system, checking that each app only accesses files, folders, and settings it has permission to use. It also handles app-to-app communication and live tile updates.

You’ll see Runtime Broker running in Task Manager under “Windows Processes”. It typically uses a small amount of CPU and memory, but occasionally it can spike or crash, triggering the error dialog. The process is not malware by itself, though some malware can disguise itself with the same name, so it’s worth checking the file location if you suspect something.

Why Does Runtime Broker Keep Stopping?

The error usually appears when a Store app (like Photos, Mail, Calendar, or the Start menu itself) tries to access a resource that Runtime Broker cannot verify. Common triggers include:

  • A corrupted Windows Store cache.
  • An outdated or buggy Store app.
  • Incorrect system permissions or a broken user profile.
  • Third-party antivirus or security software interfering.
  • Windows system files that are damaged.

The error is more frequent after a Windows update or after installing a new Store app. It’s rarely caused by hardware failure, so the fixes below are all software-based.

How to Fix Runtime Broker Stopped Working

Try these fixes in order. Most users only need the first two.

1. Restart the Runtime Broker Process

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Go to the Details tab.
  3. Find RuntimeBroker.exe in the list.
  4. Right-click it and select End task.
  5. Windows will automatically restart it when needed.

This clears the stuck process without rebooting. If the error reappears immediately, move to the next step.

2. Run the Windows Store Apps Troubleshooter

  1. Open Settings (Win + I).
  2. Go to Update & Security > Troubleshoot.
  3. Select Additional troubleshooters.
  4. Choose Windows Store Apps and click Run the troubleshooter.
  5. Follow the on-screen instructions. It will detect and fix common issues.

3. Clear the Windows Store Cache

A corrupted cache is a frequent cause. Press Win + R, type wsreset.exe, and press Enter. A blank Command Prompt window will open, then close automatically. This resets the Store cache without deleting your apps or accounts.

4. Repair or Reset the Problematic App

If the error names a specific app, or you notice it happens when you open a particular app, repair that app:

  1. Go to Settings > Apps > Apps & features.
  2. Find the app (e.g., Photos, Mail, or Calculator).
  3. Click it, then select Advanced options.
  4. Click Repair first. If that doesn’t help, click Reset (this will delete app data).

5. Run System File Checker and DISM

Corrupted system files can cause Runtime Broker to crash. Open Command Prompt as administrator and run:

  1. sfc /scannow — this scans and repairs system files.
  2. If that finds issues, run DISM /Online /Cleanup-Image /RestoreHealth.

Restart after both commands complete.

6. Check for Windows Updates

Microsoft regularly patches Runtime Broker bugs. Go to Settings > Update & Security > Windows Update and click Check for updates. Install any pending updates and reboot.

7. Create a New User Account

If the error persists and you suspect a corrupted user profile, create a new local user account and see if the error occurs there. If it doesn’t, migrate your files to the new account.

Common Mistakes and Misconceptions

One common mistake is trying to disable Runtime Broker in Task Manager permanently. You can’t — it’s a protected system process that restarts automatically. Another is assuming the error means your PC is infected. While malware can mimic the process name, the genuine RuntimeBroker.exe is located in C:\Windows\System32. If you see it elsewhere, run a full antivirus scan.

Also, some guides recommend deleting RuntimeBroker.exe from System32. Do not do that — it will break Windows Store apps and may cause system instability. The fixes above are safe and reversible.

When the Error Appears Only at Startup

If Runtime Broker crashes right after boot, it’s often linked to a startup app that uses Store permissions. Open Task Manager > Startup and disable suspicious apps, especially ones you don’t recognize. Reboot and see if the error disappears. You can re-enable them one by one to identify the culprit.

Frequently Asked Questions

Is Runtime Broker a virus?

No, the legitimate RuntimeBroker.exe is a Windows system file. However, malware can use the same name. Check the file location — if it’s not in C:\Windows\System32, run a full antivirus scan.

Can I disable Runtime Broker to stop the error?

No, you cannot permanently disable it. It’s required for Windows Store apps to function. The best approach is to fix the underlying cause, not disable the process.

Why does Runtime Broker use high CPU?

High CPU usage usually indicates a Store app is misbehaving. Try the steps above, especially clearing the Store cache and repairing the app. If it persists, check for Windows updates.

Will resetting the Windows Store delete my apps?

No, wsreset.exe only clears the cache. Your installed apps and their data remain intact. Resetting an individual app (via Settings) will delete that app’s data, but not the app itself.

Does the error affect gaming or non-Store apps?

No, Runtime Broker only manages Store apps. Games and desktop software run independently. If you see the error while gaming, it’s likely a background Store app crashing, not the game itself.

What if none of these fixes work?

If the error persists after trying all steps, consider a Windows in-place repair or a system restore to a point before the error started. You can also check the Windows Event Viewer for the exact error code to get more targeted help.

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

The whole Tech How-To bed →