New
#71
There's quite a few topics about this in the Windows Feedback app - I've upvoted the relevant ones. No idea if it'll make a difference.
There's quite a few topics about this in the Windows Feedback app - I've upvoted the relevant ones. No idea if it'll make a difference.
Eureka, I fixed it! (for now, at least? lol) Here's how:
step 1: create a new *local* user account, admin enabled (I named mine "Admin"). Make sure to use a password.
step 2: make sure your MS account is linked to your main user account (the one you're using that is search-broken)
step 3: convert your main user account to a standard (non-Admin) account.
step 3: log over to the new "Admin" account, let Windows set up the account. Change NOTHING.
step 4: reboot and/or relog into the main standard-user MS linked account.
for me, this appears to have fixed everything. Cortana has interests working, can search all my files and settings, and Windows Update appears to be functioning normally. The only catch here is that since your main user account is non-admin, you will be prompted by UAC to log in to the newly created "Admin" account to change settings or installations. I'm not 100% sure why this works, but something about Cortana doesn't like being attached to the active administrator account. Also worth noting that while my main MS user works great in this config, actually logging over to the Admin user account produces the unresponsive Cortana/taskbar bug that we're all familiar with. It seems she doesn't moonlight, she only wants to be attached to one user per PC and she'd prefer it be a local non-admin?
I have very similar experience, she is very picky.
I for one simply reinstalled windows a few times until I got an install whose search worked right away (took 4 absolutely clean installs...)
So I have only a single Admin MS account user, and Cortana is working currently, even after reindexing and pointing my user files around to other directories.
If you get search to work on an account, Never try to switch it back to local again, or it may break forever again. Once I turned a working search user to local, going back to MS didn't give me working search operations again.
Like chrisnyc75 explained, she only wants one account, and only the first MS account you ever use after Windows 10 installation.
Cortana is picky and very much monogamous it seems...
Today I noticed some updates were installed overnight. I no longer get the "we're getting search ready" message, however I still do not get any of the settings in my search results.
Just to add my two penneth..
...over the last week I have upgraded eight machines 32 bit, 64 bit, recent and ancient from Win 7 and Win 8, tablets, laptops and desktops. Only on the last two, yesterday and today did this problem show up for me. Both desktops, both in the same room, both 64 bit but one an old dell Inspiron 530 and the other a custom build Cube/Mesh machine. Yesterday I started rebuilding the index and the machine hung. I was forced to shut it down by pressing the power button. When I restarted it all was well. Today on the very last upgrade same problem BUT I decided to let the indexing proceed on its own. I switched users to add my wife's account picture. YES HER BLINKING SEARCH WAS WORKING FINE and switched back to my account to write this. SO IT IS NOT TRUE THAT ALL USERS WILL HAVE THE SAME SEARCH STATUS (ALTHOUGH I RECALL LAST WEEKEND WAS A BLUE MOON!). Now I have : Indexing is not running in the Indexing Options box.
Think I will try to get all available updates before doing anything else. Mentioning updates, I was pleased to note that my chipset and display drivers had updated automatically. Now I know some folk whose dual displays have been banjaxed are not pleased but speaking as someone who had to spend some while on an old machine reinstalling its proper driver rather than the Microsoft default, I am thrilled. IT SHOULD ALSO BE NOTED THAT MY ONLY DUAL DISPLAY IS WORKING FINE ALTHOUGH THAT IS FOLLOWING A DRIVER REINSTALLATION BY ME AND NOT AUTOMATICALLY.
Mike.
UPDATE: Search now works just a little later after 20,000 plus items indexed. I tried looking for updates earlier to resolve the issue but there was none available.
There is a troubleshooter for this here:
http://answers.microsoft.com/en-us/w...?page=1&auth=1