Windows 10: Windows search doesn't always work

True it hasn't been updated, but it's absolutely reliable and convenient- I use it across both drives and partitions. Sometimes I use Windows search when working with file explorer. And it does need to be allowed to index of course like the others.

I find Ultrasearch's GUI awkward to work with, and Everything was using more resource - a service I think- plus Everything required the use of a beta to add essential GUI features to specify the search.

Windows search on content can work well.. now where's that aardvark?



Instant- but what it doesn't indicate is that's on partition H. And to get fast content search requires all of H: to be indexed.

 

I am guessing adding huge HD's to the search index will slow it down considerably?

 

Creating the index initially would take longer, of course. That should be the only impact. Assuming changes thereafter would most commonly be smaller rather than larger, they would be re-indexed very quickly.

I've not experimented with very large volumes of content indexing (how fast something is found) with Windows search, but certainly when I used Copernic or Google Desktop search with larger volumes of information this was not an issue.

 

Sorry for the very late response, I had completely forgot about this thread. Windows says the indexing has been completed and about 1000 files has been indexed and it now seems to find my files and my programs! Will give it a few days and see if it sticks.

 

Hi,

I noticed I had a typo in my post. I apologize. Even when the indexer is still indexing, it would still say "# items indexed". So that means it could still be running. Refer to the picture to see how it would look like if the indexing is complete. Since yours says only 1000 files have been indexed, that means it's probably crashing and resetting. It should have indexed much more than 1000 files by now. So you should still "Rebuild" the index like I said. Then you should check on it hours later.

Even after "Rebuilding" the Index, it's possible that it could still be crashing & resetting. The Event Viewer will tell you on which file it crashes/resets on. I've had a similar issue like this before.

So first, Rebuild the Index, then check on it hours later.

 

I see, thats a bit confusing. I have set it to run and will let it run for the rest of the day.

 

Well it ran for most of the day yesterday, and didnt find anything besides the files that it already had found..

 

I would try rebuilding the index, like I stated earlier. It's not that hard; It's very easy.

 

Oh okay. I may have misunderstood earlier posts. Sorry bout that.

Ok, open Indexing Options and take a screen shot of it real quick. You don't mind me seeing what message it shows?
Open it > Press Alt + Print Screen > then on this page at the bottom, click in the Quick Reply box, and press CTRL + V

Then Post the message.

 

Suggest you post an example (path, file name) of
- what you're trying to find that isn't being found
- exactly how you're trying to search for it
- further info as necessary if you're doing a content search.

Given the above screenshot showing indexed locations and the path, that will help determine if you have it in an indexed location (key for Cortana search).

If you are using file explorer to search, you need to ensure explorer is open at a point in the file hierarchy above the item you are searching for.

 

Yes, take a screen shot of it just like in my example above. It will help us figure out more about the possible problem *Smile

 

It shows exactly the same as in your screengrab, except it only finds about 1000 files.

 

I'm marking this as solved since we found a solution.