What is Runtime Broker and what to do if runtimebroker.exe is using the processor?

Share on facebook
Share on twitter
Share on linkedin
Share on telegram
Share on whatsapp


What is Runtime Broker and what to do if runtimebroker.exe is using the processor?

In Windows 10, you may see the runtime broker procedure (RuntimeBroker.exe) in Task Manager, that first appeared in the version 8 of the system. It is a system procedure (regularly not a virus), but from time to time it can cause a high CPU or RAM load.

Directly what runtime broker is, or rather, what this procedure is responsible for: manages permissions for modern Windows apps 10 UWP from the store and does not typically take up a significant amount of memory or use a noticeable amount of other resources. of the computer. Despite this, in some cases (often because an application does not run correctly), this may not be the case.

High CPU and memory load solution caused by Runtime Broker

If the runtimebroker procedure.exe consumes a lot of resources, there are several alternatives to fix it.

Clear the task and restart

The first method of its kind (in case the procedure uses a lot of memory, but it can also be used in other cases) is offered on the official Microsoft website and is very easy.

  1. Open Windows Task Manager 10 (Ctrl + Shift + Esc keys, or right-click the Start button – Task Manager).
  2. If only active programs are displayed in Task Manager, Click the button “Details” In the bottom left.
  3. Search for Runtime Broker in the list, select this procedure and click the “Delete task”.
  4. Restart the computer (restart exactly, do not turn off and restart).

Uninstall the app causing the problem

As mentioned previously, the procedure has to do with apps from the windows store 10 and if the problem occurred after installing some new apps, try uninstalling them if they are not essential.

You can uninstall an app through the context menu of the app tile in the Start menu or Settings – Applications (for versions prior to Windows 10 1703 – Setting – System – Applications and Features).

Disable features of Windows Store apps 10

The next feasible option that can help fix the high load caused by Runtime Broker is to disable some features associated with store apps:

  1. Go to Settings (teclas Win + I) – Privacy – Background apps and disable background apps. If this works, you can enable background run permission for an app at the same time until the problem is identified.
  2. Go to Settings – System – Notifications and actions. Disable “Show tips, directions and recommendations when using Windows”. Disabling notifications on the same settings page may also work.
  3. Restart your computer.

If none of that helps, you can try to check if you are truly a system runtime broker or (which in theory could be) a third-party file.

Virus check in runtimebroker.exe

To find out if runtimebroker.exe is a virus, you can perform the following simple steps:

  1. Open Windows Task Manager 10, search for Runtime Broker (or runtimebroker.exe on the Details tab, right-click and select “Open file location”.
  2. By default, the file must be located in the WindowsSystem32 and if you right-click and open “Properties”, you will see that “Microsoft Windows” is signed on the tab “Digital signatures”.

If the file location is different or there is no digital signature, run an online virus scan with VirusTotal.

Subscribe to our Newsletter

We will not send you SPAM mail. We hate it as much as you.