What Is Runtime Broker in Windows Task Manager? Fix High CPU Usage Issue

The Runtime Broker is a legitimate Windows process that manages permissions for Universal Windows Platform (UWP) apps, primarily those downloaded from the Microsoft Store. It ensures that these apps have the appropriate access to system resources while maintaining user privacy and security. This process constantly runs in the background to monitor and manage app permissions. While it typically uses minimal resources, sometimes Runtime Broker causes high CPU usage, especially if a specific app is misbehaving or requesting excessive permissions. This can be caused by various factors, including misbehaving apps, Windows tips and suggestions, or issues with OneDrive or other background processes. Let’s take a look at what Runtime Broker is in Windows Task Manager and how to fix the High CPU Usage Issue in Windows 11 and 10 PC.

What Is Runtime Broker in Windows Task Manager?

Runtime Broker (RuntimeBroker.exe) is a legitimate Windows system process introduced in Windows 8 and continued in Windows 10 and 11. Its primary function is to act as an intermediary between your UWP apps, such as Microsoft Store apps like Photos, Weather, or Xbox, and the system’s resources, including hardware, privacy settings, and security permissions. It checks if an app is allowed to access specific resources (like your location, microphone, or contacts) and then grants or denies that access based on your configured privacy settings and the app’s manifest.

Key Functions of Runtime Broker:

• Runtime Broker manages permissions for UWP apps, prevent them from accessing system resources without proper authorization.
• It verifies that apps declare all their requested permissions and notifies the user if an app is trying to access something it’s not allowed to.
• It acts as a security intermediary and helps protect the system from malicious or poorly behaving UWP apps.

Is Runtime Broker a Virus?

No, Runtime Broker is not a virus. It’s a legitimate Microsoft process included in all modern Windows operating systems. However, sometimes malware infection may alter the process and disguise itself as the Runtime Broker. To verify its authenticity:

• Check the File Location: Right-click Runtime Broker in Task Manager, select “Open File Location.” It should lead to C:\Windows\System32\RuntimeBroker.exe. If it points elsewhere, it could be malware.
• Verify Digital Signature: Right-click the file, select “Properties,” and check the “Digital Signatures” tab. It should be signed by Microsoft.
• Run an Antivirus Scan: Use Windows security (Defender) or a trusted antivirus program to scan for malware if you suspect.

If you confirm it’s the legitimate process, there’s no need to worry about it being a virus.

Why is Runtime Broker Causing High CPU Usage?

It is designed to run in the background and typically uses minimal CPU and memory resources. However, it can sometimes cause high CPU usage due to several reasons:

• Faulty or outdated apps: A poorly coded or outdated UWP app can cause Runtime Broker to overwork, leading to high CPU usage.
• Corrupted System Files: Damaged or corrupted Windows files can lead to abnormal Runtime Broker behavior.
• Outdated Windows or Drivers: An outdated operating system or drivers can cause compatibility issues, increasing CPU usage.
• Antivirus software: Some antivirus programs may interact with Runtime Broker, causing increased CPU usage.

Should I Disable the Runtime Broker?

No, you should not disable Runtime Broker. We have already discussed its a core system process that manages permissions for apps, especially those from the Microsoft Store, and disabling it can compromise your system’s security and privacy. However, if Runtime Broker causes persistent high CPU usage, you can minimize its activity by following the steps below.

A simple restart can resolve temporary glitches causing high CPU usage. Close all apps, reboot your system, and check Task Manager to see if the issue persists.

• Open the task manager using Ctrl + Shift + Esc key,
• locate the Runtime Broker from the list of processes running, right-click on it, and select End Task.
• This will disable the Runtime broker process and check if the CPU usage comes down.

Disable Windows Tips and Suggestions

Disable certain privacy settings that may be causing the high CPU usage. For example, turning off the “Get tips, tricks, and suggestions as you use Windows” option in Settings can significantly reduce the CPU usage of Runtime Broker. To do this:

• Press Win + I to open Settings and click on System from the left sidebar.
• Select Notifications on the right, scroll down to the Additional settings section and expand it.
• Here, Uncheck Suggested ways to get the most out of Windows and finish setting up this device, and Get tips and suggestions when using Windows options.

This simple tweak can immediately reduce the number of background triggers for the Runtime Broker.  Restart your computer and check if this fixes the high cpu usage problem.

Turn Off Background Apps

If the problem persists, you can try disabling background apps that may be triggering Runtime Broker activity.

• Open Settings (Win + I), go to Apps > Installed Apps.
• Click the three dots next to any app you don’t frequently use and select Advanced options.
• Scroll to the Background apps permissions section. From the drop-down menu, select Never.
• Repeat this for all unnecessary apps. This limits how many apps trigger Runtime Broker when you’re not using them.

On Windows 10, you can also disable background apps through Settings > Privacy > Background Apps.

Check for Corrupted System Files

Again, corrupted files can cause Runtime Broker to misbehave. Running System File Checker with the DISM restore health command scans for and repairs corrupted or missing system files.

• Open Command Prompt as an administrator. You can search for “cmd” in the Start menu, right-click, and select “Run as administrator.
• Type sfc /scannow and press Enter to scan for corrupted or missing files and attempt to replace them with correct versions from a cache or, if necessary, from a Windows installation source.
• If errors are found, run DISM /Online /Cleanup-Image /RestoreHealth to repair them.
• Wait for the scan to complete 100% and reboot your computer.

Reset or Reinstall Problematic UWP Apps

If a specific app is persistently causing issues, you can try resetting or reinstalling it.

• Go to Settings > Apps > Apps & features.
• Locate the problematic app (e.g., Photos, Xbox), click it, and select “Advanced options.”
• Choose “Reset” or uninstall and reinstall the app from the Microsoft Store.

Tweak the registry to Disable Runtime Broker

Still need help, apply the following registry tweak to disable the runtime broker process and check the startup of the High CPU usage problem.

• Press Windows key + R, type regedit, and click ok. This will open the Windows registry editor.
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc.
• Double-click on the “Start” DWORD and change the “Value data” from “3” to “4”.
• Click ok to save changes, close the registry editor and restart your computer.

Note: This may cause instability in UWP apps and is not advised unless you fully understand the consequences.

Create a New User Profile

A corrupted user profile can cause system processes like Runtime Broker to behave abnormally. Creating a new user account provides a fresh environment to see if the issue persists.

• Press Win + I to open Settings, and go to Accounts > Other users.
• Click Add account. Choose I don’t have this person’s sign-in information then select Add a user without a Microsoft account.

Enter a username and password. After creation, log out of your current profile and switch to the new one. If Runtime Broker CPU usage returns to normal, the original user account may be corrupt.

Additionally, some users have found that disabling the “Download from other PCs” feature in Windows Update can help reduce Runtime Broker activity.

• On Windows 11, Go to Settings > Windows Update > Advanced Options > Delivery Optimization and disable the “Download from other PCs” option.
• On Windows 10, the same setting can be found in Settings > Updates & Security > Delivery Optimization.

In addition, Outdated software can cause compatibility issues. To update:

• Windows: Go to Settings > Windows Update > Check for updates and install any available updates.
• Drivers: Use Device Manager or a trusted driver updater tool to ensure all drivers are up to date.

FAQ: Runtime Broker CPU Usage in Windows

What is Runtime Broker doing in the background?
It monitors permissions and ensures apps behave securely when accessing sensitive data.

Why does Runtime Broker use CPU even when idle?
Even if you’re not opening apps, background processes or live tiles can trigger it.

Can I delete RuntimeBroker.exe?
No, deleting it may cause system instability. Instead, control its behavior using the methods above.

How much memory/CPU should it normally use?
Less than 1% CPU and under 50MB RAM during normal operation.

Kelvin smith

I am Kelvin Smith, founder of TechAIThreads. I have completed a Bachelor of Arts (BA) and am a Microsoft Certified Professional (MCP). With a strong background in computer applications, I love writing practical guides on Microsoft Windows (11, 10, etc.), Android, cybersecurity, WordPress, and more.