Created a new Windows 8 VM. Indeed this problem doesn't occur on a completely fresh install of Windows 8. I tried to recreate all configuration steps that I had taken before, still works properly. So either ViStart messed something up or I accidentally changed some weird settings. I guess this isn't a major issue then, although it would be interesting to know what caused this behavior.
I am using Windows 8 RTM downloaded from DreamSpark. It's a VM, but I doubt it matters. Start8 is the only application currently installed. Before that I tried ViStart, but didn't like it and uninstalled it, not sure if it's possible that it messed up some search settings. I'll try installing W8 again and see if I have the same problem. Thank you.
No I hadn't. I only know how to change the places it indexes. I have no idea if it is even possible to change the locations it generally searches in, but doesn't necessarily index. If it's possible, I suppose I could fix my problem by making those two lists match.
Never mind, it seems that it searched for files before searching control panel stuff. But since I tested it when some directories weren't indexed, it got stuck on file search. Now it seems to show control panel sections just fine. Version is 0.98 BETA 3, although I guess doesn't matter anymore. So, is it possible to make it only search indexed locations in future versions? I'm pretty sure telling everyone to add all drives to index and then also add the directories that we
Hello, I'm having the same problem. Whenever I try to search something from the start menu, explorer's CPU usage goes near 100% and stays there for a while (probably searching through the hard drive). When I found this thread, I checked my Windows Search settings. Windows Search is enabled and is indexing a small bunch of folders. I thought it was probably continuing its search in non-indexed locations, so I added the whole C drive (no other drives in use) to the index and wai