Everything EFU File List Not Opening: How to Fix It

When an Everything File List does not open, opens in the wrong program, or appears to load without useful results, the cause is usually narrower than a general search failure. The most common explanations are a missing Windows file association, the portable edition not being registered for EFU files, an inaccessible path stored inside the list, or confusion between a static File List and Everything's live index.

EFU stands for Everything File List. An EFU file is a CSV-formatted snapshot of filenames and related information. Opening one does not automatically make every listed file accessible, nor does it repair an outdated live index. Work through the checks below in order, and stop as soon as a small test EFU opens correctly and its accessible files launch as expected.

1. Confirm the Symptom With a Small Safe Test

Before changing services, indexes, exclusions, or security settings, determine exactly what is failing. There are three distinct symptoms that are often described as “Everything EFU file list not opening.”

• Double-clicking the EFU opens another application or displays an unknown-file prompt.
• Everything opens, but the File List does not appear or produces no expected entries.
• The EFU entries appear, but opening a listed file fails because its stored path is unavailable.

1.1 Create a small new EFU

Create a temporary folder in a location you can access, such as a folder under Documents. Add two or three harmless files with distinctive names. In Everything, search for that folder or those filenames, select the results, and use the File List export or save command to create a new EFU in Documents.

Now close the File List and open the new EFU from inside Everything. If this small list opens and shows the expected entries, Everything can read EFU files. The original EFU is then likely malformed, encoded unexpectedly, empty, outdated, or filled with paths that are no longer accessible.

Next, double-click the newly created EFU in File Explorer. Success means Windows launches Everything and Everything displays the list. If manual opening works but double-clicking does not, focus on file association rather than rebuilding the Everything index.

1.2 Inspect the EFU without modifying it

An EFU is text-based and can be inspected with a text editor. Make a copy before editing. A normal list contains column headings and rows describing files or folders. If the file is zero bytes, contains unrelated data, or was renamed from another format, Everything may have nothing valid to load.

Do not treat a readable EFU as proof that every target file still exists. The list can preserve names from a disconnected NAS, an offline external disk, or a folder that has since been moved.

2. Check EFU Opening, Association, and File List Behavior

2.1 Open the File List manually

Launch Everything first, then use its File menu to open the File List directly. Depending on the Everything generation and interface, the wording may appear as Open File List or as an equivalent File List command. Select the EFU explicitly rather than relying on Windows double-click behavior.

If manual opening succeeds, stop changing index and service settings. The EFU parser is working, and the remaining problem is almost certainly the Windows association for the .efu extension.

2.2 Repair the EFU file association

The Everything installer includes an option to associate EFU files with Everything. Rerun the official installer, choose the existing installation as appropriate, and enable the EFU association option. This normally provides a cleaner repair than browsing to an executable through Windows and accidentally selecting an obsolete copy.

You can also review the association in Windows Settings under default apps by file type. Check which application owns the .efu extension. If Windows points to a text editor, spreadsheet program, removed executable, or an older portable folder, change it to the Everything executable you actually use.

Success is specific: double-clicking a test EFU launches the intended Everything installation and loads that File List. Once that happens, do not rebuild indexes or alter the Everything service to solve the association issue.

2.3 Understand portable edition limitations

A portable copy generally aims to avoid making system-wide changes automatically. Moving its folder also changes the executable path, which can leave a previously created association pointing to a location that no longer exists. Windows associations may additionally require suitable permissions to register.

For a portable installation, the safest routine is to open Everything and load EFU files manually. If you choose to create an association, make sure it targets the current portable executable and recognize that moving or renaming the folder can break it again. On a managed computer, association policies may override a user's selection, so a system administrator may need to deploy the association.

2.4 Distinguish a File List from the live index

Everything's live index is built from configured local file systems and folder indexes. An EFU is a saved snapshot. Loading a File List does not cause Everything to scan the listed paths, monitor them for changes, or merge their current contents into the live NTFS index.

For that reason, an old EFU can show a file that has been deleted, renamed, or moved. It can also omit a file created after the list was exported. If the list opens but an entry does not, confirm the stored path in File Explorer. If the current file is elsewhere, generate a fresh EFU or use Everything's live index to locate it.

3. Review Search Options That Can Make an Open List Look Empty

Sometimes the File List opens correctly, but active search conditions hide every row. This can resemble an opening failure even though the EFU loaded successfully.

