New
#10
Thanks for suggestion but I've already done that. The previous "Runtime Broker" errors with earlier upgrades dealt with RB
causing high CPU and memory usage. The workaround for that was a registry tweak to stop Runtime Broker. My RB issue is that it has stopped working. I tried the registry tweak just to see what happens and it did not help.