Everything File List Results Not Searchable: How to Fix It

When Everything file list results are not searchable, the problem is usually not Windows Search and may not involve Everything’s live index at all. The most common causes are an EFU file list that was opened or indexed differently than expected, an active filter hiding records, incorrect use of the filelist: or filelistfilename: search functions, a stale static file list, or a path that is no longer available when you try to open a result. Permissions, portable settings, startup arguments, and network access can also matter, but only in particular situations. The safest approach is to identify whether you are searching Everything’s live index or a static file list, reproduce the symptom with a small test, and change one relevant setting at a time.

1. Confirm the Symptom With a Small Safe Test

Start by separating a search problem from an opening problem. Everything may display a record from a file list even when the original file is offline. In that case, the record is searchable, but double-clicking it fails because its path is unavailable. Conversely, the file may exist and be accessible in File Explorer while Everything hides its file-list record because a filter or search expression excludes it.

1.1 Create a known test file

Create a harmless test folder in a location you control, such as C:\Everything-Test. Inside it, create a file with a distinctive name such as efu-search-test-4821.txt. If your issue concerns a NAS or mapped drive, begin with a local test so network variables do not obscure the result.

Search Everything for the exact filename. If the file appears immediately, the live index is working for that location. If it does not appear, remove all text from the search box, select the Everything filter, and check whether the folder is part of an enabled NTFS, ReFS, or folder index. Do not rebuild anything yet.

1.2 Create or update a small EFU file list

Create an EFU file list containing the test folder by using Everything’s file-list creation feature. Save it under a unique name such as small-test-list.efu. An EFU file is a static catalog of names, paths, sizes, dates, and other recorded properties. It is not a live connection to the files it describes.

Add or open that list using the same workflow that produces the original problem. Clear the search box and active filters, then search for efu-search-test-4821.txt. Success means the record appears in the main results and, if the original path remains accessible, opens normally. Once this works, stop changing general index or service settings. The original EFU file or the way it is selected is the likely cause.

1.3 Identify which failure you actually have

• No record appears: Check file-list selection, filters, exclusions, syntax, and whether the EFU was loaded or indexed.
• The record appears but will not open: Check path availability, credentials, mapped drives, and the account running Everything.
• The record contains old information: Regenerate or replace the EFU file.
• Live files appear but file-list records do not: Concentrate on file-list configuration rather than the NTFS index or Everything service.
• Neither live nor file-list records appear: Clear the search state and inspect the active instance, index settings, and startup configuration.

2. Understand Live Indexes and Static File Lists

Everything’s normal filename search is built from its live indexes. On supported local file systems, Everything can maintain those indexes through file-system metadata and change journals. Folder indexes can also cover locations such as network shares, although their update behavior differs from a local NTFS index.

An EFU file list is different. It is a saved snapshot. Loading or indexing an EFU does not make the original location live, and changes on disk do not automatically rewrite the saved catalog. This distinction explains many cases where Everything results are missing or outdated.

2.1 Check whether the file list is available to the main search

Opening an EFU in a file-list editor or viewing its contents is not necessarily the same as adding that list to the set searched by Everything’s main results window. Review the File Lists area under Everything’s index options and confirm that the intended EFU is included and enabled in the current Everything instance.

Also verify the EFU filename and location. A portable installation may use a different configuration from an installed copy, while a named or separately launched instance can maintain its own index settings. If the list is present and a unique record from it appears in the main results, this check has succeeded. Do not alter the service or live NTFS indexes after that point.

2.2 Search within one selected file list

If several file lists are indexed, use Everything’s file-list search functions to narrow the results. The filelistfilename: function filters results by the filename of the source file list. This is useful when you want records from one EFU rather than all indexed lists.

For example, begin typing the function through Everything’s Search Help or function completion and supply the exact EFU filename. Quote names that contain spaces. Then add the filename term you want to find. If the expected result appears only after applying filelistfilename:, the list is searchable and the earlier issue was selection or scope, not corruption.

The filelist: function has a different purpose: it searches using filenames supplied by a file list. It is not interchangeable with filelistfilename:, which identifies the source list associated with indexed file-list results. Use Everything’s built-in Search Help to confirm argument formatting for your installed build, especially when paths contain spaces or punctuation.

2.3 Clear active filters and result omissions

Select the Everything filter before testing. An Audio, Video, Document, Folder, or custom filter can silently exclude valid EFU entries. Custom filters may also add macros or search expressions that remain effective even when the visible query looks simple.

Clear the search box completely and inspect the Search menu. Turn off Match Case, Match Whole Word, Match Path, regular expressions, or diacritic matching unless your test requires them. Also inspect options for excluded files, excluded folders, hidden files, system files, and result omissions. An exclusion that matches the original path can prevent records from appearing even when the EFU itself loads correctly.

