Skip to content

Windows Index Search Parsed

Evidence: Windows Index Search Parsed
Description: Parse Windows Index Search Database
Category: System
Platform: windows
Short Name: indxsp
Is Parsed: Yes
Sent to Investigation Hub: Yes
Collect File(s): No

Windows Search records each indexed item in SystemIndex_Gthr and the folder tree in SystemIndex_GthrPth. Windows 10 and Windows Server 2019 and earlier keep both tables in the ESE database Windows.edb. Windows 11 and Windows Server 2022 keep them in the SQLite database Windows-gather.db.

Each item stores its name and the identifier of its folder. Walking that folder chain rebuilds the full path. The raw databases are collected separately by Windows Index Search.

FieldDescriptionExample
source_pathDatabase the row came fromC:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows-gather.db
document_idIndexed item identifier42
scope_idFolder identifier used to rebuild the path7
file_nameIndexed file or folder namenotepad.exe
full_pathPath rebuilt from the folder treeC:\Windows\System32\notepad.exe
last_modifiedLast modified time stored in the index (UTC)2025-07-01 06:10:54+00

Items stored with a file: scheme become Windows paths. Other schemes keep their URL form, such as a winrt:// entry for a packaged application.

The collector reads the gather tables from ProgramData\Microsoft\Search\Data\Applications\Windows on every drive:

  • Windows.edb is read in place through raw NTFS, so the locked database is not copied by this evidence.
  • Windows-gather.db and its -wal file are copied to a temporary directory and queried there.

If both databases exist, both are parsed. source_path shows which file a row came from. A machine upgraded to Windows 11 can still have Windows.edb, so both formats are read when present.

This evidence is included in the full and quick acquisition profiles. The raw database files are collected only by Windows Index Search, which is included in the full profile.

The rebuilt paths show which files the index knew about, including items whose originals are gone. Item properties beyond the path remain in the raw Windows.edb or Windows.db file.

  • If Windows-gather.db-wal cannot be copied, rows from the main database are still written, and the newest items in the WAL can be missing.
  • Only the gather tables are parsed. Item properties in Windows.db and in the Windows.edb property store are not parsed.
  • Windows.edb is read while Windows Search may still be writing to it, so the newest changes can be missing.
  • What appears in the index depends on the folders Windows Search was configured to index.