Everything Search Finds Folders Not Files: How to Fix It

When Everything search finds folders not files, the cause is usually a type restriction rather than a damaged installation. A folder: search modifier, an active Folder filter, a macro, an exclusion, or a command-line option can limit results before indexing problems are even relevant. Less commonly, files are missing because an index is stale, a folder index cannot access a network location, or Everything is running under a different account context. The safest approach is to prove the symptom with a controlled test, remove type filters, and only then investigate indexing and Windows access.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, create a test that distinguishes a search-filter problem from an indexing problem. This prevents unnecessary database rebuilds and makes each troubleshooting step measurable.

1.1 Create one file and one folder

In a local location that Everything normally indexes, such as your Desktop, create a folder named EverythingTypeTest. Inside or beside it, create a text file named EverythingTypeTest.txt. Wait a few seconds, open Everything, clear the search box completely, and search for EverythingTypeTest.

Interpret the results as follows:

• If both objects appear, indexing works and the original search probably contains a type modifier, filter, macro, or path-specific restriction.
• If only the folder appears, a folder-only restriction is likely, although a file exclusion or stale index remains possible.
• If only the file appears, check for file:, an active file-type filter, or settings that omit folders.
• If neither appears, investigate the index, service, exclusions, startup context, and indexed locations.

Success means the same simple query returns both the test file and test folder. Once that happens, stop changing global settings. Compare the successful test with the original query instead.

1.2 Test the type modifiers explicitly

Everything supports search modifiers that limit results by object type. Run these searches separately:

• folder: EverythingTypeTest should return the folder and omit the file.
• file: EverythingTypeTest should return the file and omit the folder.
• EverythingTypeTest without either modifier should normally return both.

The modifiers can remain in a long query where they are easy to overlook. They may also be introduced through a filter macro or a saved command. If the unrestricted query works, the index is not the problem. Stop troubleshooting the service or database and correct the query or filter.

2. Remove File Versus Folder Restrictions

The most common Everything search finds folders not files fix is resetting the active search mode. Everything filters can silently add search syntax, so deleting visible words from the search box may not remove every restriction.

2.1 Reset to the Everything filter

Open the Search menu and select the Everything filter. Do not assume that an empty search box means no filter is active. If Folder is selected in the Search menu, Everything is intentionally showing folders rather than files.

After selecting Everything, repeat the controlled test. Both test objects should appear. That is the success condition, and there is no reason to rebuild the index if it is met.

2.2 Check the Search menu and filter controls

Review the Search menu for an active type-specific filter. Depending on the filters configured in your installation, choices may include Folder, Audio, Compressed, Document, Executable, Picture, or Video. A custom filter can also contain syntax that limits results to files or folders.

If the filter bar is visible, confirm that its selection agrees with the Search menu. Choose Everything, clear the query, and type only the test name. Also inspect the status bar and other visible filter indicators. They can reveal that a filter is active even when the query itself looks harmless.

Success means the interface indicates the Everything filter and an unrestricted query returns both object types. Stop once this works. Repeatedly toggling unrelated options can hide the original cause.

2.3 Remove file and folder modifiers

Inspect the entire query for file: and folder:. In a complex search, copy the query to a text editor and simplify it from right to left. Start with a plain filename fragment, verify both object types, and then restore one expression at a time.

For example, a query such as folder: project cannot return ordinary files named project. Conversely, file: project excludes directories. Remove the modifier when you want mixed results.

2.4 Check macros such as doc and video

Macros such as doc: or video: represent filters. They are generally intended to match file categories, so they can make folders disappear. A custom macro can contain almost any configured search expression, including folder: or an extension list.

If a query begins with a macro, run the same filename without it. Then review the macro or filter under the filter configuration in Everything Options. If the plain query works, do not change indexing. Adjust the macro only if its current behavior does not match its intended purpose.

2.5 Inspect custom filters

A renamed custom filter can be misleading. A filter called Projects might contain folder:, while another might apply extensions and therefore return files only. Open the filter editor and examine the Search field and macro definition. Temporarily select Everything rather than deleting the custom filter.

Success means the Everything filter restores the missing object type. You can then repair the custom filter without affecting the index or other saved preferences.

3. Check Indexes, Exclusions, and Result Omissions

If an unrestricted Everything filter still returns only one object type, determine whether the missing objects are in the index. Type filtering and indexing are separate layers. Filters decide which indexed results are displayed, while indexing decides what Everything knows exists.

3.1 Review NTFS and ReFS index settings

