Few users know what kind of program it is - Runtime Broker, and most often they learn about its existence when the computer starts to freeze. Then, opening the "Task Manager", they see that the consumption of resources by this process is excessively high.
The article will tell you what Runtime Broker is, why it loads the processor and RAM, and will also give recommendations for fixing the problem.
Runtime Broker - what is it
First, let's define this process in order to have an idea of what we are dealing with. So, Runtime Broker is a process that is responsible for running applications from the Microsoft Store. To be more precise, it helps manage their permissions. After starting the computer, it also starts up and continues to work in the background, without disturbing the user. Its load on the central processor and RAM is minimal, so if you notice problems with your computer that are related to Runtime Broker, you need to take some action.
Runtime Broker loads RAM
We found that Runtime Broker is a process that consumes a minimum of RAM. To be precise, just a few megabytes. But at some point you may notice that one gigabyte of space takes up more. Now we will figure out what to do in this case.
We will not go into the reasons, they are all at the system level, it is important to know how to fix the situation. And this is done as simple as possible. First of all, you need to complete the process in the Task Manager, and then restart the computer. After that, the problem should disappear.
Runtime Broker loads the processor
We have already talked about RAM, but this process can also load the central processor. In fact, if everything is clear with RAM - the system malfunctions are the cause of the problem, then everything is not so simple with the CPU. It can be viruses that make changes to the process, or it can be a common system glitch. In any case, first restart the computer, perhaps this will help. If not, then read the article further.
Solution
We have already found out that Runtime Broker is the process responsible for the operation of applications from the Microsoft Store, as well as the likelihood of it becoming infected with the virus is excessively small. Therefore, if you observe excessive consumption of resources by this process, it means that it is necessary to solve the problem at the system level. That is what we are going to do now.
Turn off notifications
We know that Runtime Broker is a process that just won't load the system, so the problem lies elsewhere. Many users have noticed the connection of the process with system notifications, saying that when they are turned off, Runtime Broker normalizes.
- Enter the system settings.
- Open the System menu.
- Go to the "Notifications and Actions" section.
- Turn the entire switch to the off position.
After that, restart the computer - the problem should be resolved. But just in case, double-check it with an antivirus from a third-party developer, possibly malware is to blame for everything.
Conclusion
Now you know that Runtime Broker is a process that should not load the system, and if this happens, you need to urgently take action. Using the instructions above, you can easily solve the problem.