Everything Excluded Files Still Showing: How to Fix It

You added a file or folder to the exclusion list in voidtools Everything, but it still appears in search results. This usually means the rule does not match the actual path, the index has not been rebuilt, the visible result is coming from another indexed source, or you are changing settings in a different Everything instance or portable configuration. The safest approach is to reproduce the problem with one test folder, verify each setting in order, and stop as soon as the excluded item disappears.

Everything is not Windows Search. Windows Search maintains its own index and settings, while Everything uses its own indexes, configuration, database, and optional service. Changing Windows indexing options will not normally fix an Everything exclusion problem. The steps below focus specifically on files showing despite exclusions.

1. Confirm the Symptom With a Small Safe Test

Before changing multiple settings, create a controlled test that makes the outcome unambiguous. This prevents unrelated filters, network paths, old bookmarks, or complicated wildcard rules from obscuring the real problem.

1. Create a folder such as C:\EverythingExcludeTest.
2. Create a harmless text file inside it named excluded-test-unique.txt.
3. Search Everything for excluded-test-unique.txt.
4. Confirm that exactly one expected result appears.
5. Add the test folder to Everything's folder exclusion list.
6. Apply the settings and search for the unique filename again.

If the test file disappears, Everything's exclusion mechanism is working. Your original rule, path, source, or instance is the likely problem. Stop changing global settings and compare the working test rule with the original exclusion.

If the file remains visible, continue through the checks below. Record its full path from the Path column or properties before making another change. A filename alone is not enough because an identically named file may exist on another volume, share, or folder index.

1.1 Verify That You Are Looking at a Live Result

Clear the search box and enter the unique test filename manually. Do not rely on an old exported list, a third-party launcher, an Everything bookmark with additional settings, or another application that queries an Everything server. Open the file's properties or inspect its full path to confirm that it is the excluded object.

Success means the result either disappears or is shown to be a different copy outside the excluded path. If it is a different copy, the exclusion is already doing its job and no rebuild is needed for that rule.

2. Check the Exclude Rule and Its Match

Open Everything and go to Tools > Options > Indexes > Exclude. Labels and layout can differ between supported builds, but the Exclude page is where index-level folder and file exclusions are normally configured.

2.1 Use a Folder Exclusion for an Entire Folder

If the goal is to exclude everything beneath a directory, add the directory through the folder exclusion control rather than typing a broad filename wildcard. Browse to the folder when possible. Browsing reduces mistakes involving drive letters, spaces, separators, and network paths.

Check the full path carefully. These are different locations:

• C:\Data\Archive
• D:\Data\Archive
• \\Server\Data\Archive
• Z:\Archive

A mapped drive and its UNC path may reach the same storage, but Everything can index them as different sources. Excluding Z:\Archive does not necessarily exclude a separately configured folder index for \\Server\Data\Archive.

Success means files under the exact excluded folder no longer appear after the exclusion is applied and, when required, the relevant index is rebuilt. Once the controlled test passes, stop modifying the exclusion list.

2.2 Check Wildcards, Slashes, and Path Assumptions

Filename exclusions and folder exclusions solve different problems. A pattern such as *.tmp targets matching names. It is not a reliable substitute for selecting a specific folder when your intention is to exclude an entire directory tree.

Review these common rule errors:

• Using a filename pattern when a folder path should be excluded
• Entering only a folder name and assuming it matches every full path
• Excluding the parent on one drive while the result comes from another drive
• Mixing a mapped-drive path with a UNC folder index
• Adding unnecessary quotation marks to a field that already accepts a path
• Using forward slashes where the setting expects a Windows-style path
• Copying a trailing space or other invisible character into a pattern
• Assuming case is the cause before checking more significant path differences

Windows paths and Everything searches are commonly case-insensitive in ordinary use, so capitalization is rarely the first cause. Even so, copy the path exactly as displayed and use backslashes for Windows paths. This removes ambiguity and makes the rule easier to audit.

2.3 Simplify Complex Exclude Patterns

If a long wildcard expression does not work, temporarily replace it with one direct exclusion for the test folder. Do not debug several semicolon-separated patterns, regular expressions, macros, or path conditions simultaneously.

After the simple folder exclusion succeeds, restore patterns one at a time. Search for a uniquely named file after each addition. The first change that makes the file reappear identifies the problematic rule or assumption.

3. Rebuild the Relevant Index When Necessary

An index exclusion controls what Everything keeps in the affected index. If an item was already indexed, applying a changed exclusion may require the index to update or rebuild before the old entry is removed. Use Force Rebuild from the appropriate index settings after confirming that the exclusion itself is correct.

Do not begin by manually deleting Everything's database. A Force Rebuild is safer because it asks Everything to recreate its indexes through the application. It also preserves the opportunity to diagnose a configuration or instance mismatch.

