RuntimeBroker.exe is a small 32KB system file in Windows 10/8 that is located in the System32 folder. If you open your Task Manager, you will see Runtime Broker running.
RuntimeBroker.exe in Windows 10/8
The file RuntimeBroker.exe runs only when you run a Windows Store app. If after starting your Windows 10/8 computer, you do not run any app, you may not see this file running in the Task Manager. Only when you open any Store/Modern app, will you see RuntimeBroker.exe running – this is because running any Windows 8/10 app triggers the RuntimeBroker.exe into action. But even if you close the app, RuntimeBroker.exe will continue to run the background consuming near-nil resources.
What does RuntimeBroker.exe do?
RuntimeBroker.exe monitors access to Windows API’s and ensure that apps do not violate the core security of Windows. It checks if the Windows Store app is when running is declaring all of its permissions to access your resources. This includes informing whether it has the permission or not. The process handles the security permission of processes like sensors, cameras, etc. In a way, it thus helps to secure your privacy when using Windows Store apps.
Is RuntimeBroker.exe a virus or malware?
If the RuntimeBroker.exe file is situated in your System32 folder, it is a legitimate Microsoft process. If not, it could be malware. You could right-click the file and check its Properties, if you have any doubts.
RuntimeBroker.exe taking a lot of memory
RuntimeBroker.exe normally leaves very a small footprint. In some cases, RuntimeBroker.exe may consume more resources, but does not release memory after the work is done, resulting in a memory leak. If your RuntimeBroker.exe consumes high memory and display high RAM usage, you may want to investigate your installed 3rd-party apps. Specifically, look at 3rd-party apps which you may have installed after you noticed this problem – especially those which display Live Tiles. Uninstall them one after the other and restart your PC and then check the memory utilization, to try and isolate the problematic app.
It should hopefully help.