Getting the most from Windows Search — Part 2

Topic

New Reply

	WOODY’S WINDOWS[/size][/font] Getting the most from Windows Search — Part 2[/size]
	By Woody Leonhard In my Sept. 22 Woody’s Windows column, I stepped you through the basics of searching in Windows 7 — in particular, Win7’s two undocumented search idiosyncrasies that can cause no end of confusion. In Part 2, I give you the advanced course, including how to search in Win7 the way you used to in Windows XP, Windows 95, or (gulp!) even DOS.[/size]

---

The full text of this column is posted at WindowsSecrets.com/woodys-windows/getting-the-most-from-windows-search-part-2/ (opens in a new window/tab).

Columnists typically cannot reply to comments here, but do incorporate the best tips into future columns.[/td]

[/tr][/tbl]

Reply | Quote

Replies

This is all good stuff but for searching in Windows, there is simply no better program than ‘Find Everything’ – download it from http://www.voidtools.com/ – it’s free, it’s fast, and you don’t need to index your drive. This is on my top-5 essential software list Works with Win XP and Win 7 for sure, maybe others too.

Reply | Quote

This is all good stuff but for searching in Windows, there is simply no better program than ‘Find Everything’ – download it from http://www.voidtools.com/ – it’s free, it’s fast, and you don’t need to index your drive. This is on my top-5 essential software list Works with Win XP and Win 7 for sure, maybe others too.

I came to the forum to say exactly the same thing (except that the app is just called “Everything”). There’s also a portable version if you don’t want to install it. It’s one of the first apps I install on a new PC.

Reply | Quote

You all beat me to it. You must try Everything. It responds instantaneously as you type. What a valuable tool for file searching.

Reply | Quote

I can’t tell you how frustrated I was with the “new, improved” Windows 7 Search, particularly when I wanted to “find all of the files with Bob in the file name, but don’t look in Hidden Files”. I found some information on the Web (written by Microsoft, but still confusing and typically not what I needed). Never saw mention of system.filename:~=”secret”. I’d love to know where you found this, or how you figured this out …

Bob Schor

Reply | Quote

One problem I’ve recently had with Windows Search is that it will not index files located on a mount point. I’d created several Windows 2008 R2 file servers to replace our 2003 ones and I didn’t want to create one large volume with the OS and data. For a variety of reasons, I mounted the data partition as a mount point, but it just would not show up for indexing.

A web search confirmed the issue and offered a few workarounds, but all were very inefficient. I had to go back to using a drive letter for the data partition.

Reply | Quote

I can’t tell you how frustrated I was with the “new, improved” Windows 7 Search, particularly when I wanted to “find all of the files with Bob in the file name, but don’t look in Hidden Files”. I found some information on the Web (written by Microsoft, but still confusing and typically not what I needed). Never saw mention of system.filename:~=”secret”. I’d love to know where you found this, or how you figured this out …

Bob Schor

Bob –

I found the general keyword description that MS has posted, and then played with the details quite a while to figure out exactly what was happening. I don’t think this stuff is documented anywhere. Which is strange, because there used to be reams of documentation about searching in XP (and 98 and 3.1 and DOS) with wildcards…

Reply | Quote

Hello ;

I’m part of those who began with MS-DOS and UNIX, then tried almost all Windows versions, and finally… find Windows 7 hard to understand and to appropriate, especially when you have very few time…
I don’t say it’s not “user friendly”, but it’s clearly – for some things – not (as you say) old-fashioned-people friendly.
Especially about search function : with XP, I was used to either hit Win+F or right click the folder in which I wanted to search a file and then hit H to call the search interface, then I was able directly to look for a filename, optionnally specify some text to look for inside files, and even to specify “on the fly” where to search and a few other criterias such as date. Simple, easy, quickly done : efficient.
As I very rarely look for text inside files, I was used to even turn off the indexing service and, “of course”, I was not using Windows Search but the basic version – at work where it has been installed, it adds a step to my description here above : clicking on the message “use standard search” – because I compared the results : I find nothing interesting with Windows Search, whereas I easily gets to my files with the standard version.
And I’m sorry, but I can’t figure why Microsoft spent so much time to program a complex search system like Windows Search where the simple version does a much better job in most cases. Oh sorry, you’re right, I’m not alone in the world and some other people can find the new version better – but please Mr. Microsoft, give us the choice, give me back my old-fashioned basic search system… it would be much easier for me than, as I must do now with 7, opening a “cmd” prompt in the right folder and type “dir /S/A search_expression”…

