# RuntimeBroker.exe

Windows Process: Microsoft Corporation

Also called runtime broker, runtimebroker

Windows, System Component

A Windows process that brokers permissions and background work for Microsoft Store and UWP apps.

## What you need to know

This sits between Store apps and the rest of Windows.

Runtime Broker checks what a Store or UWP app is allowed to do. Brief CPU use when an app starts or asks for a permission is common.

- **Safe?**: Usually yes

  **Should I close it?**: Usually no

  **Multiple copies?**: Can be normal

Feex says

Runtime Broker looks mysterious because the app name is not on the process. I would see which Store app just opened before I end the broker.

## What is RuntimeBroker.exe?

RuntimeBroker.exe is a Windows helper that mediates between Microsoft Store and UWP apps and the operating system.

## What does it do?

It enforces capability checks: camera, files, background tasks, and similar permissions. It is not your browser and not a driver.

## Why is it running?

It starts when a Store or UWP app needs a brokered capability. Idle copies can sit after an app has been used.

## Why are there multiple copies?

Windows can start more than one broker for different app packages. A few copies are not automatically a problem.

## Is it safe?

Usually safe

The legitimate file is in System32 and signed by Microsoft. Persistent high CPU with no Store app in use is a troubleshooting case, not a reason to delete the file.

A legitimate copy normally runs from:

`C:\Windows\System32\RuntimeBroker.exe`

- Expected publisher: Microsoft Corporation
- Expected path: System32

## Can I end it?

Usually no

Ending it can close or break a Store app that needed the broker. It is not a general speed-up.

## Can I remove it?

No

Do not delete RuntimeBroker.exe. Store and UWP apps depend on it.

## Should it start with Windows?

It starts on demand with Store and UWP apps. You should not add or remove it as a startup program by hand.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Short spikes when an app starts or asks for a permission

  **Memory**: Usually modest

  **Disk**: Low

  **Network**: Depends on the app behind it

## File information

| Executable name        | RuntimeBroker.exe                     |
| ---------------------- | ------------------------------------- |
| Common legitimate path | C:\Windows\System32\RuntimeBroker.exe |
| Publisher              | Microsoft Corporation                 |
| Signature expectation  | Signed by Microsoft Windows           |

## Common problems

### Stuck high CPU

A misbehaving Store app can keep the broker busy. Note which app you opened last. Restart that app before you end the broker.

### Many copies

Several brokers can exist. Count alone is a weak signal. Path and signature matter more.

## Troubleshooting

Diagnose before you change anything destructive.

### Confirm the path and signature

Open the process properties and check that RuntimeBroker.exe runs from the expected folder and is signed by the expected publisher. This is the first check, not a Registry edit.

### See what the process is doing

Task Manager can show CPU, memory, disk, and GPU. High use during an obvious job is often normal. High use when the PC is idle needs a closer look at the related app or service.

### Avoid destructive first steps

Do not delete RuntimeBroker.exe, disable critical services without knowing the effect, or edit the Registry as the first move.

## Technical details

Technical details

| Image name   | RuntimeBroker.exe                |
| ------------ | -------------------------------- |
| Related apps | Microsoft Store and UWP packages |

## Related

These entities connect to this article. Type is shown on every link.

[What is a Windows process: Guide](https://feex.it/wiki/software/system/what-is-a-windows-process)[How to read Task Manager: Guide](https://feex.it/wiki/software/system/how-to-read-task-manager)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft Learn: Runtime Broker ](https://learn.microsoft.com/windows/uwp/)· UWP platform documentation

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Windows Process

  **Publisher**: Microsoft Corporation

  **Executable**: RuntimeBroker.exe

  **Typical path**: C:\Windows\System32\RuntimeBroker.exe

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/runtimebroker.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)