Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 7 explorer search when indexed and non indexed folders present 1

Status
Not open for further replies.

stduc

Programmer
Nov 26, 2002
1,903
GB
Unlike some. I quite like the way Windows 7 searches. However although I have no problems searching either a completely non indexed location, or an indexed location, I find that if I search an entire drive that contains a mixture, only those folders that are indexed are searched. Does anyone have a better answer that resorting to using a command shell and using the command dir/s <filename> ?

In addition of non-indexed a command line search is much faster than using windows explorer! Any comments?

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
Are you saying that after the initial search of Indexed locations failing to find a file, if you use the "Search again in" "Computer" option it misses finding files in Indexed or non indexed, including hidden and system files?

I have never felt 100% sure that the results produced by Windows searching were "gospel" and usually get a second opinion.

SearchMyFiles v1.55

Running Agent Ransack via the "Run As Administrator" option is another search method I use too.

Agent Ransack - Free File Searching Utility
 
I don't want to use a third party tool unless I really have to.

What I am saying is if I look for a file, using the search box in explorer (top right of window) starting in "documents", it will find the file quickly, if it is there. But if the file is in say the system32 folder but I start the search from the root of C it will not find it! It will find it though if I start the search in the windows folder. I am assuming that this is because the windows folder is not indexed. I don't want to index it because I rarely search it! What I want is the search to not stop when it runs out of index. If you see what I mean?

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
You have Search options that can be set in Folder Options/ Search, there is not a lot of maneuvering to be had in there but it is there nevertheless.
 
I already set the Folder Options/Search to "In indexed locations...."

I think it's a bug/oversight on Microsoft's part. I could include all of drive C in the indexes (i.e the windows folder but probably not the program data folder) but Microsoft advice against it. Do you think I should?

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
Perhaps it is only a time restraint that would be the reason for not indexing the whole drive, that being the time required to complete the indexing, and then the extra bit of time taken to perform subsequent searches.

All I can say is that with the third parity applications I have at my disposal is that searching multiple drives with multiple partitions is extremely fast. I only use Windows Search for my user and data files, these are fully indexed.

By way of a test based on your observations I searched for a known file in the System32 folder (atl.dll) from the Search box of my C: drive and Windows found that and several other similar named files throughout the drive. It didn't take too long, and it was not an indexed search.

Perhaps the speed of the machine, the amount of background processes, all have to be taken into consideration?
 
Curious. A search from c:\ for atl.dll found several but none in system 32. A search from C:\Windows\System32 found atl.dll and atl.dll.mui with the non indexed may be slow message. A search for atl.dll.mui from C:\ however found nothing.

If you report back that a windows search from C:\ finds atl.dll.mui in system32 then I will have to conclude the problem is peculiar to me. Maybe I need to rebuild the indexes or something?

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
It did find 4 entries for atl.dll.mui a couple in Winsxs a one each in System32 and Syswow64.

Are you showing Hidden and System files in Folder Options, and perhaps even unchecking, "Hide known file types"?

Like I said first up, I don't really trust Windows Search.
 
I know what you mean. Makes you wonder what Microsoft are playing at sometimes. I mean, how hard can it be?

I do have "show hidden files, folders and drives" selected as well as as all "hide" options unselected.

I believe I have found the solution. I needed to tick "Don't use the index when searching in file folders for system files" In addition to selecting "In indexed locations search file names and contents. In non-indexed locations, search file names only." In the search options.

Now if I search C for atl.dll.mui I get 4 files. Same as if I use the cmd shell. But the windows search is noticeably slower than a command shell search.

However, here's the kicker, that option seriously slows down searches in indexed files! Microsoft, don't you just love em!

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
I switched over to using Locate32 a while back.
Seems to be faster and more complete then the native one in Windows.


And it adds the search command to you right click drop-down.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top