runtimebroker.exe bug - something that helped me tame it

[eagl]

Hello,

I'm sure most of you with windows 10 have had some version of the runtimebroker.exe bug... er... "feature", where it either grabs all your cpu cycles, grabs and won't release all your memory, or seems to be doing something over the network all time (or all 3 of these).  I did, and here's what I think was doing it.

Apparently windows 10 will search your network for, and automatically add, any shared media libraries or folders.  These are the usual "videos", "photos", and "music" folders.  On my network, I have a windows home server box that is also a media server, and windows 10 automatically added these shared folders to the "libraries" on all 4 of my win10 computers.  Unfortunately if not indexed properly, the default action of windows 10 will be to absolutely beat the shxt out of the hard drive hosting those networked folders that are in the win10 library.  As a simple example of what is going on behind the scenes, the win10 default app "photos" will automatically crawl all libraries looking for duplicates, and attempt to build albums and collections.  Well, with my computer this process never ends so on 2 of my 4 win10 computers runtimebroker.exe would take 25-50% cpu time, over 80% of physical ram, and saturate the network attempting to download info from the shared library folders.

I think that removing the networked folders from each computer's list of libraries has at least partially fixed the problem.  I'll have to see if it is permanent or if win10 will re-add the networked folders to the library folder list again, restarting the destructive thrash of my WHS hard drives.

Thought this might help.. there are a couple other things that can make runtimebroker.exe go rogue, but this one was the one that got me and it was destroying my server's drives.

[Chalenge]

It's resident and when I open a web page it initiates at 1% for about 2 seconds and then releases the cpu. You must be doing something I'm not.

[Skuzzy]

It is the indexing/search service causing this.  I have always disabled it as it only helps improve searches and if you never use search it is a waste of CPU cycles.

However, I have heard if you disable the indexing service in Windows 10, it will no longer show your applications in the start menu.  There may be other things causing this, but you can try it and see.  Disable "Windows Search" in the "services.msc" utility.

You can always re-enable it if you need to.

[Drano]

The more I hear about Win10 the less chance I think it'll ever have being on any of my PCs. I'll stick with Win7/64 until they pry it from my cold dead hands.

Sent from my XT1080 using Tapatalk

[bustr]

New Microsoft OS business as usual teething pains.

Standard answer, pre sp1 people are bleeding edge masochists who Microsoft knows will alpha test for free.

[MADe]

New Microsoft OS business as usual teething pains.

Standard answer, pre sp1 people are bleeding edge masochists who Microsoft knows will alpha test for free.

yup!

[BoilerDown]

This is a lot worse than the teething pains of 2000, XP, or Windows 7 though, all of which I was in relatively early when it was clear those OS's didn't totally suck.  Windows 10 is another ME, Vista, or 8.  Barring DirectX 12 being an absolute necessity, I'll never update.  @#$% Microsoft and Windows 10.