Open Tools, Options, and the relevant index pages. Confirm that the local volume containing the test objects is included and available. Everything can use file-system metadata on supported local volumes for rapid indexing. This is different from Windows Search, which uses its own indexing service and content-oriented architecture. Rebuilding or changing the Windows Search index does not normally repair an Everything filter problem.

If the volume is present and the new file appears after removing filters, the index is healthy. Stop there. If the folder appears but every new file on that volume is absent, continue with exclusions, journal state, and service access.

3.2 Review folder indexing for NAS and unsupported locations

Mapped drives, network shares, NAS folders, and file systems not handled through Everything's local volume indexing may depend on folder indexing. In Options, review the configured folders and confirm that the expected UNC path or local folder is included.

Use a direct UNC path such as \\server\share when a mapped drive is unreliable across account or elevation boundaries. A drive mapped in your interactive user session may not exist for an elevated process, service, scheduled task, or different user account.

Success means a newly created test file and folder on the share both appear after the folder index updates. If both appear, stop changing permissions and filters.

3.3 Check exclusions carefully

Open the exclusion settings and look for excluded paths, wildcard patterns, hidden or system attributes, and any rules that could match files but not their parent folders. An extension exclusion can remove files while leaving folder names visible. For example, excluding a broad wildcard or a set of extensions may create the impression that Everything is indexing directories only.

Disable one relevant exclusion temporarily rather than deleting the entire list. Repeat the test in the affected path. If the file appears, refine that rule and restore any unrelated exclusions.

3.4 Check result omission settings

Everything can omit or hide results according to configured rules and attributes. Review settings associated with excluded results and result omissions, especially if the symptom affects hidden files, system files, offline files, or one particular path. Also check whether a filter contains a negated expression that removes extensions or file types.

Success means removing the specific omission restores the expected files without broadening results more than intended.

4. Check the Service, Account Context, and Network Access

Service and permission problems are more likely when results are missing from a particular volume or share than when a Folder filter is active globally. Test locally first so that network variables do not distract from the file-versus-folder issue.

4.1 Verify the Everything service state

Open Everything's service settings and confirm that the intended indexing method is active. You can also inspect Windows Services for the Everything service. A stopped service may affect access to local file-system metadata, depending on how Everything is configured and launched.

Restart the service only if it is expected to be running and is stopped or unresponsive. Then reopen Everything and repeat the test. Do not repeatedly reinstall the service if selecting the Everything filter already restores files.

4.2 Compare elevated and standard-user sessions

An elevated Everything process can see a different set of mapped drives from a standard-user process. Likewise, a scheduled or portable instance may run with another configuration and database. Check Task Manager for multiple Everything processes, note whether the title or configuration indicates a separate instance, and confirm which executable you launched.

For a network share, test the UNC path in File Explorer under the same account running Everything. If that account cannot list the files, Everything's folder index cannot reliably add them. Correct share and NTFS permissions using least privilege rather than granting broad public access.

4.3 Check firewall and antivirus controls narrowly

A firewall is relevant mainly when the instance depends on an Everything server connection or remote service. Antivirus or endpoint security may matter if it blocks the executable, database updates, folder traversal, or network access. Review security logs and add a narrowly scoped allow rule only when there is evidence of blocking.

Do not disable protection permanently. Do not expose an Everything HTTP, ETP, or other search server directly to the public internet merely to test connectivity. Keep remote services restricted to trusted networks, authenticated channels, or a properly secured VPN.

4.4 Check server and command-line options

If Everything connects to another instance or starts from a script, verify that the expected server, instance, configuration file, and search are being used. A shortcut can include command-line parameters that select another instance, load a particular configuration, or start with search text. The remote server may also have different indexes and exclusions from the local computer.

Launch Everything normally from its executable or Start menu without the custom shortcut. Select the Everything filter and run the test. If normal startup works, inspect the shortcut target, script, server connection, or instance options rather than rebuilding the good local index.

5. Use Diagnostics Without Jumping to Destructive Changes

Diagnostics should answer a specific question: Is the object absent from the index, or is a search rule hiding it? Use the least disruptive tool first.

5.1 Read the status bar

The status bar helps confirm the number of results and may provide indexing or operational information. Watch whether the result count changes when you switch between Everything, Folder, and another filter. A large immediate change strongly suggests filtering rather than index failure.

Also compare these three searches: the plain test name, file: plus the test name, and folder: plus the test name. Predictable type-specific results indicate that Everything understands both objects correctly.

5.2 Inspect the Index Journal and update behavior

