What Runtime Broker Does and Why You Might Want to Close It

Runtime Broker is a Windows process that runs in the background to check whether your programs are following Microsoft's rules for how they should behave. It monitors apps you install from the Microsoft Store and makes sure they have permission to do what they're trying to do — like access your camera, read your files, or use your internet connection. Most of the time you won't notice it running.

Runtime Broker occasionally uses a lot of CPU power, which slows down your computer. This usually happens when Windows is checking a large number of apps at once, or when a single app is misbehaving. If you see "Runtime Broker" taking up 20, 30, or 50 percent of your CPU in Task Manager, closing it will free up that power when ready. The process will restart on its own the next time Windows needs it.

You cannot permanently delete Runtime Broker — it's part of Windows itself. But you can close it whenever it's causing problems, and your computer will keep working normally. The only apps that might stop working are Microsoft Store apps, and only while the process is closed.

Key Takeaways

  • Runtime Broker monitors Microsoft Store apps to make sure they follow Windows rules, and it restarts automatically when you close it.
  • The fastest way to close it is through Task Manager: press Ctrl+Shift+Esc, find "Runtime Broker" in the list, click it, and click "End Task".
  • Closing Runtime Broker will not harm Windows or your files, but Microsoft Store apps may not work until the process restarts.
  • If Runtime Broker keeps using high CPU after you close it, the problem is usually a misbehaving Microsoft Store app, not Runtime Broker itself.

Close Runtime Broker Through Task Manager

Task Manager is the fastest way to close Runtime Broker. Press Ctrl+Shift+Esc on your keyboard. Task Manager will open when ready, showing you all the processes running on your computer right now.

Look for "Runtime Broker" in the list. If you have many processes open, you can type "runtime" in the search box at the top to find it faster. Click on "Runtime Broker" once to select it, then click the button labeled "End Task" in the bottom right corner. The process will close within a few seconds.

Your computer will feel faster right away if Runtime Broker was using a lot of CPU. You can close Task Manager now. Runtime Broker will start again the next time Windows needs to check a Microsoft Store app, usually within a few minutes or the next time you open one of those apps.

What to Do If Runtime Broker Keeps Restarting and Using High CPU

If you close Runtime Broker and it when ready starts using high CPU again, the problem is not Runtime Broker itself — it's one of your Microsoft Store apps that's misbehaving. Runtime Broker is trying to monitor that app, and the app is doing something that takes a lot of checking.

To find which app is causing the problem, open Task Manager again with Ctrl+Shift+Esc. Click the "Performance" tab at the top, then click "Open Resource Monitor" at the bottom. In the new window, click the "CPU" tab. Look for any process using high CPU that you don't recognize or that you know you're not using right now. Note the name of that process.

Once you know which app is the problem, you have two choices. You can uninstall it by going to Settings > Apps > Apps & Features, finding the app in the list, clicking it, and clicking "Uninstall". Or you can wait for the app's creator to release an update that fixes the problem — check the Microsoft Store for updates to that app.

Close Runtime Broker From Command Line (Advanced)

If Task Manager won't open or is frozen, you can close Runtime Broker using Command Prompt. Press Windows key + R to open the Run box, type cmd, and press Enter. Command Prompt will open.

Type this command exactly as shown: taskkill /IM RuntimeBroker.exe /F and press Enter. The /F at the end forces the process to close even if it's stuck. You should see a message saying "SUCCESS: The process 'RuntimeBroker.exe' with PID [number] has been terminated." Close Command Prompt after that.

This method works the same way as Task Manager — Runtime Broker will restart when Windows needs it again. The /F flag is only necessary if the normal close command doesn't work.

Why Runtime Broker Exists and What It Checks

Microsoft created Runtime Broker to enforce app permissions — the rules about what each app is allowed to access. When you install a Microsoft Store app, it can ask for permission to use your camera, microphone, location, files, or contacts. Runtime Broker is the process that actually enforces those permissions and stops an app from doing something you didn't allow it to do.

It also checks whether apps are using features they're supposed to have permission for. If an app tries to access your microphone without asking, Runtime Broker stops it. This is a security feature, not a limitation — it prevents apps from secretly recording you or stealing your data.

Desktop apps that you install from websites (not the Microsoft Store) don't go through Runtime Broker. They run with whatever permissions you gave them when you installed them. That's why Runtime Broker only affects Microsoft Store apps.

When You Should Not Close Runtime Broker

Closing Runtime Broker is safe and won't damage Windows. However, if you're about to use a Microsoft Store app, it's better to wait for Runtime Broker to restart first. Close it, wait 30 seconds, then open your Microsoft Store app. This gives Runtime Broker time to start again and monitor the app properly.

If you find yourself closing Runtime Broker every day because it keeps using high CPU, the real problem is a Microsoft Store app that's broken. Closing Runtime Broker is a temporary fix — you should find and uninstall the misbehaving app instead. Closing the process over and over will not solve the underlying problem.

You do not need to close Runtime Broker for normal computer use. It uses very little CPU most of the time. If it's using a lot of CPU right now, something unusual is happening, and closing it will help you figure out what.

Frequently Asked Questions

Will closing Runtime Broker delete my files or break Windows?

No. Runtime Broker is a monitoring process, not a system process that Windows needs to run. Closing it will not affect your files, your settings, or Windows itself. The only thing that might stop working is Microsoft Store apps, and only while the process is closed.

How do I know if Runtime Broker is actually using a lot of CPU?

Open Task Manager with Ctrl+Shift+Esc and look at the "CPU" column. If Runtime Broker is using more than 10 or 15 percent, it's using more than it should. Anything above 25 percent is definitely a problem and worth closing.

Can I disable Runtime Broker permanently so it never starts again?

You cannot disable it through normal Windows settings because it's part of the operating system. You could disable it through Services, but Microsoft does not recommend this because it can cause Microsoft Store apps to stop working. Closing it when you need to is the safer approach.

What if I close Runtime Broker and my Microsoft Store app stops working?

Wait a few minutes for Runtime Broker to restart, then try opening the app again. If the app still won't work, restart your computer. This will restart all Windows processes, including Runtime Broker, and usually fixes the problem.

Is Runtime Broker a virus or malware?

No. Runtime Broker is a legitimate Windows process created by Microsoft. It's built into Windows 8 and newer versions. If you see a process called "Runtime Broker" using an unusual amount of CPU or doing something suspicious, it could be malware pretending to be Runtime Broker — but the real Runtime Broker itself is safe.