its fixed now I think, but last three days I have been getting random attacks of runtime broker using 25% CPU randomly and eating 1.9 gb of ram before releasing it. It was associated with Onedrive activity. I made the normal changes that stop the runtime broker from running but it kept going.
Then I remembered I had played some music last week and since this user is only new, I hadn't set a default music player so it had loaded Groove and then groove proceeded to gather all my music files. I closed window and forgot all about it since I then loaded Foobar2000 and set it up.
I just checked, Groove was set to get music off Onedrive as well as locally, so must have a timer when it goes to check the music folders I have on Onedrive to see if anything new. Removing Onedrive from folder list seems to have stopped Runtime broker.
It wasn't a big problem, just a curious one as it would do it for about 20 minutes and then just stop as suddenly as it started.
This might help someone figure out same problem
Then I remembered I had played some music last week and since this user is only new, I hadn't set a default music player so it had loaded Groove and then groove proceeded to gather all my music files. I closed window and forgot all about it since I then loaded Foobar2000 and set it up.
I just checked, Groove was set to get music off Onedrive as well as locally, so must have a timer when it goes to check the music folders I have on Onedrive to see if anything new. Removing Onedrive from folder list seems to have stopped Runtime broker.
It wasn't a big problem, just a curious one as it would do it for about 20 minutes and then just stop as suddenly as it started.
This might help someone figure out same problem
