Everything Filters Not Working: How to Fix It

When filters in voidtools Everything stop applying correctly, the cause is usually not a broken Windows Search index. Everything maintains its own filename index and has its own search options, filter definitions, macros, folder indexes, exclusions, services, and server settings. A filter can appear ineffective because the wrong filter is selected, its search expression is incorrect, a macro is being used differently than expected, matching files are absent from the index, or another option is changing how the query is interpreted.

The fastest way to solve the problem is to separate filtering from indexing. First confirm that the filter changes a controlled set of results. Then verify the active Search menu selection, inspect the filter expression, and check whether the expected files are indexed. Stop as soon as a small repeatable test succeeds. Changing unrelated settings after the filter works can create a second problem and make the original cause harder to identify.

1. Confirm the Symptom With a Small Safe Test

Before editing filters or rebuilding an index, create a controlled test that tells you whether filtering itself is failing. Choose a folder already visible to Everything and identify two files with clearly different extensions, such as one PDF and one TXT file. You can also create harmless empty test files in a temporary folder if your organization permits it.

1. Open Everything normally, without using a customized shortcut or command-line launcher.
2. Clear the search box.
3. Open the Search menu and select the built-in Everything filter.
4. Search for the exact temporary folder name or a distinctive portion of the test filenames.
5. Confirm that both file types appear.
6. Select a relevant built-in filter, such as Documents, and run the same filename search again.

Success means the result set changes in a way that matches the selected filter. If the TXT or PDF file is treated as a document by the current built-in definition while an unrelated file is removed, filtering is functioning. You can stop changing global options and focus on the particular custom filter or macro that failed.

If neither test file appears even with the Everything filter selected, this is primarily an indexing, exclusion, permission, or location problem. A filter cannot return a file that is not available to the active Everything instance.

1.1 Distinguish filters from exclusions

Filters and exclusions solve different problems. A filter narrows the current result set by adding a predefined search expression. An exclusion prevents locations or matching items from being included in the index, or omits them according to exclusion settings. Turning a filter off does not restore a file that was excluded from indexing.

To test the distinction, select the Everything filter and search for the full filename. If the file remains missing, inspect the relevant index and exclusion settings instead of repeatedly editing the filter.

1.2 Check the status bar and visible state

The status bar can reveal whether Everything is still indexing, whether the query produced zero results, and how many objects are available. The checked item in the Search menu identifies the active filter more reliably than memory or the wording of the query.

If the status bar indicates that indexing is active, wait for it to settle before comparing result counts. Success is a stable result count and a predictable change when switching between the Everything filter and the filter under investigation.

2. Check the Active Filter and Its Search Expression

Everything uses one active Search menu filter at a time. Selecting a second filter replaces the first selection rather than stacking two menu filters. This behavior is easy to misread when testing several categories in succession.

2.1 Reset the active Everything filter

An Everything filter reset normally means selecting the built-in Everything entry from the Search menu. It does not mean deleting the database, resetting every preference, or reinstalling the application.

1. Clear the search box.
2. Select Search, then Everything.
3. Verify that Everything is the checked Search menu item.
4. Enter a simple filename fragment with no operators, macros, quotation marks, or regular expressions.

Success means the broad, unfiltered set of indexed matches returns. At that point, stop modifying index settings. Reapply the desired filter and investigate only the difference between its results and the Everything results.

2.2 Verify that only one filter is expected

If you select Audio and then Pictures, Everything does not normally combine both menu filters. Pictures becomes the active filter. To combine conditions, put the required logic into a custom filter expression or the search box rather than expecting multiple Search menu checks.

For example, a custom filter intended to include two extension groups must explicitly express that relationship using supported Everything search syntax. Pay attention to spaces, vertical bars, grouping, and negation because they can change whether terms are treated as AND, OR, or exclusions.

2.3 Inspect custom filter definitions

Open the filter organization or editing interface from the Search menu. The exact wording can differ between release families, but the filter editor exposes the filter name, search expression, and optional macro.

Check the search expression for these common faults:

• An extension was entered without the intended extension operator or wildcard behavior.
• An OR expression lacks grouping and combines with the typed query unexpectedly.
• A minus sign or exclamation-style exclusion removes the desired results.
• A path contains spaces but is not grouped or quoted appropriately.
• The expression assumes regular-expression behavior while regex mode is off.
• The expression uses ordinary Everything syntax while regex mode is on.
• A copied expression contains an invisible or typographic character.

Temporarily replace a complicated expression with a single, known-good condition, such as one file extension. Apply the filter to the controlled test files. Success means the simplified filter returns the intended type and removes the other type. Add conditions back one at a time and stop when the failing condition is identified.

2.4 Test filter macros separately

A filter macro provides a reusable way to invoke filter logic from the search box. The macro name and invocation syntax must match the definition. A duplicated macro name, spelling difference, missing delimiter, or a macro that expands to an invalid expression can make the filter appear inactive.