If new objects do not appear, inspect the relevant index status and Index Journal features available in your setup. Confirm that Everything is receiving or processing changes for the volume. A stale index is more plausible when older files appear but newly created files and folders do not.

Try a normal rescan or update mechanism appropriate to the index first. For a folder index, confirm its update schedule and trigger an update if available. Success means newly created objects appear without a full rebuild.

5.3 Use Force Rebuild only after safer checks

Force Rebuild is appropriate when the index is demonstrably inconsistent, not merely because a filter is active. Before using it, confirm the Everything filter is selected, modifiers are absent, exclusions are not responsible, and the affected location is configured for indexing.

If those checks fail and known existing objects are absent, use Force Rebuild from the Indexes options. Allow indexing to complete before judging results. Rebuilding may temporarily reduce or clear results while the index is recreated, so do not start it during a critical workflow without planning.

5.4 Capture debug information when behavior remains unexplained

Debug output can reveal index updates, service communication, command-line settings, and configuration loading. Enable debugging only long enough to reproduce the issue, record the exact query and filter, and then disable it. Logs can contain filenames and paths, so sanitize sensitive information before sharing them.

Useful evidence includes the query, selected filter, affected path, file-system type, whether the location is local or remote, the process account, and whether a clean test succeeds.

6. Run a Clean Temporary Test

When many settings have accumulated, a temporary clean profile can determine whether the problem belongs to the configuration or the underlying system. This is safer than deleting the working database or resetting every preference.

6.1 Start a separate portable test

Use an official portable copy in a temporary folder and keep it separate from the installed instance. Close or distinguish existing instances so you know which configuration is active. Do not overwrite the normal configuration or database.

With default search behavior, index a small safe local location if needed, select Everything, and repeat the one-file, one-folder test. If both appear, the original installation likely has a filter, exclusion, startup parameter, custom macro, or stale configuration. Compare settings methodically instead of replacing everything at once.

6.2 Change one variable at a time

1. Select the Everything filter.
2. Clear the query and search for the exact test name.
3. Test file: and folder: independently.
4. Check the affected location's index configuration.
5. Review only exclusions relevant to that location or extension.
6. Compare normal and custom shortcut startup.
7. Test the same path under the same Windows account.

After every change, repeat the controlled test. When both objects appear, stop. The last change identifies the likely cause and avoids introducing new variables.

7. Quick Fix Checklist

• Choose Search and then Everything to clear the active Folder or file-category filter.
• Remove folder: if files are missing, or remove file: if folders are missing.
• Test without macros such as doc: and video:.
• Check the status bar and visible filter controls for an active restriction.
• Search for one newly created file and folder with the same distinctive name.
• Confirm the affected volume, folder, NAS share, or UNC path is indexed.
• Review exclusions and omission rules that match file extensions or attributes.
• Verify the Everything service and the Windows account running the process.
• Launch without custom command-line arguments, scripts, or server connections.
• Use a temporary clean profile before resetting the normal configuration.
• Use Force Rebuild only after proving that expected objects are absent from the index.

8. Frequently Asked Questions

8.1 Why does Everything show folders but no files?

The most likely causes are an active Folder filter, the folder: modifier, or a custom filter containing folder-only syntax. Select the Everything filter and search for a simple name without modifiers. If files return, indexing was not broken.

8.2 Why does Everything show files but no folders?

Look for file:, an extension-based filter, or a macro such as doc: or video:. These searches intentionally focus on files. Reset to the Everything filter and remove type syntax when you need both files and folders.

8.3 Does rebuilding Windows Search fix Everything?

Usually not. voidtools Everything and Windows Search are separate products with different indexes and search behavior. For this symptom, check Everything's Search menu, query modifiers, filters, indexes, and service. Change Windows Search only when the problem actually occurs in Windows Search.

8.4 Why are files missing only from a mapped drive or NAS?

The share may require folder indexing, and the Everything process may not see the same mapped drive as your interactive account. Test the UNC path, confirm folder indexing, verify permissions under the running account, and check the update schedule. A firewall matters only if network communication is actually involved.

8.5 Should I delete the Everything database?

No, not as a first step. Reset the filter, test the modifiers, review exclusions, confirm the indexed location, and try a normal update first. Use Force Rebuild only when evidence shows that the index itself is incomplete or inconsistent.

8.6 How do I know the issue is fixed?

With the Everything filter active, a plain search for your controlled test name should return both the file and folder. Then the original location should return the expected object types without an unintended modifier or filter. Once those checks pass, stop changing settings and remove the temporary test objects if desired.