Fix Runtime Broker High CPU Usage in Windows 10/11

The Runtime Broker is a legitimate Windows system process in Task Manager that helps manage permissions on your device for apps from the Microsoft Store. However, it can sometimes cause high CPU or RAM usage when misbehaving apps, excessive notifications, or background services repeatedly request permissions. If Runtime Broker is causing high CPU usage on your Windows 11 or your system feels slow, laggy, or unresponsive, especially just after sign‑in, this article is for you. Here, we explain what the Runtime Broker is, whether you should disable it, and show a few effective workarounds that help reduce CPU usage on Windows 11 and Windows 10.

What is the Runtime Broker in Windows 11 and 10?

The Runtime Broker (RuntimeBroker.exe) is a Windows system process introduced in Windows 8 and still used in Windows 10 and Windows 11. The main task of the Runtime Broker is to check whether the applications you are using on your Windows computer have all the required permissions to run. It monitors access to Windows APIs and ensures that apps do not violate Windows’ core security.

Runtime Broker acts as a security mediator between Universal Windows Platform (UWP) apps and the operating system.

In normal conditions:

• Runtime Broker should sit in the background using almost no CPU (0–1%).
• It may spike briefly (for a few seconds) when you open a Microsoft Store app or when Windows shows tips and suggestions.

However, if RuntimeBroker.exe is constantly at high CPU or memory usage for minutes or hours, something is wrong. It’s usually a misbehaving app or Windows feature, not the process itself.

Is Runtime Broker a Virus in Windows 11?

In most cases, the answer is No, Runtime Broker is a legitimate Microsoft process.

However, some malware can pretend to be Runtime Broker.

To Check if it’s genuine:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Go to the Processes tab.
3. Find Runtime Broker.
4. Right‑click it → Open file location.
5. Confirm the path is:
   • C:\Windows\System32\RuntimeBroker.exe

If it is not in System32 (for example, it’s in Downloads, Temp, or some random folder), it might be malware. In that case, run a full malware scan immediately (see the next section).

Should I Disable Runtime Broker on Windows 11?

Short answer: generally, no.

Runtime Broker helps protect your privacy and security by managing permissions for Microsoft Store apps. Fully disabling it can:

• Break some Store apps and notifications
• Weaken permission control for modern apps
• Lead to unexpected errors

When is it okay to disable or restrict it?

• On advanced systems where you never use Microsoft Store apps
• On lab/test machines, not on primary personal or business devices

For most users, instead of disabling Runtime Broker completely, it’s much safer to:

• Turn off unnecessary tips and suggestions
• Reduce background apps
• Tweak a few update and privacy settings

Below are safer, recommended methods before considering any permanent disabling.

Quick Checklist Before You Change Anything

Try these fast checks first they often fix Runtime Broker high CPU usage in Windows 11 and 10 without advance tweaks:

1. Restart PC once (cold restart, not just sleep).
2. Check for Windows updates and install any quality/security updates.
3. Scan for malware (Windows Security or a reputable third‑party AV).
4. Disable a few notifications & tips and background apps (steps below).

If Runtime Broker still causes 100% CPU or high memory usage, continue with the detailed fixes.

Fix 1: Check for a virus or Malware Infection

High CPU usage by any .exe process (including Runtime Broker) can be caused by malware. Let’s first verify the file location and confirm the file is in C:\Windows\System32. If you still want to confirm, you can run a full system scan to verify.

Run a full scan with Windows Security

1. Press Start and type Windows Security, then open it.
2. Click Virus & threat protection.
3. Under Current threats, click Scan options.
4. Choose Full scan.
5. Click Scan now and wait for it to complete.

If threats are found, let Windows Security quarantine or remove them, then restart your PC and see if Runtime Broker CPU usage drops.

Tip: For extra assurance, you can also run a one‑time scan with a reputable on‑demand tool like Microsoft Safety Scanner or Malwarebytes Free.

Fix 2: End the Runtime Broker Process (Safe Temporary Fix)

If Runtime Broker is consuming a lot of CPU or RAM right now, you can end the process. Windows will automatically restart it when needed. This is a quick way to stop the current spike and get your PC responsive again.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. On Windows 11, click More details if needed.
3. Under the Processes tab, find Runtime Broker.
4. Right‑click it → choose End task.

This often temporarily fixes high CPU or memory usage. If the problem returns frequently, continue with the next fixes to address the root cause.

Fix 3: Disable Tips, Tricks, and Suggestions in Windows

According to many reports on the Microsoft forum, disabling the “Show me tips about Windows” option in Settings will fix this problem and prevent RuntimeBroker.exe from consuming excessive resources on your PC.

To disable Show me tips about Windows, fallow bellow:

Windows 11

1. Press Windows + I to open Settings.
2. Go to System → Notifications.
3. Scroll down to Additional settings and uncheck:
   • Offer suggestions on how I can set up my device
   • Get tips and suggestions when I use Windows

Windows 10

1. Press Windows + I to open Settings.
2. Go to System → Notifications & actions.
3. Turn Off: Get tips, tricks, and suggestions as you use Windows

Restart your computer and monitor Task Manager to see if Runtime Broker CPU usage has dropped.

Fix 4: Turn Off Background Apps You Don’t Need

Again, Background apps can frequently wake the Runtime Broker to check permission‑related operations.

Turn Off Background Apps Windows 11