3.1 Clear the search and reset the filter

Delete all text from the search box and select the broad Everything filter rather than Audio, Documents, Folders, or a custom filter. Turn off options such as Match Case, Match Path, Match Whole Word, and regular-expression mode unless you intentionally need them.

Also check whether the search box contains advanced syntax, a path restriction, or a negated term. A query that worked against a local index may not match paths in an imported File List. Success means the unfiltered test EFU displays all of its rows.

3.2 Verify result omission and exclusions

Review Everything's result-omission and exclusion settings if entries vanish only for certain folders, attributes, or patterns. An exclusion designed to hide temporary folders from the live index can also complicate diagnosis when you expect the same names in a File List view.

Temporarily remove only the specific suspected condition, then reopen the small test list. Record the original value before changing it. If nothing changes, restore the setting rather than accumulating unrelated configuration changes.

3.3 Avoid troubleshooting the wrong window or instance

Multiple installations can coexist, especially when an installed copy and a portable copy are both present. The EFU association may launch one instance while you inspect settings in another. Compare the executable location, configuration, window title, and startup behavior.

Close all Everything windows, start the intended executable directly, and open the EFU manually. If that succeeds, repair the association so it targets the same executable.

4. Check File Paths, Permissions, Drives, and Account Context

4.1 Test a listed path in File Explorer

Copy one full path from the EFU and paste it into File Explorer. If Explorer cannot reach it, Everything cannot make the target accessible merely because the name appears in a File List. The EFU itself is functioning as a catalog, but its destination is unavailable.

Common causes include a disconnected external drive, a changed drive letter, a renamed server, a retired share, expired credentials, or a file moved after export. Reconnect the correct resource or create a current File List from the new location.

4.2 Check mapped drives and UNC paths

Mapped drive letters belong to a Windows logon context. A drive mapped in a standard desktop session may not appear to an elevated process, a service, a scheduled task, or another user. If an EFU stores a path such as Z:\Archive, test the equivalent UNC path, such as \\server\share\Archive, when one is available.

For durable NAS lists, UNC paths are often less dependent on a particular user's drive-letter mapping. However, the user still needs share and file-system permissions. Authenticate to the share through File Explorer first, then test the listed file again.

4.3 Compare elevated and standard launches

Running Everything as administrator can change access to mapped drives and network credentials. If the problem occurs only when elevated, close Everything and run it normally. If corporate policy or a specific administrative task requires elevation, ensure the needed network resource is available in that account context.

Success means both the EFU row and its target path behave consistently in the chosen context. Do not weaken folder permissions merely to make a historical list clickable.

4.4 Review antivirus and firewall behavior carefully

Security software may block an executable, quarantine a downloaded EFU, or restrict access to a network location. Check Windows Security protection history, controlled-folder notifications, and your organization's security logs for a specific event at the time of failure. Restore or allow an item only after verifying that it is legitimate.

A firewall is generally not involved when opening a local EFU. It becomes relevant only when Everything is configured to use network features such as an ETP or HTTP server, or when the listed targets reside on a network share. Do not expose an Everything server to the public internet as a troubleshooting shortcut. Test only on trusted networks with appropriate authentication and firewall scope.

5. Use Everything Diagnostics Without Destroying Useful State

5.1 Read the status bar first

After opening an EFU, look at Everything's status bar. It can help confirm whether results are present, whether a search has filtered them, and whether a long operation is still active. Compare the status with the number of rows expected in the small test list.

If the status indicates results but the view appears empty, clear filters, sort by a normal column, and verify that the result pane has not been resized or configured unexpectedly.

5.2 Check the relevant Options pages

Review settings methodically rather than toggling everything. Prioritize the File Lists, General, Indexes, Folders, Exclude, Results, and service-related pages that exist in your installation. Look for an obviously stale path, disabled option, exclusion, or instance mismatch.

Service state and NTFS indexing affect the live database, not basic parsing of a local EFU. If manual opening of the small EFU fails, restarting the service is unlikely to repair its file association or contents. If live results are also missing, service and index checks become relevant as a separate Everything troubleshooting track.

5.3 Use Force Rebuild only for live-index symptoms

Force Rebuild is appropriate when the Everything index is not updating and safer checks confirm that indexed volumes or folder indexes are configured correctly. It is not a primary Everything EFU file list not opening fix because an EFU is separate from the live database.

