Windows 10: Why is Runtime Broker tied to EVERYTHING?

I don't know why but this irritates me. It's tied into just about any program I use.





:)

 

Runtime Broker in build 10586.29 on PC uses 67% of CPU usage with NAS/LAN impact

Runtime Broker in build 10586.29 on PC uses 67% of CPU usage. When broker is hogging the system I notice my NAS "MyCloud" HDD lights are blinking and the LAN light is ablazing. When runtime broker is killed in task manager the CPU usage goes down to 5%
and the NAS/LAN lights stop blinking. Not sure how to associate which process/service is tied to the NAS/LAN and runtime broker, so as to uninstall, disable or modify.

 

Runtime Broker in build 10586.29 on PC uses 67% of CPU usage with NAS/LAN impact

Hello

Have done the above suggestion many times, but I'm still at the point of not knowing how to identify process/service that is tied to the runtime broker hoarding the CPU and causing 67% usage. Need to know process/service in order to complete all the steps
in your suggested remedy.

Additionally I had a mapped network drive assigned to NAS, which I have disconnected. In doing so the runtime broker has settled down considerably. Maybe you may be able to investigate why a mapped drive to a NAS would cause this problem. The remedy would
be appreciated because I need to map a drive to the NAS.

Thanks

 

@gettheclicker:

This sums it up somewhat:

What Is “Runtime Broker” and Why Is It Running on My PC?

 

I think he means Runtime Broker now runs "multiple times" under any universal app, instead of showing one instance... this behavior is new in the 1709 build.

I ignore why Microsoft changed that, though, probably the same reasoning behind splitting services in 1703...

 

Well I suppose as long as it's not a virus I'll ignore it. I tried disabling it, big mistake.

 

Yeah, you should ignore it, otherwise you will break the UWP that Windows 10 uses, even for the settings app.