If you are reading this article, you may have seen the Runtime Broker process in the Task Manager window and wondered what this process is, and is it causing the sudden increase in CPU usage? This article will answer your questions.
What is the Runtime Broker process?
Runtime Broker (or Time Broker) is a Windows system process that manages permissions for popular apps you install from the Microsoft Store. It was first introduced in Windows 8 and continued to appear in all subsequent versions.
This process runs in the background and acts like a gatekeeper: It acts as an intermediary between universal apps and system resources like network, camera, and location. In other words, Runtime Broker ensures that applications have the necessary permissions to function properly without compromising the security of the system.
When you launch an app from the Microsoft Store, Runtime Broker checks whether the app has the necessary permissions to use system resources. Otherwise, it will request permission on behalf of the application. With the permission granted, the Runtime Broker acts as an intermediary between the application and the resources it needs to use.
For example, if you launch a photo editing application that needs access to your photos, Runtime Broker will request access to those images. Once approved, Runtime Broker will ensure the application only accesses photos and not other sensitive information. In this way, Runtime Broker protects Windows from security threats and unauthorized access.
Why does Runtime Broker use memory?
The Runtime Broker process only runs when the universal app needs access to system resources. Typically, this only requires a few megabytes of memory. But if an application constantly requests permissions or has permission problems, Runtime Broker will also run frequently and consume a lot of CPU power.
When inactive, Runtime Broker uses little memory, typically taking about 20-40 MB. When you start a universal app, you will see a memory increase of 500 to 700 MB.
Launching another universal app, Runtime Broker also does not use additional memory. And when closing all universal apps, Runtime Broker's memory capacity is reduced to about 20-40 MB.
Why does Runtime Broker suddenly increase CPU usage?
Now that you know what Runtime Broker is, you may wonder why it sometimes uses a large amount of CPU resources. You may notice this process appearing often when using Task Manager.
When running only in the background, Runtime Broker does not use CPU, only when running universal app, CPU increases to about 25-30% and then decreases again and this is a normal process. However, if you see Runtime Broker consistently using CPU usage up to 30% or higher, showing higher than expected memory usage, or suddenly increasing when not running the universal app, consider the reasons and solutions. fix below.
The reason may be because, when upgrading to Windows 10, it displays a few tips through notifications. This works like universal apps and participates in the Runtime Broker process. Users can fix this problem by disabling tips. Visit Settings > System > Notifications & Actionsthen turn off the option “Get tips, tricks, and suggestions as you use Windows“.
Another reason may be that some applications are not working properly, causing Runtime Broker to use more CPU than usual. In this case, you need to find the application that is causing the problem, make sure the application is updated to the latest version. If this doesn't work, try uninstalling and reinstalling the app. If the above two methods still cannot fix the problem, the only way is to notify the developer about this problem (if you don't need the app, you can uninstall it while waiting for an answer). from the developer).
Is it possible to disable Runtime Broker?
The answer is no, you cannot disable Runtime Broker. And you shouldn't do that because this process protects user privacy and security when running universal apps and it's also very lightweight when working properly, so there's no reason to disable it. If you think it is not working properly, you can stop this Runtime Broker process by right clicking on it in Task Manager and choose End Task.
After a few minutes, Runtime Broker will restart automatically. You should note that during this process relaunch, universal apps cannot successfully access settings and may not run.
Is Runtime Broker a virus?
The process itself is an official Windows component. While it is possible that the virus replaced the actual Runtime Broker with an executable of its own, that is highly unlikely. There have been no reports of viruses taking control of this process. If you want to be sure, you can check the basic file location of Runtime Broker. In Task Manager, right-click on Runtime Broker and select options Open File Location.
If the file is stored in directory “C:\Windows\System32” then you can be pretty sure you don't have a virus.
That said, if you still want a little more peace of mind, you can always scan for viruses with your favorite antivirus software. Be careful and carefree!
See more:
