What Runtime Broker Does and Why You Might Want to Stop It
Runtime Broker is a Windows background process that monitors whether programs are following Microsoft's app permission rules. It runs automatically and uses a small amount of your computer's memory and processing power. Most of the time you will not notice it, but on older computers or machines with limited memory, Runtime Broker can slow things down noticeably.
Runtime Broker itself is not malware or a virus — it is a legitimate Windows system file. However, if it is consuming too much CPU or memory, or if you simply want to reduce the number of background processes running, you have several ways to stop it. The methods range from temporary (stopping it just now) to permanent (preventing it from starting automatically).
Key Takeaways
- Runtime Broker is a Windows system process that checks whether programs have permission to access your camera, microphone, location, and other sensitive features.
- You can stop Runtime Broker temporarily through Task Manager, but it will restart the next time you restart your computer or when Windows needs it.
- Disabling it permanently requires either turning off app permission monitoring in Settings or using the Services app to prevent it from starting automatically.
- Stopping Runtime Broker may prevent Windows from enforcing app permissions, which means programs could potentially access your camera or microphone without your knowledge.
- If Runtime Broker is using excessive resources, the problem is usually a misbehaving program rather than Runtime Broker itself, and finding that program is often a better solution.
Stop Runtime Broker Right Now Using Task Manager
The fastest way to stop Runtime Broker immediately is through Task Manager. This method works right now but does not prevent it from starting again later.
Press Ctrl + Shift + Esc on your keyboard. Task Manager will open directly. If that does not work, press Ctrl + Alt + Delete, then click Task Manager.
Look for Runtime Broker in the list of running processes. If you do not see it, click the arrow next to Windows processes to expand that section. Click on Runtime Broker once to select it, then click the End Task button in the bottom right corner. Runtime Broker will stop immediately.
Your computer will continue to work normally. However, Windows will restart Runtime Broker the next time you restart your computer or the next time a program requests permission to use your camera, microphone, or location.
Prevent Runtime Broker From Starting Automatically Using Services
If you want Runtime Broker to stop starting automatically, you can disable it through the Services app. This is a more permanent solution than Task Manager, though you can always re-enable it later if you change your mind.
Press Windows key + R on your keyboard. A small box will appear. Type services.msc and press Enter. The Services window will open.
Scroll down through the list until you find App Readiness. Right-click on it and select Properties. In the Startup type dropdown, change it from Automatic to Disabled. Click Apply, then OK. This prevents Runtime Broker from starting when Windows boots up.
Close the Services window. You can now stop Runtime Broker using Task Manager if it is still running. The next time you restart your computer, Runtime Broker will not start automatically.
Turn Off App Permission Monitoring in Windows Settings
Another way to reduce Runtime Broker activity is to disable app permission monitoring in Windows Settings. This tells Windows to stop checking whether programs are using your camera, microphone, location, and other sensitive features.
Open Settings by pressing Windows key + I. Click Privacy & security in the left sidebar. You will see a list of permissions: Camera, Microphone, Location, and others.
For each permission you want to disable, click on it and toggle the switch at the top to Off. For example, if you click Camera, you can turn off camera access for all programs. Repeat this for Microphone, Location, and any other permissions you do not want programs to use.
When you turn off permission monitoring, Runtime Broker has less work to do and will consume fewer resources. However, this also means Windows will not warn you if a program tries to use your camera or microphone without your knowledge.
Check If a Specific Program Is Causing Runtime Broker to Use Too Much CPU
If Runtime Broker is using a lot of your computer's processing power, the problem is usually not Runtime Broker itself but a program that is constantly requesting permission to access something. Finding and stopping that program is often more effective than disabling Runtime Broker.
Open Task Manager again by pressing Ctrl + Shift + Esc. Click the Performance tab at the top. Then click Open Resource Monitor at the bottom. A new window will open.
Click the CPU tab. Look for RuntimeBroker.exe in the list. Click on it to expand it and see which program is making requests to it. The program listed underneath is the one causing Runtime Broker to work hard. If you do not need that program, you can uninstall it or prevent it from starting automatically.
Once you identify the culprit, you have options: uninstall the program, update it to a newer version that may be more efficient, or disable it from starting automatically using Task Scheduler or the program's own settings.
Re-Enable Runtime Broker If You Change Your Mind
If you disabled Runtime Broker and later decide you want it running again, you can turn it back on in a few seconds.
Press Windows key + R, type services.msc, and press Enter. Find App Readiness in the list, right-click it, and select Properties. Change the Startup type dropdown back to Automatic. Click Apply, then OK.
Restart your computer, and Runtime Broker will start automatically again. You can also re-enable individual permissions in Settings by going back to Privacy & security and toggling each permission back to On.
What Happens When Runtime Broker Is Disabled
When Runtime Broker is not running, Windows stops monitoring whether programs are using your camera, microphone, location, and other sensitive features. This means programs can potentially access these features without triggering a permission prompt or warning.
For most users, this is not a major concern if you trust the programs you have installed. However, if you are concerned about privacy or if you have programs you do not fully trust, keeping Runtime Broker enabled is the safer choice. The performance impact on modern computers is usually minimal.
If you disabled Runtime Broker because it was slowing down your computer, and you still notice slowness after disabling it, the problem was likely not Runtime Broker but something else — such as a virus, too many startup programs, or a failing hard drive.
Frequently Asked Questions
Is Runtime Broker a virus or malware?
No. Runtime Broker is a legitimate Windows system process created by Microsoft. It is not malware, though malware can sometimes disguise itself with a similar name. If you are concerned, check that the file is located in C:\Windows\System32 and that it is signed by Microsoft.
Will disabling Runtime Broker make my computer faster?
Only if Runtime Broker was using a significant amount of CPU or memory. On most modern computers, Runtime Broker uses very little resources and you will not notice a speed difference. If your computer is slow, the problem is usually something else.
Can I disable Runtime Broker without using Services?
Yes. You can stop it temporarily using Task Manager, or you can turn off individual app permissions in Settings. However, if you want to prevent it from starting automatically, the Services app is the most straightforward method.
What if I disable Runtime Broker and then a program crashes?
Disabling Runtime Broker does not usually cause programs to crash. If a program crashes after you disable it, the crash is likely unrelated. You can re-enable Runtime Broker using the steps above to rule it out.
Do I need Runtime Broker if I do not use my camera or microphone?
Runtime Broker still monitors other permissions like location and file access, even if you do not use your camera. However, if you have disabled all app permissions in Settings, Runtime Broker will have very little to do and will use minimal resources.