Andrew8647

It was not enough for me. I had to also index all folders on C except for windows folder to make it run decently. It was working even better with whole drive indexed. Start10 keeps searching in "documents" and "files and folders" whatever it means like it was completely ignoring my setting to only search in start menu. It also adds start10ctrlpnl to indexed locations which probably means it indexes control panel. Maybe it is my language fault and button is not working as it should.</p

Rebuilding index did not help. But I found solution: check if C drive has "allow indexing on this drive" enabled. I enabled it - index has grown from 300 to 120 000 entries and now searching is fast and fine - cpu load drops fast. However start 10 is searching in some strange folders but I have "search in different locations" (or something like that) disabled in start10 options. Update - I rebuilt index after this. Now it has only 20 000 entries (searches only in documents and start m

15.00 Normal 0 21 false

It did not help at all. I gues I'll have to wait until my manufacturer releases 1903 for me. I do not want to force install it. Lastest windows update must have ruined it. It is not stardock fault. It is microsoft fault. I tried rebuilding windows index and disabling windows search but it did nothing. Troubleshooter says there are some problems with windows search catalog privileges.

I boot my PC. CPU load is minimum (~5%). I open start10 and enter any search - explorer.exe starts consuming 25% of cpu. If I close search and go back to desktop and then input something into search bar - another 25% is added to CPU usage. If I do this 4 times, my cpu usage is 100%. If I use ctrl+windows key to open standard Microsoft start menu and search using this - explorer.exe is fine. It jumps for a second and then it is quiet. Only remedy for start10 cpu usage is to wai