Wednesday, 10 February 2016

Windows 10 Runtime broker CPU usage issue fixed

There is a lot of un-useful and conflicting information on this  issue around the net, so I thought I'd post my fix here, in case it helps anybody else.

Issue: A process called 'Runtime Broker', runs away with CPU resources and maxes it at 100%. I found this often happens immediately after I resumed from standby on my desktop. Killing the process fixes the issue, but not the cause.

Very brief background: Runtime Broker isn't the issue itself, as it is a process used by various other background apps and processes - so it's a case of finding the app or feature causing the problem.

Fix: Remove any NAS or remote locations from Libraries (or just the photos map in my case). All my data sits on my NAS, which all my other devices point at. However, there is no need to have those remote locations included in 'Libraries' within Windows, instead just change the default / storage locations of the system folders 'Documents', 'Photos' etc, it achieves the same thing if you're only mapping a single location.

Fuller explanation and credit due here: https://www.itunity.com/article/windows-10-runtime-broker-slow-performance-solved-2581

Hope it helps!