First select the filter directly from the Search menu. If direct selection works but the macro does not, the index and base filter expression are probably sound. Inspect the macro field, compare it with the exact text entered in the search box, and remove unrelated search terms while testing. Success means direct filter selection and macro invocation return the same controlled result set.

2.5 Review global search options

Search options can alter how both typed queries and filter expressions behave. Check options such as Match Case, Match Whole Word, Match Path, Match Diacritics, and Enable Regex. A setting left over from a previous search may make a valid filter look broken.

Turn off only the options that are not required for the test, then repeat the simple filename query. If results return, re-enable options individually. Stop when you identify the option that changes the result. Do not reset every preference if one visible Search menu toggle explains the symptom.

3. Verify That Expected Files Are Actually Indexed

If a file is absent with the Everything filter active, repairing a custom filter will not make it appear. Determine how the location is indexed and whether the running instance has access to it.

3.1 Local NTFS and ReFS volumes

Everything can use file-system metadata to build fast indexes for supported local volumes. Check the volume pages in Options and confirm that the relevant volume is included. Also confirm that Everything has completed its initial indexing work.

The Everything service can allow the desktop application to obtain the access it needs without running the entire interface as administrator. If service use is configured, verify through Windows Services or Everything options that the service is running and that the application is connected to the expected instance.

Success means a known filename from the volume appears under the Everything filter. Once that happens, return to the filter test instead of continuing to alter service settings.

3.2 Folder indexes, NAS devices, and nonstandard file systems

Network shares, NAS folders, mapped drives, removable media, and file systems that are not indexed through local file-system metadata may need a configured folder index. Open the folder index settings and confirm that the exact UNC path or local path is present and available.

A mapped drive letter exists in a user and session context. A drive mapped in an interactive account may not exist for a service, scheduled task, elevated process, or different user. When practical, use a stable UNC path for a network folder index and ensure the relevant account has read and list permissions.

Success means files newly created in the indexed folder become searchable after the folder index updates. If the built-in Everything filter finds them but a custom filter does not, stop investigating the network and return to the custom expression.

3.3 Check exclusions and result omission

Review exclusion settings for the affected path, filename, extension, hidden state, or system state. Also inspect the active query for negative terms that omit results. Do not disable every exclusion permanently. Temporarily adjust only the specific rule that could match your controlled file.

Success means the known file appears with the Everything filter after the relevant exclusion is removed or corrected. Reapply the desired protection or omission using a narrower rule that does not hide required files.

3.4 Force an index rebuild only when justified

Force Rebuild can help when an included local index is stale or inconsistent, but it is not the first response to a malformed filter. Before rebuilding, confirm that the file is missing under the Everything filter, the correct volume or folder is enabled, and exclusions do not explain the absence.

Use the supported Force Rebuild control in the applicable index options rather than manually deleting database files. Allow the rebuild to finish and watch the status bar. Success means known current files return under the Everything filter. If they do, retest the filter and stop changing index settings.

4. Check Account, Network, and Startup Context

Everything may behave differently when launched under another account, elevated, from a portable directory, through a scheduled task, or with command-line options. These contexts can select different settings, databases, services, or accessible network resources.

4.1 Compare normal and elevated launches

Run the same small test in the way you normally start Everything. If you also test an elevated launch, compare the configured indexes and filter list rather than assuming elevation is automatically better. Different account contexts can expose different mapped drives or profile data.

Success means the normal launch uses the intended configuration and can see the controlled files. Once the working context is identified, correct the shortcut or startup entry instead of routinely running with unnecessary privileges.

4.2 Inspect shortcuts and command-line options

Open the properties of the shortcut, startup item, script, or management tool that launches Everything. Look for options that select a configuration file, named instance, database, filter, search text, server connection, or portable mode. Then launch the executable directly without those extra arguments for comparison.

If the direct launch works, add command-line options back one at a time. Success means you identify the exact option that changes the filter, index, or profile. Stop after correcting that launcher.

4.3 Check portable settings and multiple instances

A portable copy can store configuration near its executable, while an installed copy may use another settings location. Running both can create the impression that a filter disappeared or reverted. Confirm the executable path, window instance, filter list, and indexed locations.

Make a distinctive temporary filter in the instance you are testing. If it does not appear after launching through the usual shortcut, the shortcut may be opening another installation or profile. Success means all launches consistently open the intended instance.

4.4 Review firewall, antivirus, and server settings safely

Local filtering generally does not require public network access. Firewall rules become relevant when the client depends on an Everything server or another remote indexing arrangement. Verify the configured host, port, authentication, network scope, and whether the service is listening only where intended.

Do not expose an Everything server to the public internet merely to test filters. Keep access restricted to trusted networks or a properly secured private connection. Do not permanently disable antivirus software. If security software is suspected, review its event history and create only a narrow, temporary test approved by your security policy.