3.1 Watch the Status Bar During the Rebuild

After initiating a rebuild, watch Everything's status bar. Wait until indexing activity has completed before judging the result. Searching while a rebuild is underway can produce changing or incomplete results.

When the rebuild finishes, search for the unique test filename again. Success means the excluded file is absent while ordinary non-excluded files remain searchable. Stop troubleshooting at that point. Repeated rebuilds will not improve a rule that is already working.

3.2 Distinguish NTFS Indexes From Folder Indexes

Everything can obtain filenames from local NTFS indexes and from explicitly configured folder indexes. Folder indexing is often used for network shares, NAS storage, non-NTFS volumes, or locations that cannot be indexed through the NTFS change journal.

Open the relevant Indexes pages and identify every source that could contain the visible path. A location might be reachable through both a local volume and a folder index, or through both a mapped drive and a UNC share. Remove an unintended duplicate source or apply the appropriate exclusion to the source actually producing the result.

Success means only one intended representation of the location remains, and its excluded subtree no longer appears.

4. Separate Index Exclusions From Result Omissions

An index exclusion prevents matching items from being retained in an index. A result omission or search-time filter hides matching items from the current results without necessarily removing them from the underlying index. Confusing these mechanisms can make an exclusion appear unreliable.

If you used a result-omission feature, filter, bookmark, macro, or search expression, verify that it is active in the window where you are testing. A new window, another instance, or an external client might not inherit the same temporary search state.

Conversely, if you want the files excluded consistently from the index, configure the Exclude page instead of depending on a negative search expression. A query such as !path: can be useful as a diagnostic test, but it does not prove that an index-level exclusion is configured.

4.1 Test Without Filters or Advanced Search Syntax

Select the broadest normal filter, commonly Everything, clear the search box, and search only for the unique filename. Disable options such as Match Case, Match Whole Word, Match Path, or regular-expression mode if they are not needed for the test.

This step is important because an active filter or malformed query can create the opposite symptom, including Everything results missing when they should be visible. Once the plain search behaves correctly, reapply filters individually.

5. Check the Running Instance, Service, and Portable Configuration

Multiple Everything installations or instances are a frequent reason that a correct setting appears to have no effect. You may edit exclusions in one process while searching through another process, launcher integration, server, or portable copy.

5.1 Confirm Which Everything Process You Are Using

Close extra Everything windows and inspect the system tray for additional running copies. If you intentionally use named instances, confirm that the instance whose options you changed is the same instance receiving the search.

Command-line shortcuts can select an instance, load a specific configuration, or start Everything from a different folder. Review the shortcut target and startup scripts for instance-related or configuration-related arguments. Test by launching the intended executable directly, without optional arguments.

Success means the same exclusion appears when you reopen Options from the exact search window showing the problem.

5.2 Understand What the Everything Service Does

The Everything service helps a standard user account index NTFS volumes without running the main interface with elevated privileges. The service is not the same thing as the search interface, and changing Windows Search service settings is unrelated.

If the service is stopped, misconfigured, or tied to another installation, local NTFS indexing may not update as expected. Check the service through Everything's options or Windows Services, then restart Everything normally if needed. Do not permanently disable antivirus or other security software to test this symptom.

A healthy result is that Everything completes indexing, ordinary filesystem changes appear, and the exclusion survives an application restart.

5.3 Check Portable Settings and Write Access

A portable copy commonly keeps configuration near its executable. If that location is read-only, protected, synchronized, or unavailable, exclusion changes may appear to apply during the session but disappear after restart.

Change a harmless setting, exit Everything cleanly, reopen it, and verify that the change persisted. Also confirm that you are editing the portable copy you actually launch. Avoid running one copy from a temporary archive extraction folder and another from a permanent tools directory.

6. Check Windows, Network, and Account Context

Windows permissions do not normally make an excluded local file remain in an otherwise correct Everything index. They become relevant when the indexed path changes according to the account, drive mapping, share credentials, or startup context.

6.1 Mapped Drives and NAS Shares

Mapped drive letters are associated with a user session. An elevated process, service account, scheduled task, or different user may not see the same mappings. Everything may therefore index a NAS share through a UNC path while you exclude its mapped-drive form, or the reverse.

Compare the result's displayed path with the path listed under folder indexing and exclusions. Use the same canonical path form consistently. For network storage, UNC paths are often easier to recognize across sessions, provided the account running the relevant process has access.

6.2 Firewall and Security Software

A firewall matters mainly when an Everything client queries an ETP, HTTP, or other supported search server, or when a network folder index must access a remote share. If local searches behave differently from remote searches, test directly on the computer hosting the index.

Do not expose an Everything search server to the public internet as a troubleshooting shortcut. Keep it limited to trusted networks, authenticate and restrict it where supported, and follow your organization's firewall policy.