Success means the distinctive test record appears with an empty or simple filename search under the Everything filter. Re-enable optional matching modes individually and stop as soon as the setting that hides the result is identified.

3. Update Stale EFU Files Without Damaging Working Indexes

A static EFU file does not continuously monitor its source. If a NAS folder, removable drive, archive, or offline volume changed after the EFU was created, the list remains stale until it is recreated or replaced. Restarting Everything or rebuilding a live NTFS index does not update the contents recorded inside the EFU.

3.1 Verify the EFU timestamp and contents

Check the EFU file’s modification date in File Explorer. If appropriate, open it through Everything’s file-list tools and look for a recently created filename. If the new file is absent from the catalog, searching cannot find it.

Generate a fresh file list from the source while the source is available, save it under a temporary new name, and add that new list to Everything. Keep the old list until the replacement is verified. Success means the recent filename appears when the new EFU is selected. You can then retire the older list without touching unrelated indexes.

3.2 Distinguish stale metadata from unavailable paths

An EFU may correctly contain Z:\Projects\Report.docx even when drive Z is currently disconnected. Everything can search the stored text, but Windows cannot open the target until that path resolves. Similarly, a UNC path recorded under one server name may fail after a NAS migration.

Right-click a result and inspect its full path. Paste that path into File Explorer or the Run dialog. If Windows cannot reach it, restore the mapping, connect to the correct network, authenticate to the share, or update the EFU from the new path. The Everything database and file list are not the cause when Windows itself cannot resolve the recorded location.

4. Check Windows, Network, and Account Context

Windows permissions become relevant when Everything must scan a folder to build a list, update a folder index, or open a result. They do not normally prevent a previously recorded EFU row from being matched as text. This is why permission troubleshooting should follow the small file-list search test rather than precede it.

4.1 Mapped drives and network shares

Mapped drive letters belong to a user session. A drive visible in your interactive desktop may not be visible to an application running under another account or in a different elevation context. If possible, test the corresponding UNC path, such as \\server\share\folder, instead of relying only on a drive letter.

If the EFU contains a mapped drive path, keep in mind that changing Everything’s folder index to a UNC path will not rewrite the old EFU records. Regenerate the EFU using the preferred path format if you need opening and path-based searches to remain consistent.

4.2 Service state versus file-list searching

The Everything service helps the desktop application perform low-level indexing without requiring the user interface to run with elevated privileges. A stopped or misconfigured service can affect live indexing, but it is not the first suspect when only static file-list searches fail.

Check the service when local live results are also missing, the status bar reports an indexing problem, or the application says it cannot access a volume. Confirm that the desktop client and service belong to the intended installation and instance. If static EFU records remain searchable, stop changing service settings and return to path access or file-list freshness.

4.3 Firewall, antivirus, and Everything servers

A firewall matters if the client is querying an Everything server, connecting to a remote service, or reaching a network share. It does not normally block local matching against an already loaded EFU. Confirm the server address, port, authentication, and network route, and restrict access to trusted networks. Do not expose an Everything search server directly to the public internet without a properly secured architecture.

Security software may quarantine an executable, block access to a folder, or prevent an EFU from being rewritten. Review protection history and logs rather than disabling protection permanently. If necessary, test with a small file in an approved local folder or create a narrowly scoped exception according to your organization’s policy.

4.4 Portable installations and startup behavior

A portable copy may store settings beside its executable, while an installed copy may use another configuration location. Opening the wrong executable can make file-list indexes appear to have vanished. Compare the application path, instance name, status bar, and File Lists options in the window you are actually using.

Inspect shortcuts, scheduled tasks, scripts, and command lines that launch Everything. Arguments can select a different instance or configuration, load a specific search, or otherwise change startup behavior. Test by launching the intended executable directly with no optional arguments. If the file list works, restore arguments one at a time until the conflicting option is found.

5. Use Everything’s Diagnostic Tools Carefully

Diagnostics are most useful after you have identified whether the failure concerns the live index, a folder index, or a static EFU. Avoid using Force Rebuild as the first response because it can consume time without changing a stale file list or inaccessible path.

5.1 Read the status bar and Options pages

The status bar can reveal whether Everything is indexing, sorting, or showing a limited number of results. Check the total result count after clearing the search. A nonzero count with no expected EFU records suggests scope, filters, or exclusions. An unexpectedly empty database suggests that you are using another instance or that indexing has not completed.

Review the relevant Options pages for NTFS or ReFS volumes, folder indexes, file lists, and exclusions. Do not enable every available index. Confirm only the source required for the test and wait for any active scan to finish before judging the result.

