18
11
Since upgrading to Windows 8.1 this weekend, the Search feature became pretty useless. When I start typing, it sends my CPU usage to 100% (Task Manager shows Windows Explorer as the main offender), and results are pretty slow. The funny thing is, I have a i7 with 8 logical cores, and this is one of the rare times a single program actually manages to utilize all of them at once. :)
Some searches which worked earlier (e.g. typing "devices" would bring out a "Devices and printers" link for the Control Panel) also aren't shown anymore if "Everything" is selected for searching. If I select "Settings" in the drop-down, then the "Devices and settings" link is shown, but it takes around 3s for the results to show up making the whole thing useless.
I tried disabling the Windows Search service completely (although it's not the one peaking the CPU), but it didn't help. Also disabled Bing web search integration in PC settings, but it didn't change anything (apart from the web results now being omitted from the slow search).
I have found a couple of similar threads online, but they don't offer any solutions:
- Windows 8.1 explorer.exe sends CPU to 100% when searching in Metro interface
- Windows 8.1 preview search charm loads 100% CPU
- Windows 8.1 search causes explorer.exe to spike to 100%
Does anyone have a similar problem, and possibly a solution to this problem?
Since I've accustomed to hitting the Windows button and typing immediately to start my apps, I am considering two obvious solutions:
- Reinstall plain old Windows 8 again
- Install a third-pary Start menu app with a working search functionality
This is a Windows 8.1 bug, no fix released yet, but you can try to rebuilt the search index. >> http://www.neowin.net/forum/topic/1182675-windows-81-search-causes-explorerexe-to-spike-to-100-cpu/ & https://social.technet.microsoft.com/Forums/windows/en-US/2a12dfac-b9be-4880-97ed-5b4ef9056360/search-charm-loads-100-cpu
– Rudolph – 2013-10-29T10:45:47.7771@Rudolph: thanks. Rebuilding the Search index didn't help, and disabling it didn't help either. I also ran Process Monitor to see what was happening: it turns out that Explorer.exe is iterating through all folders on all of my disks when the search starts, and doesn't stop iterating even after I've already selected a result from the list (it just keeps going until it checks every single folder). Btw, your links are already included in my question. :) – Groo – 2013-10-29T10:55:09.710
I find it weird that more people aren't experiencing this. Does anyone have an idea why this problem is caused? (Ie, why is a necessary folder not in the indexing path by default?) – flindeberg – 2013-11-07T16:26:11.357