Windows Search Index Locations Registry Path
This article explains the exact Windows Registry locations used by the Windows Search service to define and manage indexed file paths, included directories, and supported file extensions. By navigating these specific registry hives in Regedit, administrators can inspect or configure the inclusion parameters governing the search indexer.
1. Indexed Inclusion Roots (Crawl Scope)
The primary parameters defining which root folders and locations are included in the search index are managed by the Crawl Scope Manager. You can find these settings at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\CrawlScopeManager\Projects\SystemIndex\SearchRoots
Inside the SearchRoots key, individual numbered subkeys
(e.g., 0, 1, 2) represent each
root URL included or tracked by the indexer (such as
file:///C:\Users or
file:///C:\ProgramData\Microsoft\Windows\Start Menu).
Key values within each entry include: *
URL: The path target (e.g.,
file:///C:) defining the indexing boundary. *
Included: A DWORD value where
1 indicates the location is included in the indexing scope
and 0 indicates an exclusion. *
FollowDirectories: A DWORD indicating
whether the indexer should traverse child directories.
2. Path Traversal and Rule Sets
To see how individual paths and granular inclusion/exclusion rules are structured internally by the indexing engine, check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gather\Windows\SystemIndex\Sites\LocalHost\Paths
This key contains the internal path hierarchy that the gatherer uses when determining whether specific folders inside an included root should be processed or skipped.
3. File Type and Extension Inclusions
In addition to folder paths, the Windows Search indexer stores the list of included file extensions and their parsing filters (IFilters) at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gather\Windows\SystemIndex\Extensions\ExtensionList
Each file extension (such as .txt, .docx,
.pdf) has a subkey that dictates: * Whether the file type
is indexed. * Whether only file properties are indexed or both
properties and file contents are indexed (controlled by the persistent
handler and filter settings assigned to the extension).
Applying Changes
Direct modifications made in the Registry will not take effect immediately while the search service is running. To apply manual registry updates:
- Open Services (
services.msc) or use an elevated Command Prompt. - Stop the Windows Search service
(
net stop wsearch). - Apply the registry changes.
- Restart the service (
net start wsearch). - Rebuild the index via the Indexing Options control panel if deep path structure changes were made.