Tutorials

Fix high cpu and ram consumption of runtime broker

Table of contents:

Anonim

Having problems with the CPU and RAM consumption of Runtime Broker ? Well, from today it will stop being so, because we bring you a tutorial in which we tell you how to solve the high consumption of Runtime Broker. There is no doubt that Runtime Broker is necessary for Windows 10. It is a process responsible for managing the permissions of the Windows Store applications.

The bad? That Runtime Broker consumes a lot of CPU and RAM. But now there is something you can do about it and that is what we will see in this article.

Fix the high CPU and RAM consumption of Runtime Broker

To solve the high CPU and RAM consumption of Runtime Broker let's go by steps:

1- Check what the process consumes

First things first, see if you consume so much to worry. This can be done quickly from Windows Task Manager. Once inside, locate it and without seeing that Runtime Brocker exceeds 15% of consumption, you have to close it. Finish the task and go. This allows you to fix it only temporarily, let's now move on to the following points.

2- Deactivate Runtime Broker

Now is the time to deactivate it, you will have to deactivate the tricks, tips and suggestions of Windows 10. How? Following these steps: Open Settings in Windows 10> System> Notifications and actions> Get tricks, tips and suggestions while using Windows ". Just disable this and you're done.

Hasn't it worked for you? Could be due to other apps

The problem could be in conflicting apps:

  • Check if you have pending updates (if any, update).If you have doubts about an application, try uninstalling it, installing it again and then restarting the PC.

In addition, to continue reducing the consumption of background processes (remember that they will continue to work), we recommend doing the following: Settings> Privacy> Background applications . Here deactivate the ones you do not use or you do not want to receive any type of alert or notice.

With all this that we have told you, you should solve the high consumption of Runtime Broker successfully. If you have any doubts, can you ask us?

Tutorials

Editor's choice

Back to top button