1. Open Settings → Apps → Installed apps.
2. Click the three dots (⋯) next to an app you don’t need running in the background.
3. Click Advanced options (if available).
4. Under Background apps permissions, select:
   • Never (or Power optimized, depending on options).

Repeat for all apps you don’t need running in the background (especially Store apps you rarely use).

Turn Off Background Apps Windows 10

1. Open Settings → Privacy.
2. In the left sidebar, click Background apps.
3. Toggle Let apps run in the background to Off (for a broad approach), or
4. Leave it On and turn Off individual apps you don’t want running.

This reduces unnecessary activity, saving CPU, RAM, and battery.

Check Which App Is Triggering Runtime Broker

Sometimes one specific app is responsible for most of the CPU spikes.

1. Open Task Manager (Ctrl + Shift + Esc).
2. On the Processes tab, expand Runtime Broker (if grouped), or keep it visible.
3. Observe Task Manager while you:
   • Open and close Store apps (Weather, Photos, Mail, etc.).
   • Use features like Widgets, Start menu news, or notifications.

If you notice CPU jumps when a particular app runs, try:

• Resetting the app:
  • Settings > Apps > Installed apps > (select app) > Advanced options > Reset.
• Or uninstalling the app if you don’t need it.

This is especially relevant for the Photos app and some OEM‑preinstalled Store apps, which are frequently mentioned in user reports about Runtime Broker spikes.

Fix 5: Adjust Delivery Optimization (Windows Update Peer‑to‑Peer)

While Delivery Optimization doesn’t directly belong to Runtime Broker, heavy update activity can contribute to overall high resource usage, making Runtime Broker spikes more noticeable.

Normally, Microsoft wants to make use of other PC’s on your Network and also another PC’s on the internet to deliver quicker updates to your computer. Disabling this option has helped many users to reduce the activity of Runtime Broker on their computers. To disable Updates from more than one place, follow the steps below.

Windows 11

1. Open Settings → Windows Update.
2. Click Advanced options.
3. Scroll to Delivery Optimization.
4. Toggle Allow downloads from other PCs to Off, or limit it to Devices on my local network.

Windows 10

1. Open Settings → Update & Security → Windows Update.
2. Click Advanced options.
3. Click Delivery Optimization.
4. Turn Off Allow downloads from other PCs, or limit to PCs on my local network.

This can indirectly reduce background network and CPU load.

Fix 6: Check Problematic Apps (Photos, Store Apps, Live Tiles)

Some specific apps are known to trigger high CPU usage by the Runtime Broker on Windows 11/10, especially when they constantly access photos, notifications, live tiles, or background tasks.

Common culprits:

• Photos app (background indexing / OneDrive integration)
• Weather, News, Widgets (live tile/widget updates)
• Poorly coded third‑party Store apps

Steps to troubleshoot app‑related Runtime Broker spikes

1. Close all Store apps (Photos, Mail, Calendar, Weather, etc.).
2. Watch Task Manager for a few minutes.
   • If CPU drops significantly, one of those apps is probably the cause.
3. Reopen them one by one and see when Runtime Broker spikes.
4. Once identified, you can:
   • Update the app from the Microsoft Store
   • Reset the app:
     • Settings → Apps → Apps & features (or Installed apps)
     • Click the app → Advanced options → Reset or Repair
   • Disable its background permissions

Fix 7: Use a Clean Boot to Find Conflicting Software

If none of the above helped, try a clean boot to see if third‑party software is triggering Runtime Broker.

Works on both Windows 10 and Windows 11:

1. Press Windows + R, type msconfig and press Enter.
2. Go to the Services tab.
3. Check Hide all Microsoft services.
4. Click Disable all.
5. Go to the Startup tab:
   • On Windows 11/10, click Open Task Manager.
6. In Task Manager’s Startup tab, Disable all non‑essential startup items.
7. Click OK and restart your PC.

Now check Task Manager again:

• If Runtime Broker high CPU usage is gone, re‑enable startup items and services one by one (or in small groups) until the problem returns. That reveals the conflicting program.

Note: Don’t leave security software or essential drivers permanently disabled. Re‑enable them after testing.

Advanced: Disable RuntimeBroker.exe via Registry Editor

If, after stopping the RuntimeBroker service, Windows work normally, and again after a system restart, the same problem starts with 100% CPU usage or High Memory usage, and the system becomes unresponsive, then you can permanently disable the RuntimeBroker process to get rid of this problem.

Note: Disabling the Runtime Broker didn’t affect your Windows 10 computer. The Runtime Broker isn’t a necessary process.

Disable Runtimebroker permanently

We can disable Runtimebroker permanently through the Windows Registry Editor. First of all, open the Run dialog box by pressing the combination of Windows + R key, then type regedit in it, then hit the Enter key.

Now, the Registry Editor will appear on your computer. Simply, navigate to the following registry on your computer:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBrokerSvc “Start”=dword:00000003

Here double click on the registry which is known as “Start” and change its value data from 3 to value data 4.

Note: Value data 4 means that you want to disabled while value data 3 means that it is manual. If you have entered the value data 2 it means that it is automatic. As we want to disable RuntimeBroker.exe so we have to set it to 4 here.

Once you have disabled the runtime broker process in the Windows Registry Editor, restart your Windows computer. Now, on the next start, you won’t get a high CPU usage issue in Windows 10 PC.

Note: If you notice issues with apps or notifications afterward, revert this change by setting the value back to 3 (Manual) or 2 (Automatic).

Frequently Asked Questions