Success means the client receives the expected remote result set and the local filter then narrows it correctly. If the remote server never returns the file, fix server indexing or permissions before editing client filters.

5. Use Diagnostics Without Destroying a Working Configuration

Diagnostics should answer a specific question. Save or note the current settings before making changes, and change one variable at a time.

5.1 Use direct search syntax tests

Copy the custom filter expression into the search box and test it without additional words. Then test each component separately. If each component works but the combined expression fails, grouping or operator precedence is likely responsible.

Next, select the custom filter and enter only a unique filename fragment. This reveals how the filter expression combines with ordinary input. Success means the direct expression and selected filter produce equivalent results.

5.2 Inspect the Index Journal and debug output

Where available in your Everything build, the Index Journal can help establish whether a file creation, rename, or deletion was observed. Debug logging can also reveal index updates, startup arguments, service communication, or server connection failures.

Enable logging only long enough to reproduce the issue, note the time and affected path, and then turn it off. Logs can contain filenames and paths, so handle them according to your privacy and organizational requirements. Success means the diagnostic output identifies whether the file entered the index or whether the failure occurs later during filtering.

5.3 Run a temporary clean profile test

A clean profile is useful when direct syntax works but the normal instance remains inconsistent. Preserve the existing configuration, then start a temporary test instance or portable copy with a separate settings location. Do not point two writable instances at the same configuration or database files.

Add only one safe test folder or appropriate local volume, create one simple custom filter, and repeat the controlled search. If the clean profile works, compare filter definitions, search toggles, exclusions, and launch arguments with the original profile. Migrate corrections selectively rather than discarding all established settings.

6. Run a Clean Temporary Test Before Broad Changes

When several causes remain possible, use this sequence to isolate the fault without disrupting a production configuration:

1. Record the executable path, active instance, selected Search menu filter, and visible search options.
2. Choose two known indexed files with different extensions in the same accessible folder.
3. Select the Everything filter and confirm that both files appear.
4. Create a temporary custom filter containing one simple extension condition.
5. Select that filter directly and confirm that only the expected file remains.
6. Assign a unique test macro and compare its results with direct filter selection.
7. Add the original filter conditions one at a time.
8. If files are missing before filtering, inspect the relevant volume, folder index, exclusion, service, or server instead.

The test is successful when the same input repeatedly produces the same filtered result after restarting Everything in the normal launch context. At that point, stop. Do not rebuild unrelated indexes, reset preferences, or change security settings.

7. Quick Fix Checklist

• Select Search, then Everything to reset the active filter.
• Confirm the intended filter is the single checked Search menu item.
• Clear the search box and remove leftover regex or path-specific syntax.
• Check Match Case, Match Path, Whole Word, and Regex options.
• Edit the filter and reduce its search expression to one known-good condition.
• Test direct filter selection before testing its macro.
• Search for the expected file with the Everything filter active.
• Check the status bar for indexing activity and stable result counts.
• Verify the correct volume or folder index includes the file location.
• Review only exclusions that could match the affected file or path.
• Confirm the Everything service is running if your setup uses it.
• Use UNC paths when mapped-drive account context is causing inconsistent access.
• Inspect shortcut and command-line options for alternate instances or profiles.
• Use Force Rebuild only after confirming a genuine index problem.
• Run a separate clean-profile test before resetting a mature configuration.

8. Frequently Asked Questions

8.1 Why does selecting a second Everything filter turn off the first?

Everything has one active Search menu filter at a time. The second selection replaces the first. If you need combined criteria, create a custom filter expression or add supported syntax to the search box.

8.2 How do I reset an Everything filter?

Select the built-in Everything entry from the Search menu and clear the search box. Also disable unintended search options such as Regex or Match Case. This resets the active filtering state without deleting the database or all preferences.

8.3 Why does a filter work from the menu but not through its macro?

The macro name or invocation may not match the filter definition, or extra query text may combine with the expansion unexpectedly. Confirm direct selection first, inspect the macro field, and test the macro alone. If direct selection succeeds, avoid rebuilding the index.

8.4 Why are expected results missing from every filter?

If a file is missing with the Everything filter selected, check its volume or folder index, exclusions, permissions, service state, server source, and account context. This indicates an index or access problem rather than a filter-selection problem.

8.5 Is Everything the same as Windows Search?

No. voidtools Everything uses its own filename index, configuration, and services. Rebuilding the Windows Search index usually does not fix missing Everything results or a faulty Everything filter. Troubleshoot the Everything instance that is actually producing the results.

8.6 When should I use Force Rebuild?

Use Force Rebuild when known files are missing even under the Everything filter, the correct index source is enabled, exclusions do not explain the omission, and the index appears stale or inconsistent. Do not use it as the first fix for an incorrect custom search expression.