Before rebuilding, check whether the expected volume is online, supported, included, and visible to the active account. For NAS locations and file systems that are not indexed through local NTFS mechanisms, review Folder Indexing and its update schedule. Rebuild only when the symptom is genuinely stale or missing live results.

5.4 Capture a debug log when behavior is repeatable

If Everything reports an error, closes, or silently rejects a valid test EFU, enable the application's documented debugging output, reproduce the issue once, and save the relevant messages. Record the exact executable path, whether it is installed or portable, the EFU path, and the steps that trigger the failure.

Do not publish logs without reviewing them. File-search logs can reveal usernames, server names, paths, and confidential filenames. A short sanitized reproduction is more useful than a large unscreened log.

5.5 Treat the Index Journal as supporting evidence

The Index Journal is useful when investigating why live results changed or disappeared. It does not make a static EFU current and is not the first tool for a broken .efu association. Use it only when you have established that the separate problem is Everything results missing from the live index.

6. Run a Clean Temporary Test Before Changing More Settings

If the cause remains unclear, test with a fresh temporary configuration. Keep your working installation and database intact. Do not delete the existing database or configuration as an early step.

1. Download Everything only from the official voidtools website.
2. Place a portable copy in a new temporary folder.
3. Run it without importing old settings.
4. Open the small test EFU manually from inside that copy.
5. Then test the original EFU without editing it.

If both files open in the clean copy, the original installation probably has a configuration, association, plugin, command-line, or instance-specific problem. If the small EFU opens but the original does not, inspect or recreate the original list. If neither opens, verify the files, download source, permissions, and exact error before making broader Windows changes.

Also inspect how Everything starts. A shortcut, scheduled task, launcher, or script may pass command-line options that select another instance, configuration file, database location, or startup mode. Start the executable directly with no custom arguments. If direct startup fixes the issue, correct the shortcut or script rather than altering unrelated indexes.

7. Quick Fix Checklist

1. Create a tiny EFU containing files in a local folder you control.
2. Open it manually from Everything's File menu.
3. If that works, repair the .efu association with the official installer or Windows default-app settings.
4. Confirm the association points to the Everything executable you currently use.
5. For portable Everything, expect manual opening unless you deliberately register an association.
6. Clear the search box and choose the Everything filter.
7. Check one stored path directly in File Explorer.
8. Reconnect offline drives or authenticate to network shares without weakening security.
9. Test standard and elevated account contexts if mapped drives behave differently.
10. Use Force Rebuild only when the live index, not the File List, is stale.
11. Run a clean portable test before deleting databases or resetting your main configuration.

Stop troubleshooting when the test EFU opens through the intended method, displays its expected rows, and accessible targets launch correctly. An old list containing unavailable paths does not indicate that Everything itself remains broken.

8. Frequently Asked Questions

8.1 Why does an EFU open in Notepad or Excel instead of Everything?

The .efu extension is associated with that application, or the Everything association points to a missing executable. Open the list manually in Everything to prove it is readable, then enable the EFU association through the official installer or change the Windows default app for .efu files.

8.2 Why can I see an EFU result but not open the actual file?

An EFU stores a snapshot of a path. The target may have moved, been deleted, or reside on an offline drive or inaccessible share. Paste the full path into File Explorer and restore access to the resource. Recreate the EFU if its locations have permanently changed.

8.3 Does opening an EFU add its files to the Everything index?

No. A File List is separate from the live index. It lets you search saved rows, including paths that may currently be offline. To maintain current results for a NAS or unsupported location, configure an appropriate Folder Index or regenerate the EFU on a suitable schedule.

8.4 Will restarting the Everything service fix EFU association?

Usually not. The service helps Everything index supported local file systems without requiring the interface to run with elevated privileges. Windows controls which application opens .efu files. Repair the association if manual opening works.

8.5 Why does a portable Everything association stop working after I move it?

The Windows association can contain the portable executable's old path. Moving or renaming the folder makes that command invalid. Update the association to the new executable or open File Lists manually from the portable application.

8.6 What should I do if Everything search is not working too?

Treat it as a second symptom. Confirm the service or indexing mode, indexed volumes, Folder Index settings, exclusions, account access, and active search filters. Use Force Rebuild only after those checks. A live-index repair will not fix a malformed EFU or an incorrect Windows file association.