5.2 Use Force Rebuild only for the correct index

Force Rebuild can help when Everything’s live index is demonstrably inconsistent with the selected volumes or folder indexes. Before using it, verify the indexed locations, exclusions, service state, and account access. Preserve your settings and allow the rebuild to finish.

A rebuild is not a substitute for regenerating a stale EFU. If the missing filename does not exist inside the file-list snapshot, no rebuild of the live database can invent that record. Replace or recreate the EFU instead.

5.3 Test search syntax in small steps

Begin with the exact distinctive filename. Next, test a unique partial name. Then add path matching, filelistfilename:, or filelist: separately. Quoting paths with spaces helps prevent terms from being interpreted independently.

If a simple filename works but the full expression does not, the index is functioning. The failure lies in the added function, filter, quoting, or Boolean logic. Remove terms from right to left until results return, then correct only the first term that causes them to disappear.

5.4 Review debug output and the Index Journal

Debug logging can show what Everything is doing while it loads an index, scans a folder, or processes startup settings. Enable it only long enough to reproduce the problem, and review logs for failed paths, inaccessible files, unexpected instances, or repeated reloads. Logs can contain filenames and paths, so sanitize them before sharing.

The Index Journal is useful for understanding changes to Everything’s maintained indexes. It does not transform an EFU snapshot into a live source. If the journal shows live changes but the selected EFU remains old, regenerate the file list.

6. Run a Clean Temporary Test Before Changing Many Settings

If the cause remains unclear, use a separate temporary configuration or portable copy in a test folder. Preserve your existing installation and settings. Avoid running competing services or allowing two copies to modify the same configuration files.

1. Exit the normal Everything user interface after noting its executable path and instance.
2. Back up the relevant configuration files and the original EFU.
3. Start an isolated portable or temporary instance with a clean profile.
4. Add only the small test EFU created earlier.
5. Select the Everything filter and search the distinctive test filename.
6. Add the original EFU and repeat the search.
7. Introduce custom filters, exclusions, startup arguments, and network paths one at a time.

If the small EFU works in the clean profile, Everything’s basic file-list search is operational. If the original EFU fails there, inspect or regenerate that list. If both work, the normal profile contains the conflicting filter, exclusion, instance choice, or startup setting. Stop testing once one added setting reproduces the failure.

7. Quick Fix Checklist

• Clear the search box and select the Everything filter.
• Turn off Match Path, regex, whole-word, and case matching for the first test.
• Confirm the EFU is included in the current instance’s File Lists settings.
• Use filelistfilename: to restrict results to the intended EFU source.
• Use filelist: only for its intended filename-list matching purpose.
• Check exclusions and custom filters for the original folder or filename.
• Verify that the desired record actually exists inside the EFU.
• Regenerate a stale EFU instead of rebuilding unrelated live indexes.
• Test the result’s full path directly in File Explorer.
• Use UNC paths when mapped-drive visibility differs by account or elevation.
• Confirm that you opened the correct installed, portable, or named instance.
• Inspect shortcut and script arguments for unexpected startup behavior.
• Check the service only when live indexing is also affected.
• Use a clean temporary profile before making broad configuration changes.

8. Frequently Asked Questions

8.1 Why can Everything display an EFU result but not open it?

The EFU stores a path as catalog data. Everything can match that stored path even if the drive, share, or original file is unavailable. Test the full path in File Explorer. Reconnect the drive, authenticate to the share, or regenerate the EFU with the current path.

8.2 Does Force Rebuild update an EFU file?

No. Treat an EFU as a static snapshot. If its source has changed, create a new file list or update it through the appropriate file-list workflow. Force Rebuild is for Everything’s maintained indexes and should be used only after safer checks establish that those indexes are inconsistent.

8.3 What is the difference between filelist and filelistfilename?

filelist: searches from names supplied by a file list, while filelistfilename: filters indexed file-list records according to the source file-list filename. They solve different problems. Use Search Help in your installed Everything build to verify syntax and quoting.

8.4 Why do live results work while file-list results are missing?

The live index and indexed file lists are separate sources. The EFU may not be included in the active instance, an active filter may hide its records, or the list may be stale. Check File Lists settings and search with the Everything filter before changing the service.

8.5 Is this the same as Windows Search not working?

No. Everything is a separate filename-search application with its own indexes, services, filters, file lists, and optional servers. Rebuilding the Windows Search index generally does not repair an Everything EFU search problem.

8.6 When should I stop troubleshooting?

Stop changing settings as soon as the expected record appears under a simple search and opens when its path is available. If the record appears but the path fails in File Explorer, troubleshoot Windows or network access. If a newly generated EFU works, replace the stale list and leave working live indexes, services, and security controls unchanged.