One more word. I’m not against changes. The way you search today will be old-fashioned tomorrow and you’ll learn a new way to do it. But WHY would you really HAVE TO change when you’re pleased with today’s tools ?
The system should serve the user, not the editor’s ego or I_don’t_know_what…
Don’t you think so ?

Best regards,
Bertrand L.

Reply | Quote

Woody, and your other responders,
The info you have provided is helpful, and I thank you all for that. But why are you all, particularly you Woody as a professional journalist, not writing about what seems to me the main point? MS introduces new stuff all over the place – fine – but why is there no DIRECTLY accessible concise and accurate info about the change available?! This is sheer arrogance or sheer laziness, or both, on MS’s part. It would have been very simple to have added a “?” box in the search window – which could have at least directly pulled up the MS article you provided the link to (or better to the”basic search” MS article that the advanced one points to). However even this would have taken us only part way down the road, since the MS articles are neither complete nor accurate. For example the standard ‘old’ explanation of “?” and “*” is given – with not a word about the new meaning of these characters. Even your article does not cover searching on “?fred” (without the quotes). Is this restricted to searching file names, or contents, or ….. ?

Again – I see the news story here as ‘Once again MS has the arrogance to toss out a significant new feature with a clear ‘Let them figure it out for themselves.” attitude.

Reply | Quote

Woody, and your other responders,
The info you have provided is helpful, and I thank you all for that. But why are you all, particularly you Woody as a professional journalist, not writing about what seems to me the main point? MS introduces new stuff all over the place – fine – but why is there no DIRECTLY accessible concise and accurate info about the change available?! This is sheer arrogance or sheer laziness, or both, on MS’s part. It would have been very simple to have added a “?” box in the search window – which could have at least directly pulled up the MS article you provided the link to (or better to the”basic search” MS article that the advanced one points to). However even this would have taken us only part way down the road, since the MS articles are neither complete nor accurate. For example the standard ‘old’ explanation of “?” and “*” is given – with not a word about the new meaning of these characters. Even your article does not cover searching on “?fred” (without the quotes). Is this restricted to searching file names, or contents, or ….. ?

Again – I see the news story here as ‘Once again MS has the arrogance to toss out a significant new feature with a clear ‘Let them figure it out for themselves.” attitude.

In general I agree with the sentiment. For those few of us who actually try to find documentation it is almost laughable to see what is provided. Unfortunately, Microsoft is no different than any other software developer these days. No one explains new features any more. I’m sure that Microsoft can give you plenty of data about how “help” is not used. People just don’t take the time to read directions or explanations.

Joe

--Joe

Reply | Quote

How crude. Why does Microsoft even bother to add a “search” feature when it is so lame. With hundreds (maybe thousands) of programmers working on Windows, you would think getting “search” even half as good as the add-ons you can download would be a priority. This is like having a switch on your car dash that isn’t labelled and appears to do nothing. I have one of those too.

Reply | Quote

Woody —

Don’t bother trying to help explain this convoluted searching to us, if an interface is not natural and self exposing, it should die in future releases. Imagine Google’s chances for success with such an interface.

Reply | Quote

I also like to add Everything as an alternative to filename search with windows search. It gives amazingly instant replies and works with the old wildcards.
For text search in files I use Agent Ransack. It has al lot of options and works fast.
Its incredable that windows comes again with a bad solution and with other wildcards than usually.

Reply | Quote

Great post, but I have to say that the head-shaking started as soon as you began to explain the ridiculous syntax one has to use, and the cussing started when you mentioned that Search uses wildcards in a nonstandard (for DOS–>Windows) way. Petermat mentioned that you may have missed the main point and suggested that it was that Microsoft doesn’t advertise changes accessibly, but for me, the main point is that Windows Search does not work. By that, I don’t mean that it doesn’t function or doesn’t work in the way your much-needed documentation explains, but that it attempts to give the average user an interface that often returns unusable results. Over the years, and especially when helping someone on their own computer, I’ve had to use the various incarnations of Windows Search, and the times that it returned the file I was looking for is in the neighborhood of 20%. Now, I understand that this was probably due to my not using it correctly (or is it that Windows uses wildcards incorrectly?), yet that points back to the main issue: A search tool should default to returning files with or without a standard wildcard and with or without some key text that might appear in them. Period. Any advanced uses beyond that should be accessible with simple, clear visual controls and labels. And the idea that a general Windows search tool would automatically return the contents of emails is simply stupid. That’s what email software is for.

