New
#131
All of mine were already correctly English United Kingdom :/
It's so frustrating, I wish I could get any kind of response from MS about my problem with the Indexer not even adding the correct drive when selected, the feedback tool is so one sided.
Thank you pakjebakmeel.
This was the solution for me:
1. Open and elevated CMD window (rightclick --> run as admin)
2. Start powershell (type 'powershell' without quotes and press enter)
3. Run the command:
Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
I did not need to delete the folder first. It worked instantly. After more than a week of the annoying "We're getting search ready" error, and no search hits on already installed apps - I finally got everything working.
Thank You!
Fixed my crazy problem, finally able to free up enough space to back up my 250gb SSD and delete the partition, format, then make a new partition.
Finally after doing that the Indexer Options UI adds drives correctly when selected.
I still think it's crazy that the indexer seemed to be the only thing that was effected by whatever was wrong with the partition data though.
The volumes had unique GUIDS, all the info I could find with diskpart indicated they should have always been treated as distinctly different partitions without confusion.
Anyway, because of this, my "We're getting search ready" problem is now solved :)
Last edited by Yakumo; 27 Aug 2015 at 15:35.
I think we're getting there! I've managed to quash my "We're getting search ready" problem as well. However it can't find any of the files I've indexed on Dropbox on a different drive location. This is really annoying because my C: (SSD for windows) only contains programs, whereas my E (HDD for dropbox) contains all the stuff I wanna search for.
It's added to the index options and I've rebuilt it umpteen times! Stuff on the C: it indexes, stuff on the E: never appears in the results.
This didn't fix the problem for me, but it helped me reproduce the problem. I've tried everything in this thread and nothing worked.
Once you add a second language and press "Set as primary", this bug occurs.
As a workaround, I had to completely reset my Windows, deleting all files, and avoid clicking "Set as primary".