Windows

Runtime broke runs on my pc – virus or windows program?

Once we click on the power button of our Windows-based PC, there are many things that happen in the background that we do not see. For example, a good number of processes and programs are loaded together with the operating system itself in a transparent way for us. This is the case, for example, of the Runtime Broker process that we will talk about in depth so that you know what it really is.

When we say that along with the Windows operating system, many processes start up and run in the background, these correspond to a multitude of elements. With this, what we want to tell you is that some of these processes belong to Windows itself, others to third-party programs, and there may even be malicious ones. The latter are not the most common, but they can occur if we have suffered some kind of attack on the PC.

All this is something we have to live with when using Microsoft software , since after installing the Windows system, a series of system processes are automatically executed. But we must not detract from these elements, since many of them are essential for the proper functioning of the equipment and all its components. The same thing happens in most cases when we install and run an application here.

This is due to the fact that these programs also load in memory a series of own processes and libraries necessary to function. The problem with all this is that some of these consume high RAM and CPU memory, which will affect the rest of the PC.

What is the Runtime Broker process

The first thing we should know when taking a look at the background processes that run in Windows, is how to see them. Well, for this we can use the Task Manager, a section that we access using the key combination Ctrl + Shift + Esc. Here, in the Processes tab, we find all those that are running at that moment, everything it in real time. In fact, here we will have the possibility to see the consumption of RAM, CPU, network or disk that each one of them does at that specific moment.

Well, once we know these, say that many of the processes that run on the system, can be easily identified by name. However, many others are much more complex, so when identifying them, things get a little more complicated. Serve as an example the case in which we want to focus on these same lines, we refer to the process called Runtime Broker.

For all those who at some point have had doubts about it, we will tell you that you have nothing to fear. To say that Runtime Broker is a completely legitimate process from Microsoft itself that was implemented for the first time in Windows 8. At the same time we continue to find this process running in Windows, so it is still present among the long list of these when opening the Task Manager.

What is the task of this process in Windows

Once we know its real origin, we may also be interested in knowing its reason for being on the computer, running in the background. For those of you who do not know, we will tell you that this is a process in charge of controlling all the universal UWP applications in Windows. Both those that are installed by default, as well as those that we download from the official store, the Microsoft Store.

In fact, Runtime Broker is in charge of making sure that they comply with all the permissions that we have previously configured. With this we talk about permissions such as access to the microphone, the webcam, or the location, thus ensuring that this data also does not come out of the UWPs that use them. Of course, at the same time we must know that by default it is always running, consuming around certain resources of the computer.

To give us an idea, the Runtime Broker process can consume a few megabytes of RAM on the PC. What’s more, we are going to find several of these elements working at the same time, each of them with its individual RAM consumption.

Should I close, or not, the Runtime Broker process

To all this that we tell you, we can add the fact that the use of RAM shoots up when we run some of these Windows 10 UWP applications . But this is something temporary and that will go down as we close the program in question. On the other hand, regarding the use of the computer’s CPU, this consumption of the process when we have a UWP application running, could sometimes increase up to 25%.

The main reason for this significant rise is that some of these universal applications are constantly running in the background. Therefore, when one of them takes focus and goes live, the CPU usage could increase considerably. Of course, in any case, we do not recommend ending this process because it is a vital element for the security of the operating system.

On the other hand, we must bear in mind that the expenditure of resources in this sense is not very high, all despite the fact that it may sometimes increase. But this upload is usually temporary, so deactivating it is not worth it, mainly for security- related reasons .

How to know if it is a virus

We have already mentioned that Runtime Broker is a very important element for the security of our operating system. This is something that is especially evident when we work with Windows UWP applications. That is why, at least initially, the process can be said to be totally reliable. However, there is always the probability that some type of malware has taken control of it, something that can happen almost with any other Task Manager process.

To check this fact and if it is a virus or not, from the Task Manager itself we just have to right-click on that item. In this case we select the option to Open file location. Under normal conditions this should lead us to the following route:

C:/Windows/System32

Here we can see the program responsible for this process. But in the event that it sends us to a somewhat stranger disk location, what we must do is scan the computer with an antivirus, for example with Windows Defender.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button