Finally, the main reason one actually resorts to searching for a file (as opposed to checking where you know it’s supposed to be) is that you’ve lost it somewhere on the drive (a victim of drag-and-drop or a download whose destination wasn’t what you assumed). When that happens, I use the search tool in my favorite two-pane file manager to do a brute force search of the entire drive. If that fails, I know that the file isn’t there and don’t have to worry that an over-engineered tool has second-guessed what I was trying to do.

Reply | Quote

Hi all,
Interesting reading, but I was wondering if anyone could tell me, in simple terms, how I can do a two tier search?
I often want to search all – say – “doc” files in a folder, not search the folders underneath, and look for a particular word in the .doc; all at the same time. Is someone able to tell me how I can do that in Windows 7? Thanks in advance!!

Reply | Quote

Klinkehoffen asked how to
>…search all “doc” files in a folder, not search the folders underneath, and look for a particular word in the .doc; all at the same time

Try this:
file:*.doc in:yourfoldername content:foo

You can abbreviate yourfoldername to any unique phrase e.g. in:yourf

“foo” is whatever search word you want to find.

You do not really need the “content:” keyword but it restricts that part of the search to looking inside the file
and ignores “foo” in filenames.

Note that the search word in the file must start a word, that is, it must be preceded by space or other punctuation.
But it can be followed by anything, e.g. content:foo would find fooxxx but not xxfoo.

To find either the word foo or bar inside of files use content:(foo OR bar)
Note that OR must be all-caps.

content:(foo bar) is the same as content:(foo AND bar) and requires that both words be in the file (they need not be adjacent).
Put it in quotes to find the exact phrase, e.g. content:”foo bar”

Go nuts:
content: (“foo bar” AND NOT Robert)

-Rob

Reply | Quote

Woody —

Don’t bother trying to help explain this convoluted searching to us, if an interface is not natural and self exposing, it should die in future releases. Imagine Google’s chances for success with such an interface.

Ah, but it doesn’t seem to hurt Facebook. :rolleyes:

Reply | Quote

The article said: “Note, however, you can add a folder to your PC’s index only if it’s located on the PC — you can’t add a networked folder….”

I’ve found that you can add networked folders under the following circumstances:
1) The folder/share is indexed on the server (I’m running 2008R2/SP1)
2) You add the network share to your Library (I’ve not tried indexing otherwise)
3) You add it with the actual \machinenameshare and NOT \dfsnameshare

I may have overlooked something on the DFS issue, but can live with the single server share name in my environment so I quit experimenting.

That said, I, too, have found the new ‘improved’ search to be less useful so will explore the suggested alternatives mentioned above.

Thanks!

Greg

Reply | Quote

The article suggests using: system.filename:~=”secrets” for a search to find secrets anywhere in a filename.

A shortcut for this is filename:*secrets
or simply file:*secrets

which is a lot easier to type and remember –
although you will need to use a question mark to match a space, eg file:*windows?secrets

The filter file:*.doc works pretty much as you would expect, except it also matches stuff like foo.docx.
You can use file:*.doc AND NOT file:*.docx to limit it more.

Sometimes you need the opposite – to find a word in the contents of files while ignoring the word in file names.
A search for content:secrets will search for the word secrets in the contents of files (ignoring if it is in the file name or not).

Note that any search term in a file (e.g. secrets) must begin a word, that is, it must be preceded by a space or other punctuation even if the search phrase has a *.

—

The article also had a small error…it states “As soon as Win7 sees the *, it doesn’t bother looking inside files. You could have the text *doc inside a Word document, and Windows won’t find it.” Opps, that’s not right. My test (with Win 7) does find *doc inside of a file. Try putting “docxxx” (or “*docxxx” ) in a word document and searching for *docxxx. The “docxxx” in the file must begin a word i.e. be preceded by a space or punctuation – but Windows will find it inside of a document and not just in a file name.

Keep up the great articles (and don’t fret the occasional glitch!).

-Rob

Reply | Quote

Rereading this thread, and seeing the glowing reviews for “Everything”, I looked at their website. I was very disappointed to find that Everything only looks for file and folder names, not content. I guess 70 – 80% of my searches are for content.Does anyone know of a product this good that does file / folder and / or content searches?

Reply | Quote

I was very disappointed to find that Everything only looks for file and folder names, not content … Does anyone know of a product this good that does file / folder and / or content searches?

I really like FileSearchEX

Reply | Quote