Runtime Broker is a built-in Windows process that manages permissions for apps installed from the Microsoft Store. It runs quietly in the background and helps ensure that apps access features such as your microphone, camera, location, or notifications only when they’re allowed to. Under normal circumstances, Runtime Broker uses very little CPU and memory. However, it can occasionally start consuming a large amount of CPU resources due to a misbehaving app, incorrect Windows settings, corrupted system files, or a software bug. When this happens, your PC may slow down, the cooling fan may run more often, and Task Manager may show Runtime Broker using an unusually high percentage of CPU. In this guide, we’ll explain what causes Runtime Broker’s high CPU usage and the most effective ways to fix it on Windows 11.
Why Is Runtime Broker Using High CPU on Windows 11?
Runtime Broker normally uses less than 1% of your CPU and only becomes active when apps request access to Windows features and permissions. If it continues using a high CPU for several minutes, something is preventing the process from working normally.
Some of the most common causes include:
- A misbehaving Microsoft Store app: A buggy or outdated app may repeatedly request permissions, causing Runtime Broker to remain active.
- Too many background apps: Apps running in the background can continuously communicate with Runtime Broker, increasing CPU usage.
- Windows tips and notification settings: Features such as Windows tips, suggestions, and frequent notifications can trigger Runtime Broker more often than necessary.
- Corrupted system files: Damaged Windows system files can interfere with normal system processes, including Runtime Broker.
- Windows update bugs: In some cases, a recently installed Windows update may temporarily cause abnormal CPU usage until Microsoft releases a fix.
- Malware disguised as Runtime Broker: Although uncommon, malicious software can use a similar process name to hide its activity and consume excessive system resources.
1. Restart Your Computer
A temporary Windows glitch or a background process that didn’t close properly can cause Runtime Broker to use an unusually high amount of CPU. Restarting your PC ends stuck processes, reloads Windows services, and often resolves the problem.
After your computer restarts, open Task Manager (Ctrl+Shift+Esc) and check whether Runtime Broker’s CPU usage has returned to normal. If it is still consuming excessive CPU usage, proceed to the next solution.
2. Close Unnecessary Background Apps
Runtime Broker works closely with apps, especially those installed from the Microsoft Store. If one of these apps becomes unresponsive or frequently requests permissions, Runtime Broker may remain active and use more CPU than normal.
Close apps you aren’t using, then check whether CPU usage drops. If the problem only occurs after opening a particular app, update or reinstall that app to resolve the issue.
You can also prevent unnecessary apps from running in the background:
- Open Settings > Apps > Installed apps.
- Click the three-dot menu next to the app and select Advanced options (if available).
- Under Background app permissions, choose Never.
If Runtime Broker continues to use high CPU, proceed to the next solution.
3. Turn Off Windows Tips and Suggestions
Windows occasionally displays tips, suggestions, and welcome experiences to help you discover new features. These notifications can trigger Runtime Broker in the background, and on some systems, disabling them reduces unnecessary CPU usage.
To turn off Windows tips and suggestions:
- Open Settings > System > Notifications.
- Scroll down and click Additional settings.
- Uncheck the following options:
- Suggest ways to get the most out of Windows and finish setting up this device
- Get tips and suggestions when using Windows
- Restart your computer and check Runtime Broker’s CPU usage in Task Manager.
4. Scan Your PC for Malware
Malware can consume excessive system resources or disguise itself as a legitimate Windows process. While the genuine Runtime Broker process is safe, malicious software with a similar name may be responsible for unusually high CPU usage.
Run a full system scan using Windows Security to rule out malware:
- Open Settings > Privacy & security > Windows Security.
- Click Virus & threat protection.
- Select Scan options and choose Full scan.
- Click Scan now and wait for the scan to complete.
If Windows Security detects any threats, remove them and restart your PC. Then check whether Runtime Broker’s CPU usage has returned to normal.
5. Repair Corrupted System Files Using SFC and DISM
Corrupted or missing Windows system files can prevent built-in processes from working correctly. If Runtime Broker continues to use high CPU after trying the previous fixes, repairing the system files may resolve the problem.
- Open Command Prompt as an administrator.
- Run the following command and wait for the scan to finish:
sfc /scannow
- If SFC reports that it found problems but couldn’t fix them, run these DISM commands one at a time:
DISM /Online /Cleanup-Image /RestoreHealth
- Restart your computer after the scan completes.
Once Windows starts again, open Task Manager and check whether Runtime Broker’s CPU usage has returned to normal.
6. Install the Latest Windows Updates
If Runtime Broker started using high CPU after a recent change or due to a Windows bug, installing the latest updates may resolve the issue. Microsoft regularly releases updates that fix performance problems, improve system stability, and address known bugs.
To check for updates:
- Open Settings > Windows Update.
- Click Check for updates.
- Download and install any available updates.
- Restart your computer if prompted.
After your PC restarts, monitor Runtime Broker in Task Manager. If CPU usage remains unusually high, try the final solution below.
7. Perform a Clean Boot
If none of the above solutions work, a third-party service or startup program may be causing Runtime Broker to consume excessive CPU resources. Starting Windows in a Clean Boot state loads only essential Microsoft services, making it easier to identify software conflicts.
- Press Windows + R, type msconfig, and press Enter.
- On the Services tab, check Hide all Microsoft services, then click Disable all.
- Switch to the Startup tab and click Open Task Manager.
- Disable all unnecessary startup apps.
- Restart your computer.
If Runtime Broker’s CPU usage returns to normal after the Clean Boot, re-enable the disabled services and start up apps one at a time until you identify the software causing the issue.
Conclusion
Runtime Broker is an essential Windows process and normally uses very little CPU. If it suddenly starts consuming excessive processor resources, the cause is usually a misbehaving app, incorrect Windows settings, corrupted system files, or a software bug.
In most cases, restarting your PC, closing unnecessary background apps, disabling Windows tips, installing Windows updates, or repairing system files with SFC and DISM will resolve the problem. If the issue continues, performing a Clean Boot can help identify whether a third-party application is responsible.
If Runtime Broker still uses a high amount of CPU after trying every solution, consider checking for newer Windows updates or contacting Microsoft Support, as the problem may be caused by a known Windows issue.
Frequently Asked Questions
No. Runtime Broker is a legitimate Windows process that manages permissions for Microsoft Store apps. However, malware can sometimes disguise itself using a similar name. If Runtime Broker is consuming unusually high CPU or memory, run a full system scan with Windows Security to rule out malware.
Under normal conditions, Runtime Broker uses very little CPU and only becomes active when an app requests access to Windows features such as the camera, microphone, or location. It should return to near 0% CPU usage after the request completes.
Runtime Broker may use more memory than usual if a Microsoft Store app is malfunctioning, too many apps are running in the background, or Windows is processing notifications and app permissions. In most cases, memory usage returns to normal after closing the problematic app or restarting your PC.
Yes. You can end the Runtime Broker process from Task Manager if it’s using excessive CPU or memory. Windows will automatically restart the process when it’s needed. However, if the problem keeps returning, it’s better to identify and fix the underlying cause rather than repeatedly ending the process.
No. Runtime Broker is a built-in Windows process, and disabling it is not recommended. It helps manage app permissions and supports Microsoft Store apps. Instead of disabling the process, troubleshoot the underlying cause of the high CPU usage using the solutions in this guide.
