{"id":5894,"date":"2017-11-01T14:21:39","date_gmt":"2017-11-01T08:51:39","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=5894"},"modified":"2023-07-31T17:57:38","modified_gmt":"2023-07-31T12:27:38","slug":"search-contents-of-any-file-windows-search-indexing","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/search-contents-of-any-file-windows-search-indexing\/","title":{"rendered":"How to Search the Contents of Any File Type Using Windows Search"},"content":{"rendered":"

Windows Search and its Advanced Query Syntax (AQS) is a freaking awesome feature in Windows. It lets you quickly find a particular file or group of files with a specific name or metadata, in a folder and sub-folders.<\/p>\n

Along with indexing file properties or metadata, most known plain-text files are also content indexed by default. When a file type is content indexed, Windows Search lists out the files that contain the word or phrase in the file contents when you type a search phrase in the Search box.<\/p>\n

RELATED:<\/strong> What is Enhanced Search (Indexing Options) in Windows 10<\/a><\/div>\n

Which Plain-Text Files are “Content Indexed” by Default?<\/h3>\n

By default, known plain-text file types such as .BAT<\/code>, .CMD<\/code>, .CPP<\/code>, .VBS<\/code>. Here is the full list of file types that are, by default, content indexed on a Windows 10 computer:<\/p>\n

A, ANS, ASC, ASM, ASX, AU3, BAS, BAT, BCP, C, CC, CLS, CMD, CPP, CS, CSA, CSV, CXX, DBS, DEF, DIC, DOS, DSP, DSW, EXT, FAQ, FKY, H, HPP, HXX, I, IBQ, ICS, IDL, IDQ, INC, INF, INI, INL, INX, JAV, JAVA, JS, KCI, LGN, LST, M3U, MAK, MK, ODH, ODL, PL, PRC, RC2, RC, RCT, REG, RGS, RUL, S, SCC, SOL, SQL, TAB, TDL, TLH, TLI, TRG, TXT, UDF, UDT, USR, VBS, VIW, VSPSCC, VSSCC, VSSSCC, WRI, WTX<\/pre>\n
Enable Searching File Contents of Any File Type<\/h3>\n
If you have a custom file type that is of plain-text format, and want to fully index (except the stop words) the contents, you can add the file extension manually in indexing options. Type Indexing Options<\/strong> in the Start\/Cortana search box and click on the search result.<\/p>\n
\"indexing<\/p>\n
To add custom or unknown plain-text files like, .AHK<\/code> or .PHP<\/code>, in the Indexing Options dialog, click Advanced, and click File Types.<\/p>\n
\"php<\/p>\n
Type the file extension PHP<\/code>, select Index Properties and File Contents<\/strong> radio-button, and click OK. After you press OK, the prompt “Rebuilding the index might take a long time to complete. Some views and search results might be incomplete until rebuilding is finished.<\/em><\/strong>” appears.<\/p>\n
\"rebuild<\/p>\n
Click OK, and give the indexer considerable time (maybe even hours) to do its job.<\/p>\n
\n
Example:\u00a0Enable Searching File Contents of PowerShell Scripts (.PS1)<\/h4>\n
PowerShell script file type .PS1<\/code>, although it’s a known plain-text file, is not content indexed by default. To demonstrate this, I have two files with different file extensions, but containing exactly the same PowerShell code.<\/p>\n
\"windows<\/p>\n
As you can see, the file contains a word named Defender<\/code>.<\/p>\n
\"ps1<\/p>\n
However, when I typed defender<\/code> in the Search text box, it listed only the text (.txt<\/code>) file. Although the .PS1<\/code> file has got the same contents, the file wasn’t listed in the search results.<\/p>\n
\".ps1<\/p>\n
To search file contents of .PS1<\/code> using Windows Search, enable content indexing for the file extension. In Indexing Options, click Advanced, and select the File Types tab. Select .PS1<\/code> from the list and enable Index Properties and File Contents<\/strong> radio-button.<\/p>\n
\"ps1<\/p>\n
Click OK, and give ample<\/strong> time for Windows Search to index the chosen file type. Rebuilding<\/a> may take anywhere from minutes to hours depending upon the system configuration, number of files waiting to be indexed, and the user activity level in the system. Don’t expect Windows to content index your additional file types immediately.<\/p>\n
After some time, Windows Search indexed the contents of all .PS1<\/code> files duly, and here are the search results:<\/p>\n
\".ps1<\/p>\n<\/div>\n
RELATED:<\/strong> How to Search for Files Created Between Two Dates in Windows<\/a><\/div>\n
Exclude Files in Specific Folders to Prevent the Contents Indexed<\/h3>\n
Content indexing additional file types mean additional database file size<\/a> and additional resources consumed by the Search Indexer. To keep the database size down, enable the option only for the files you need. For the rest of the file types, you can choose to index only the file properties and metadata.<\/p>\n
Besides configuring content indexing on a per-file type basis, you can exclude certain folders (or files) as well. Right-click on a file or folder, click Properties, and click Advanced.<\/p>\n
\"disable<\/p>\n
Note:<\/strong> You can do this on a per-file or per-folder basis.<\/em><\/p>\n
Uncheck Allow files in this folder to have contents indexed in addition to file properties<\/strong>, and click OK. For folders, Windows asks you whether to apply the settings for files from the current folder only, or for sub-folders as well. Choose the appropriate option and click OK.<\/p>\n
From now on, Windows Search will not index the contents of the files present in that particular folder<\/strong>, regardless of your per-file type setting in the File Types dialog in Indexing Options. This helps lower the burden of Windows Search, and keeps the database size smaller.<\/p>\n
\n
Search file names only, not contents (even with content indexing enabled)<\/h3>\n
Sometimes, you may want to prevent Windows search from indexing the contents of documents and archives (without turning off the file content indexing feature), restricting the results to filenames only.<\/p>\n
To make Windows Search search only for the file name (not contents), use the search operator filename:<\/code><\/p>\n
For example, the advanced search query filename:*audit*<\/code> lists out files that contain the word audit<\/code> in the file name, regardless of file contents. For accurate searches, always use advanced search operators.<\/p>\n
\n
Refine your searches using Search tab Ribbon commands<\/h4>\n
Don’t like manually typing or memorizing the advanced query syntax? No problem! use the advanced search ribbon buttons in File Explorer Search tab to refine your searches. It fills up the search operators automatically in the search text box.<\/p>\n
\"AQS<\/p>\n
\n
For demonstration, I added a 0-byte file named defender.txt<\/strong> along with sample.txt<\/strong> and sample.ps1<\/strong>.<\/p>\n
\"AQS<\/p>\n
The files sample.txt and sample.ps1 contain the word defender<\/strong> inside the file. In this case, typing defender<\/strong> in the search box lists all three files:<\/p>\n
\"AQS<\/p>\n
That’s because, for freestyle keyword searches, Windows Search looks for the filename, as well as searches the contents (of included file types) for the keyword used. If I used the Advanced Query Syntax (AQS) syntax filename:<\/code> or name:<\/code> it searches for the file name only<\/strong>, as seen in the following screenshot.<\/p>\n
\"AQS<\/p>\n
\"tipsThe filename:<\/code> operator is always preferred to name:<\/code> because the name:<\/code> operator will only search from the beginning of the file name, as opposed to anywhere in the file name.<\/p>\n
Similarly, there are many such advanced search operators<\/a> that you’d like to be familiar with. For example, using the AQS, you can search for Files created between two dates<\/a>. You can mix and match multiple search operators to refine your searches. With Windows Search’s AQS, the opportunities are endless.<\/p>\n<\/div>\n
Search file contents even in non-indexed locations<\/h3>\n
Thus far, everything written in this article applies to indexed locations. For non-indexed paths, Windows has to scour through each file or folder in the file system and fetch the results. This will be accurate, but very slow and drains the system resources more.<\/p>\n
By default, in non-indexed locations, Windows Search doesn’t search file contents. If you wish to search file contents in non-indexed locations, there is a setting you can enable.<\/p>\n