Antivirus software can occasionally interfere with configuration writes or startup, but permanent disabling is not an appropriate fix. Check security logs or create a narrowly scoped, temporary test approved by your administrator.

6.3 File System and Startup Timing

Local NTFS volumes can be updated through NTFS indexing behavior, while network shares and other file systems may depend on folder indexing and scheduled rescans. If Everything starts before a mapped share becomes available, that index may be stale or unavailable.

Confirm that the share is connected, rescan or rebuild the relevant folder index, and then repeat the unique-file test. Success means the displayed source and its exclusion remain consistent after sign-out, restart, or reconnection.

7. Use Diagnostics Without Destroying Useful Evidence

If the straightforward checks fail, collect evidence before resetting anything. The status bar, Options pages, index journal information, and debug logging can reveal whether Everything recognizes the source and receives filesystem changes.

7.1 Inspect Index State and Journal Behavior

Check whether the total indexed item count changes after creating or deleting a test file. If ordinary filesystem changes do not appear, the wider issue may be that the Everything index is not updating rather than an exclusion failure.

For local NTFS volumes, review the applicable index and journal information exposed by Everything. For folder indexes, verify the configured rescan behavior and availability of the path. Force Rebuild only the relevant index after recording the current configuration.

7.2 Capture a Short Debug Session

Use Everything's documented debug or logging facilities only long enough to reproduce the test: start logging, create or locate the test file, apply the exclusion, rebuild if needed, search once, and stop logging. Logs can contain filenames and paths, so store and share them according to your privacy and security requirements.

Look for evidence that the intended instance loaded the configuration and processed the correct volume or folder index. If the log refers to a different path or instance, correct that mismatch rather than repeatedly rebuilding.

8. Run a Clean Temporary Test

When settings have accumulated over time, a clean temporary profile or separate named instance can determine whether the problem is configuration-specific. Do not overwrite your working profile. Back up relevant settings and create a temporary, isolated configuration following the official Everything documentation for your installation type.

1. Start one temporary instance with no third-party launcher or server client.
2. Index only a safe, small test location where practical.
3. Create the unique test folder and file.
4. Confirm that the file initially appears.
5. Add the folder through the Exclude page.
6. Apply the setting and use Force Rebuild if the index requires it.
7. Confirm that the file disappears.

If the clean test works, the application and basic exclusion mechanism are functioning. Compare the original profile's folder indexes, filters, result omissions, startup arguments, and duplicate instances. If the clean test fails too, preserve the exact steps, paths, filesystem type, and logs for a focused support request.

9. Quick Fix Checklist

• Confirm the visible result's full path, not just its filename.
• Create one uniquely named test file in one test folder.
• Add the folder through Options > Indexes > Exclude.
• Use a folder rule for a folder and a wildcard only for matching filenames.
• Check drive letters, UNC paths, backslashes, spaces, and copied characters.
• Look for duplicate NTFS, folder, mapped-drive, or network indexes.
• Use Force Rebuild after changing an index exclusion when necessary.
• Wait for indexing to finish before searching again.
• Clear filters, bookmarks, regex mode, and advanced search syntax.
• Distinguish temporary result omissions from index exclusions.
• Verify that you changed the same instance or portable copy you search with.
• Confirm settings persist after a clean exit and restart.
• Test locally if a remote Everything server returns different results.
• Use a temporary clean profile before resetting the main configuration.

10. Frequently Asked Questions

10.1 Why do excluded files still appear after I click Apply?

The rule may not match the displayed path, or an existing indexed entry may remain until the relevant index updates. Confirm the full path, simplify the rule to one folder exclusion, and use Force Rebuild if necessary. Wait for indexing to finish before retesting.

10.2 Does Everything use Windows Search exclusions?

No. Everything and Windows Search maintain separate indexing systems and settings. Configure the exclusion inside voidtools Everything. Changing Windows Indexing Options will not normally remove a result from Everything.

10.3 Should I exclude a folder with a wildcard?

Usually not. If you want to exclude an entire folder tree, add that folder through the folder exclusion control. Use filename wildcards for file types or naming patterns, such as temporary-file extensions, after testing the pattern on a small sample.

10.4 Why does the exclusion work locally but not in another application?

The other application may query a different Everything instance, named instance, portable installation, or remote server. Check its connection and command-line configuration. The exclusion must exist in the instance that owns the index returning the result.

10.5 Can the same network folder be indexed twice?

Yes. A share may be configured through a mapped drive and a UNC path, or appear through multiple folder indexes. Inspect the Path column and folder-index settings. Remove unintended duplicate sources or exclude the exact source returning the result.

10.6 When should I stop troubleshooting?

Stop when the unique file in the excluded test folder no longer appears, normal non-excluded files still appear, and the behavior survives an Everything restart. Additional rebuilds, security changes, or configuration resets are unnecessary once those checks pass.