Search Files with Flow Launcher: Engine and Scope

Steps to follow

1. Choose a small local file you can already open in File Explorer. Note its exact name, extension, and directory.
2. Open Flow Settings, select Explorer, and inspect the index search engine. Determine whether the search goes to Windows Search or Everything.
3. Search for the known filename using the Explorer action keyword shown in your settings. Check that the file’s directory is included in the selected engine and not excluded in Flow.
4. Open the result context menu to inspect its path. Once the basic test succeeds, broaden the query or configure dedicated content-search keywords.

Limits and common pitfalls

A missing text-content match does not prove filename indexing is broken. Network shares, cloud-only files, and excluded locations may behave differently from a local indexed document.

Make the check repeatable

Use a filename test that cannot be confused with an app or bookmark. A distinctive local test document is more useful than a common word like settings. When reporting a failure, provide the search type, engine, sample filename, and directory category without exposing private document contents.

Questions and answers

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

• Project documentation: Explorer plugin
• Project documentation: usage tips

Related guides