Try restarting your system and check if the service’s usage goes back down to normal.
If the Runtime Broker is constantly using a significant amount of processing power, it isn’t normal and indicates a problem either with the system’s files. The spike in CPU usage can be caught if you open a UWP app and you’re fast enough to find Runtime Broker in Task Manager’s processes list. Runtime Broker will occasionally use a significant amount of processing power and you will see it spike in the CPU column in Task Manager however, it returns to 0% in a matter of seconds. If it isn’t running on your Windows 10 system, you should be worried. It’s also an essential app so it has to run no matter what. The service is light and you won’t notice it unless you check in Task Manager. Specifically, all UWP apps are supposed to declare what devices/information on a system they will access and the Runtime Broker service makes sure they aren’t stepping out of line.
This is an essential service that keeps an eye on what UWP apps are accessing on your system. Runtime Broker is a Windows service that runs in the background.
0 kommentar(er)
