Everything Macros in Custom Filter Not Working: How to Fix It

When an Everything custom filter macro does not expand or returns unexpected results, the problem is usually local to the filter definition, macro name, search syntax, or active search state. Less commonly, the macro expands correctly but the expected files are absent from Everything's index because of exclusions, folder-index settings, permissions, network availability, or the account under which Everything is running.

This guide focuses specifically on custom filter macros in voidtools Everything for Windows. It does not treat Everything as Windows Search. Everything maintains and queries its own filename index, while Windows Search uses separate indexing services and settings. Changing a Windows Search option will not normally repair an Everything filter macro.

1. Confirm the Symptom With a Small Safe Test

Before changing indexing, services, or security settings, determine whether the macro itself is failing. A controlled test prevents an unrelated indexing problem from being mistaken for a macro problem.

1.1 Create a predictable test file

Create a harmless file in a location that Everything already searches, such as your Documents folder. Give it a distinctive name, for example macro-test-unique-7421.txt.

Enter the exact filename in Everything without using a filter or macro. If the file appears, the basic index can see it. If it does not appear, stop troubleshooting the macro temporarily and investigate indexing, exclusions, folder coverage, or account access.

Next, search for a simple extension expression such as ext:txt. This confirms that ordinary Everything search functions work. Finally, activate or invoke the custom filter macro you are testing.

Success means the distinctive file appears when its properties match the filter. Once that happens, stop changing index or service settings. The remaining issue, if any, is likely in the original search terms rather than the macro mechanism.

1.2 Separate filter activation from macro invocation

A named filter and its macro are related but not identical ways of applying a saved search. Selecting a filter from the Search menu applies its saved search rules. A configured macro lets you invoke that filter from the search box by entering its macro name followed by a colon.

For example, if a filter's Macro field is set to mytext, test it with mytext:. Do not assume that the filter's display name is automatically its macro name. Open the filter definition and read the Macro field directly.

Compare these three tests:

1. Enter the filter's underlying search expression directly.
2. Select the filter from the Search menu.
3. Invoke the configured macro from the search box.

If the direct expression and menu filter work but the macro does not, the index is probably healthy. Concentrate on the macro name, punctuation, conflicts, and filter definition.

2. Check the Custom Filter Definition and Macro Syntax

The fastest fix for Everything macros in custom filter not working is often a small correction in the filter organizer. Avoid rebuilding the index until these checks are complete.

2.1 Edit the filter from the organizer

Open Everything and use Search > Organize Filters. Select the affected custom filter and choose the edit option. Check the following fields carefully:

• Name: The human-readable filter name shown in menus.
• Search: The actual Everything search expression applied by the filter.
• Macro: The short name used to call the filter from the search box.
• Keyboard shortcut: An optional shortcut that is separate from macro invocation.

Copy the Search field into the normal search box and run it directly. This is the most useful diagnostic step because it shows whether the saved search expression works independently of the macro.

If the copied expression fails, correct the expression first. If it succeeds, restore the filter and focus on the Macro field.

2.2 Verify the macro name and colon

Invoke a filter macro using the exact configured macro name followed by a colon. A macro named projectdocs is called with projectdocs:, not merely projectdocs.

Use a short, distinctive macro name containing uncomplicated letters for the first test. Avoid spaces, punctuation, or a name that resembles an existing search function. After confirming that the simple name works, you can decide whether a more descriptive name is necessary.

Success looks like the filter's saved search taking effect as soon as the macro is entered. If a simple unique name works, stop changing other settings. The old name was malformed, ambiguous, or conflicting.

2.3 Check for conflicts with built-in macros and search functions

Everything includes built-in search functions and macros such as extension, path, folder, file, size, date, and attribute-related expressions. A custom macro that reuses or closely resembles a built-in term can be interpreted differently than intended.

Rename the custom macro to something unlikely to collide, such as cbtestfilter, save it, and test cbtestfilter:. Do not change the filter's Search expression at the same time. Changing one variable makes the result meaningful.

If the renamed macro works, keep the unique name or choose another clearly distinct name. There is no reason to rebuild the database or modify Windows permissions after identifying a naming conflict.

2.4 Test the expanded search text

Everything must ultimately evaluate a search expression. Take the exact text stored in the filter's Search field and paste it into the search box. If the filter is intended to be combined with additional terms, test both the saved expression alone and the combined expression.

Pay attention to spaces, quotation marks, vertical bars used for alternatives, negation characters, parentheses, and path text. A path containing spaces may need quoting. A misplaced space can change grouping, while an unintended exclusion can remove every expected result.

Start with a minimal filter expression such as ext:txt. Confirm it through the custom macro, then add the original conditions back one at a time. The first addition that breaks the result identifies the problematic part of the search expression.

3. Check Search State, Index Coverage, and Result Omission

A macro can work correctly while showing no results because another active option narrows the search. Everything combines the current query, active filter, case and path options, and indexed content.

3.1 Clear hidden restrictions in the user interface

Open the Search menu and review the active filter and search options. Temporarily return to the broadest filter, commonly the Everything filter, and disable restrictive options that are not required for the test. Clear the search box before entering the test macro again.

Also check whether Match Case, Match Path, Match Whole Word, Match Diacritics, or regular-expression mode is active. Their exact relevance depends on the expression, but each can change what matches. A regular expression mode is especially important because ordinary Everything syntax may not behave as expected while it is enabled.

Success means the expected result returns after one restrictive option is removed. Stop there and decide whether that option should remain off or whether the custom filter should be rewritten to accommodate it.

3.2 Read the status bar

The status bar helps distinguish a working search with zero matches from an application that is still indexing or has an unexpectedly small index. Compare the reported result count after running the direct expression, selecting the filter, and invoking the macro.

If invoking the macro changes the result count in the same way as selecting the filter, the macro is being recognized. Missing files then point toward index coverage or filter logic rather than expansion failure.

3.3 Review NTFS and folder indexing

Everything can index local NTFS volumes using filesystem metadata when it has the required access and configuration. Other locations, including many network shares, mapped drives, removable devices, and non-NTFS filesystems, may depend on folder indexing or a separate Everything server connection.

Open the relevant Indexes pages in Everything's Options and confirm that the volume or folder containing the missing file is included. For a folder index, verify the folder path, update behavior, and current availability. Do not assume a mapped drive visible in File Explorer is visible in the account context running Everything.

Success means a direct filename search finds the file after the relevant index has updated. Only then should you retest the custom macro.

3.4 Inspect exclusions before rebuilding

Review Everything's exclusion settings for excluded paths, files, extensions, hidden items, or system items. A broad path exclusion or wildcard can remove matching files from the index even though the macro syntax is correct.

Temporarily adjust only the exclusion that could affect the controlled test location. Do not remove all exclusions indiscriminately, especially on managed systems where they may exist for operational or privacy reasons.

If the test file appears after correcting a specific exclusion, indexing was the cause. Stop changing the filter unless its search expression still behaves incorrectly.

4. Check Services, Network Shares, and Account Context

Service and network issues matter only when the missing results are stored in locations affected by them. They do not normally explain a macro that fails against files already visible in ordinary Everything searches.

4.1 Distinguish the Everything Service from Windows Search

The Everything Service can help the Everything client access NTFS indexing information without requiring the user interface to run with elevated privileges. It is not the Windows Search service. Restarting or reconfiguring Windows Search is therefore not a targeted fix for an Everything custom filter macro.

In Everything's Options, verify that the configured service state matches how the application is intended to run. If Everything reports a service connection problem, correct that problem using the application's own service controls or Windows service management. Avoid repeatedly launching different copies as administrator and non-administrator because that can create confusing account and configuration differences.

4.2 Check mapped drives and network shares

Windows drive mappings are associated with a user and logon context. A mapped drive available to your interactive desktop may not exist for a service, scheduled task, elevated process, or another account. If results are missing only from a NAS or share, test the underlying UNC path, such as \\server\share, where appropriate.

Confirm that the account accessing the share can list the target folder and read filenames. If Everything uses folder indexing for that location, verify that the configured path is reachable. Reconnect the share and allow the folder index to update before retesting.

Success means the file appears through a plain filename search. At that point the macro should work if the file meets its saved search conditions.

4.3 Review firewall and server settings safely

If your setup queries another Everything instance through an ETP or other supported server feature, verify the configured server address, port, credentials, and network reachability. A local custom macro cannot return remote files when the remote connection is unavailable or the server's index does not contain them.

Use narrowly scoped firewall rules appropriate for trusted networks. Do not expose an Everything search server directly to the public internet merely to test a filter, and do not disable the firewall or antivirus permanently. A brief, administrator-approved diagnostic can identify blocking, but the final solution should preserve security controls.

4.4 Check startup and portable-app behavior

Portable users can accidentally start a different Everything executable, configuration file, or instance than the one where the filter was created. Confirm the executable path and whether the expected custom filter appears in Organize Filters.

Startup shortcuts, command-line options, instance names, and portable configuration behavior can direct Everything to another profile. If the filter is absent or has an older definition after startup, correct the shortcut or configuration location rather than recreating the entire index.

Success means the same filter definition remains present after closing and reopening the intended Everything instance.

5. Use Targeted Diagnostics Before Force Rebuild

Diagnostics should answer a specific question. A database rebuild is useful when the index itself is demonstrably stale or inconsistent, but it is not the first remedy for a misspelled macro.

5.1 Compare four controlled searches

Run these tests in order and note the result count:

1. Search for the unique test filename.
2. Run the filter's saved Search expression directly.
3. Select the filter from the Search menu.
4. Invoke the filter through its configured macro.

If steps two and three work but step four fails, edit the macro name or syntax. If only step one works, the filter expression is wrong. If step one fails, investigate the index. This sequence isolates the fault without destructive changes.

5.2 Use debug output when the behavior remains ambiguous

Everything provides debugging facilities that can help advanced users observe search and indexing behavior. Use the application's documented debug options or console rather than downloading unofficial diagnostic tools. Reproduce the problem once, record the relevant output, and remove sensitive filenames or network paths before sharing logs.

For managed systems, record the Everything executable path, instance name, launch command, account context, filter name, macro name, direct search expression, and whether the source is local NTFS, a folder index, or a remote server. Those facts are usually more useful than a screenshot showing zero results.

5.3 Review the Index Journal

If ordinary searches omit recently created or renamed files, the Index Journal can help determine whether Everything observed the filesystem change. This is relevant to stale indexing, not to macro parsing itself.

If the journal shows the file event but the file remains absent, review exclusions and index configuration. If the journal does not cover the location, confirm that the volume or folder is actually indexed.

5.4 Use Force Rebuild only when evidence points to the index

Consider Force Rebuild when a covered location is available, exclusions are correct, service access is healthy, and plain filename searches still omit files that should be indexed. Expect rebuilding to consume time and resources according to the size and type of indexed content.

Do not delete the database manually as an opening step. Force Rebuild through the supported interface is safer and preserves a clearer troubleshooting path. After rebuilding, first test the exact filename without a macro. If it appears, test the filter expression and macro in sequence.

6. Run a Clean Temporary Test Before Broad Changes

If the macro remains broken and several settings may be involved, use a temporary clean Everything profile or separate test instance. The goal is not to erase the working configuration. It is to determine whether the behavior follows the existing profile.

Back up or record the affected filter definition first. Start a temporary instance according to Everything's documented instance or configuration methods, using only a small safe test location where practical. Create one filter with a simple expression such as ext:txt and a unique macro such as cbtestfilter.

If the clean test works, the executable and basic macro feature are functioning. Compare the original profile's filter definition, active search options, startup command, and configuration location. Reset or recreate only the affected filter.

If the clean test fails too, confirm that you are invoking the macro with the colon and that the test file appears in a direct search. Then gather the exact reproduction steps and consult the official Everything support documentation or forum.

6.1 Reset one filter instead of all settings

In Organize Filters, record the filter's name, Search expression, macro, and shortcut. Delete or rename only that custom filter, then recreate it with a unique macro and the simplest working expression. Test it before restoring complex conditions.

This targeted reset avoids losing unrelated filters, indexes, exclusions, server settings, keyboard shortcuts, and interface preferences. Once the recreated filter works, add conditions one by one. Stop as soon as the intended results appear consistently.

7. Quick Fix Checklist

• Confirm the expected file appears in a plain filename search.
• Open Search > Organize Filters and inspect the exact Macro field.
• Invoke the macro with its configured name followed by a colon.
• Rename the macro to a unique, simple name to avoid built-in conflicts.
• Paste the saved Search expression into the search box and test it directly.
• Clear restrictive search options and select the broad Everything filter.
• Check exclusions and verify that the target volume or folder is indexed.
• For NAS files, verify share access, UNC paths, and folder-index updates.
• Confirm the intended portable instance, profile, and startup command are in use.
• Recreate only the affected filter before resetting all settings.
• Use Force Rebuild only when plain searches prove the index is incomplete.
• Stop changing settings as soon as the direct search, filter, and macro agree.

8. Frequently Asked Questions

8.1 Why does selecting my custom filter work while its macro does not?

The saved Search expression is probably valid, but the Macro field may be empty, misspelled, invoked without a colon, or conflicting with a built-in search term. Check the filter in Organize Filters, assign a unique macro name, and test that name followed by a colon.

8.2 Why does the macro return zero results even though it is recognized?

An active search option, another filter condition, an exclusion, or incomplete index coverage may remove the expected files. Paste the filter's Search expression into the search box, clear other terms, and confirm that the files appear in ordinary searches.

8.3 Do I need to restart or repair Windows Search?

No, not for this symptom. voidtools Everything and Windows Search use different indexing systems. Check Everything's filter, index, service, and folder settings. Windows Search becomes relevant only if you are separately troubleshooting results in File Explorer or another application that uses it.

8.4 Why are macro results missing only from my NAS?

The NAS may not be covered by the local NTFS index. Verify the folder index or remote Everything server setup, share permissions, network availability, and the account context. Test a plain filename from the NAS before blaming the macro.

8.5 Should I delete Everything's database?

Not as a first step. First test the macro name, direct search expression, active options, exclusions, and index coverage. If plain searches remain incomplete despite correct settings, use the supported Force Rebuild option before considering manual database changes.

8.6 When should I stop troubleshooting?

Stop when the expected file appears in a plain search, the saved expression produces the intended set, selecting the filter gives the same result, and invoking the macro reproduces it. Further service, firewall, index, or profile changes would add risk without addressing the solved symptom.