What is Runtime Broker &why it Use So Much Memory?

Leave a comment

Microsoft introduced the Runtime Broker process (RuntimeBroker.exe) in Windows 8 and continued to use it in Windows 10.

Windows Runtime Broker is a legitimate process, but it has a poor reputation for inhancing CPU load and memory usage on systems sporadically.

You may have noticed already that Runtime Broker is not always active if you monitor the Windows Task Manager with Ctrl-Shift-Esc or if you use a more advanced process monitor like Process Explorer.

If we look at it closely, it appears to be associated with Universal Windows Apps (those installed through Windows Store, those added as part of the operating system, and sideloaded apps).

The guide provides information about the process, as well as tips on how to handle the high CPU load it can cause.

Runtime Broker High Cpu
Runtime Broker High Cpu

Runtime Broker

When you open the Windows Task Manager on Windows 10, you can find Runtime Broker under processes and details.

Windows 10’s Task Manager separates processes into apps and background processes. The Runtime Broker may appear in one or both of these categories depending on its status. If you want a clearer picture, click on Details and find it there.

Due to the fact that Runtime Broker is connected to Universal Windows Applications, you will notice that it becomes active whenever one of these softwares is launched.

Specifically, Runtime Brokers are responsible for checking whether the requested permissions have been declared by these applications and providing you with information on this.

In other words, it acts as a security middleman between the app and the data and hardware on the device.

Runtime Broker causing high CPU load

Running Runtime Broker on Windows 10 caused high CPU loads as early as 2015, and on Windows 8 it used a lot of memory as early as 2012.

It may also eat up a lot of memory, especially if a faulty app is to blame:

The Runtime Broker is a Windows process in Task Manager that manages permissions for apps from the Windows Store on your PC. The Runtime Broker should use a few megabytes of memory, but in rare cases, it may consume a gigabyte or more of memory when a faulty application is running.

Quick temporary Fix

If the Runtime Broker Process consumes more than 15% of memory, Microsoft recommends killing it.

You may have a problem if you are using a lot of RAM and your PC is running slowly. Open Task Manager by pressing Ctrl+Shift+Esc and then check how much memory Runtime Broker uses on the Processes tab. If it’s using more than 15% of your memory, there’s probably a problem with an app on your computer. By selecting Runtime Broker in the list, selecting End task to shut down Runtime Broker, and restarting your computer, you can stop Runtime Broker from using so much memory.

  • The Task Manager can be accessed by pressing Ctrl-Shift-Esc.
  • The Runtime Broker process will appear in the list when you right-click it.
  • From the context menu that appears, select End Task.
  • Restart the PC.

Runtime Broker will launch again when a Universal Windows Application is launched, so this is only a temporary solution.

Disable get tips, tricks, and suggestions

The Runtime Broker process is executed when any feature of Windows 10 is powered by a Universal Windows Application.

As a result, you might see the process thrashing the hard drive, causing high CPU usage, or high memory usage, even though no Windows application is running at the time.

Windows users’ tips and suggestions can be disabled by disabling the application that displays them.

  • Windows 10’s Settings application can be opened by pressing the Ctrl-I key.
  • Access Notifications & Actions from the System.
  • You can turn off “Get tips, tricks, and suggestions as you use Windows” by finding it and switching it off.

A misbehaving application

If you notice that a particular application is consuming a lot of memory, disk space, or load on Runtime Broker, you may attempt the following:

  • Delete the app if it is not essential and you will be done with the issue.
  • Detect and download any updates available to the app, then install them to find out if they have resolved the issue.
  • Try uninstalling the app and reinstalling it after restarting your PC if that does not work.

Limit the number of background apps

Runs in the background may be one of these applications. This means that they will continue running despite not being in the foreground.

The following methods can be used to control the behavior:

  • Launch the Settings application with Windows-I.
  • Navigate to Privacy > Background Apps.

Turn off any software that you don’t need to run in the background. You may lose functionality such as the application’s ability to send notifications or stay current as a result.

Other fixes

You will find dozens of suggestions on how to fix Runtime Broker issues if you search the Internet.

  • Windows Spotlight (which changes the screen background frequently) should be changed to Picture for the local screen background. Under Personalization > Lock Screen in Settings, you can change your lock screen.
  • Disable P2P updates under Settings > Update & Security > Advanced Options > Choose how updates are delivered. There, you can switch off the option.

You may have the same issue if you run any other program as an application.

Check if Runtime Broker is a virus

In addition, you might also want to check if Runtime Broker is malware or a legitimate Windows process.

Check if RuntimeBroker.exe is located in c:\windows\system32\.

  • Open the Task Manager by pressing Ctrl-Shift-Esc.
  • Under processes, locate the Runtime Broker process.
  • Click the “open file location” menu option when you right-click on the process.

Using this command, you can view where the process has been started from. Anything but c:\windows\system32\

Can I Disable It?

You cannot disable the Runtime Broker. In any case, you shouldn’t. When running universal apps, it’s crucial to protect your privacy and security. Additionally, it is very lightweight when it is running correctly, so there isn’t much reason to disable it. It is possible to end the Runtime Broker process in Task Manager by right-clicking it and choosing End Task if you think it is misbehaving.

Leave a Reply

Your email address will not be published.