Everything Search Syntax Spaces Quotes: How to Fix It

When a voidtools Everything search with spaces, quotes, AND, OR, or NOT produces unexpected results, the cause is usually one of four things: the query is being interpreted differently than expected, a search option or filter is modifying the query, the relevant location is not indexed, or Windows is preventing Everything from seeing the location. The fastest solution is to test the syntax against a few known filenames before rebuilding indexes or changing multiple settings.

This guide focuses on Everything's filename-search syntax, particularly spaces and double quotes. Everything is not the same as Windows Search. Everything primarily finds indexed file and folder names, while Windows Search also uses Windows content indexing and its own query rules. Syntax that works in one search tool may not behave the same way in the other.

1. Confirm the Symptom With a Small Safe Test

Begin with a controlled test in the Everything graphical interface. Do not start by deleting the database, rebuilding every index, or changing security software. A small test separates a syntax problem from an indexing problem.

1.1 Create filenames that reveal how the query is parsed

Create a temporary folder on a location that Everything already indexes, then add several empty text files with names such as:

• red blue.txt
• red monthly blue.txt
• red.txt
• blue.txt
• green report.txt

Wait briefly, then search for the folder or one of the complete filenames. If the files appear, the index is receiving changes. You can now test syntax without guessing whether the target files exist.

1.2 Understand what a space means

In Everything, a space normally acts as AND. The query red blue asks for results containing both terms, but the terms do not have to form one uninterrupted phrase or appear in a particular order.

Therefore, red blue can match both red blue.txt and red monthly blue.txt. This is expected behavior, not a broken phrase search.

Success means every displayed result contains both search terms. If that happens, stop changing index and service settings. The issue was the meaning of the space.

1.3 Use double quotes for an exact phrase

To keep words together, place the phrase inside straight double quotes:

"red blue"

This searches for the adjacent phrase rather than treating the space as an AND separator. It should match red blue.txt but not red monthly blue.txt.

Use straight ASCII quotation marks, not typographic opening and closing quotes copied from a formatted document. If a query copied from email or a web page behaves strangely, delete the quote characters and type them again in Everything.

Success means the exact-phrase result remains while the filename containing an intervening word disappears. Stop troubleshooting if this produces the intended result.

1.4 Test OR, NOT, and grouping

Everything uses operators rather than relying on English words in every context:

• red|blue means red OR blue.
• !green means NOT green.
• <red|blue> report groups the OR expression, then requires report.
• red blue means red AND blue.

For example, <red|blue> report looks for report together with either red or blue. Grouping with angle brackets is particularly useful when AND and OR occur in the same query.

Do not assume that typing the words AND, OR, or NOT will always express the intended logic. Use a space, pipe, exclamation point, and angle brackets respectively. If Everything has Match Whole Word, Match Case, Regex, or another search mode enabled, those options may further alter the result.

1.5 Understand literal quote macros

Everything supports search macros for characters that otherwise have syntactic meaning. The quot: macro represents a double-quote character. It is useful when constructing or passing expressions in contexts where a quote must be represented without prematurely opening or closing a quoted phrase.

However, standard Windows filenames cannot contain the double-quote character. Consequently, a filename-only search for a literal quote will not uncover ordinary NTFS filenames containing that character. Literal-character macros are more relevant to advanced expressions, generated searches, or functions that operate on text beyond a normal Windows filename.

2. Check Search Options, Filters, and Index Settings

If the controlled syntax test fails, inspect the settings that can directly change matching behavior. Change one item at a time and repeat the same query after each change.

2.1 Clear the active filter

Look at the filter selector near the search box. A filter such as Audio, Documents, Executables, or a custom filter can hide otherwise valid matches. Select Everything as the filter for the test.

A custom filter may also add its own search expression. This can make a correct quoted phrase appear broken when the actual problem is an extra extension, path, or exclusion condition.

Success means the missing test files appear after selecting the Everything filter. If so, keep the filter disabled or edit that custom filter rather than changing the index.

2.2 Disable incompatible search modes temporarily

Review the Search menu and temporarily turn off modes that are not required for the test, especially Regex, Match Case, Match Whole Word, Match Path, and Match Diacritics. The exact available items can depend on the installed Everything edition and configuration.

Regex is a common cause of confusion because quotation marks, pipes, spaces, and grouping have different implications in regular expressions. First verify ordinary Everything syntax with Regex disabled. Enable Regex again only if the task actually requires it.

Success means the basic test query behaves normally after one search mode is disabled. At that point, stop changing settings and decide whether that mode should remain off for routine searches.

2.3 Check whether the location is indexed

Search for the full name of a known file without operators. If the file does not appear at all, quote handling is probably not the primary problem.

Open Everything's Options pages and examine the relevant index category:

• NTFS for supported local NTFS volumes.
• ReFS where supported and configured.
• Folders for network shares, mapped drives, NAS locations, or file systems handled through folder indexing.
• Excludes for paths, files, or patterns intentionally omitted.

Everything's rapid local results commonly come from file-system metadata and change journals. A NAS share or ordinary mapped drive is not automatically equivalent to a local NTFS volume. Such locations generally need an appropriate folder index or an Everything server arrangement.

Success means a direct search for the known filename works before syntax is added. Once the base file appears, return to the space and quote tests.

2.4 Review exclusions and result omissions

An excluded folder cannot be restored by changing a quote or OR operator. Check configured exclusions for the full path, drive, extension, hidden-file rule, or wildcard pattern associated with the missing result.

Also verify that results are not being omitted through an active filter, a temporary result-list action, or another configured search expression. If only one directory or extension is absent, an exclusion is more likely than a global indexing failure.

Success means removing or narrowing the relevant exclusion makes the known file appear. Do not remove unrelated exclusions merely to increase the result count.

3. Check Services, Permissions, Drives, and Network Context

Syntax cannot match information that the current Everything instance has never indexed. Service state, account context, and network availability matter when results are missing beyond the small local test.

3.1 Verify the Everything service or administrator mode

Everything may use the Everything service to index local volumes without requiring the interface to run elevated. Open the Options pages and check whether the service configuration is healthy. You can also inspect Windows Services for the Everything service if your installation uses it.

If the service is stopped, start it through the normal Everything or Windows service controls. Avoid repeatedly switching between service mode and running the entire application as administrator without understanding which instance and configuration are active.

Success means the volume appears in the index settings and known files begin appearing or updating. If local results were already current, the service was not the cause of the syntax problem.

3.2 Check mapped drives and NAS shares in the correct account

Mapped drive letters are associated with a Windows logon context. A share visible as Z: in your interactive desktop session may not be visible to a service running under a different account. Prefer a UNC path such as \\server\share when configuring a folder index if that arrangement is appropriate for your environment.

Confirm that the account performing the folder scan can list the target directories and read filenames. Test access in File Explorer under the same user context where practical. Do not weaken share permissions broadly just to make search work.

Success means the configured folder index can scan the share and a newly created test filename eventually appears. Folder indexes may not update as instantly as journal-backed local NTFS indexes.

3.3 Consider firewall and antivirus only when networking is involved

A firewall is relevant when Everything is connecting to an ETP server, HTTP server, or another remote Everything service. It is not a likely explanation for quotation marks behaving differently in a local search box.

If remote search is involved, verify the server address, port, authentication, permitted network profile, and whether the service is listening on the expected interface. Add only narrowly scoped firewall permissions that are necessary for trusted networks. Do not expose an Everything search server directly to the public internet without suitable network security and access controls.

Security software can also delay or restrict access to an executable, configuration directory, or network share. Review its logs and create a specific approved exception only if there is clear evidence of blocking. Do not disable antivirus protection permanently.

3.4 Check portable startup behavior

A portable copy can use an INI file and database associated with its executable directory, while an installed copy may use another configuration. Launching a different executable than expected can make filters, indexes, and syntax options appear to change randomly.

Use Task Manager or the application's information screens to identify the running executable path. Close duplicate Everything windows and confirm whether they belong to the same instance. Check shortcuts for command-line switches that select an instance, configuration, database, server, filter, or initial search.

Success means repeated launches open the intended instance with the same indexes and search options.

4. Use Diagnostics Without Destroying a Working Index

When the cause remains unclear, gather evidence before using Force Rebuild. A rebuild can help an unhealthy index, but it will not correct misunderstood quote syntax or an active filter.

4.1 Read the status bar and narrow the query

The status bar can show result counts and search activity. Start with a direct filename, then add one condition at a time:

1. Search for report.
2. Search for monthly report.
3. Search for "monthly report".
4. Search for <monthly|quarterly> report.
5. Search for <monthly|quarterly> report !draft.

The first step that removes the expected result identifies the condition to inspect. This is more reliable than debugging a long expression all at once.

4.2 Inspect the index journal and update behavior

If existing files appear but newly created or renamed files do not, investigate index updating rather than syntax. Review the NTFS index settings and Index Journal where available. Confirm that the affected volume remains online and that change monitoring is enabled as intended.

For a folder index, check its rescan schedule and whether the path was reachable during the last scan. Network interruptions, sleeping NAS devices, changed credentials, and disconnected VPNs can leave a folder index temporarily stale.

Success means a newly created, renamed, or deleted test file is reflected after the expected update interval.

4.3 Use Force Rebuild only after targeted checks

Force Rebuild is reasonable when a configured local index is clearly stale or inconsistent, the correct volume is selected, the service can access it, and journal monitoring is not restoring updates. It should not be the first response to a phrase-search misunderstanding.

Before rebuilding, note the current index and exclusion settings. Then use the supported Force Rebuild control in Everything's index options. Allow indexing to finish before judging search results.

Success means known files and subsequent changes appear consistently. If they do not, rebuilding again is unlikely to help. Return to permissions, volume type, service state, folder-index access, or instance selection.

4.4 Use debugging for reproducible failures

Everything provides debugging facilities and command-line options that can help identify configuration, index, and startup problems. Capture a short reproduction: launch the intended instance, run the smallest failing query, and note the active filter and search options.

Avoid publishing logs without reviewing them. Search expressions, filenames, paths, server names, and usernames may contain sensitive information.

5. Run a Clean Temporary Test

If ordinary syntax still behaves incorrectly, test with a separate Everything instance or temporary clean profile rather than overwriting the working configuration. Everything supports named instances through its command-line options. A separate instance can isolate filters, macros, search history, startup switches, and index settings.

Close unnecessary Everything windows, launch a clearly named test instance, and configure only the minimum local test location. Run the same queries with the Everything filter selected and special search modes disabled.

• If the clean instance works, the original profile likely contains a filter, macro, search option, startup switch, or index configuration causing the behavior.
• If both instances fail only for files on one location, investigate that location's index, file system, permissions, or connectivity.
• If the GUI works but a command-line search fails, inspect shell quoting and argument boundaries.

Windows command shells process quotation marks before an application receives its arguments. A query passed through Command Prompt, PowerShell, a batch file, or another launcher may need shell-specific quoting. Verify the intended expression in the Everything GUI first, then use the documented -s search option and the quoting rules of the shell in use.

Success means the temporary instance reproduces correct space, quote, OR, NOT, and grouping behavior. Stop making broad system changes and compare only the relevant settings with the original instance.

6. Quick Fix Checklist

1. Use a space for AND: red blue.
2. Use straight double quotes for an exact phrase: "red blue".
3. Use a pipe for OR: red|blue.
4. Use an exclamation point for NOT: !draft.
5. Use angle brackets for grouping: <red|blue> report.
6. Select the Everything filter.
7. Temporarily disable Regex and other unnecessary matching options.
8. Search for one known filename without operators.
9. Confirm the drive, folder, share, or NAS location is indexed.
10. Review exclusions before rebuilding anything.
11. Verify the service, account context, and folder-index credentials.
12. Confirm that you launched the intended installed or portable instance.
13. Use a clean named instance if configuration interference is suspected.
14. Use Force Rebuild only for evidence of a stale or inconsistent index.

7. Frequently Asked Questions

7.1 Why does a space return files where the words are separated?

A space means AND in ordinary Everything syntax. It requires both terms but does not make them an adjacent phrase. Use straight double quotes around the words when adjacency matters.

7.2 Why do AND, OR, and NOT not work as expected?

Use Everything's standard operators: a space for AND, | for OR, and ! for NOT. Use < and > to group mixed expressions. Also check whether Regex or a custom filter is active.

7.3 Why are files missing even with the correct quoted phrase?

First search for one distinctive word from the filename. If the file remains absent, inspect the active filter, exclusions, indexed volumes, folder indexes, network availability, and instance configuration. Correct syntax cannot return an unindexed item.

7.4 Why is Everything not updating a NAS or mapped drive?

Network shares usually rely on folder indexing or a configured Everything server rather than local NTFS journal indexing. Confirm the UNC path, account permissions, rescan schedule, network connection, and NAS availability. A mapped drive may be invisible to a service running under another account.

7.5 Why does the query work in the GUI but fail from a script?

The shell may consume or alter quotation marks, pipes, exclamation points, or angle brackets before Everything receives the query. Test the expression in the GUI, then apply the correct escaping rules for PowerShell, Command Prompt, or the calling program.

7.6 Should I delete the Everything database?

Not as a first step. Verify syntax, filters, matching options, exclusions, indexed locations, service state, and account context first. If there is clear evidence of an inconsistent index, use the supported Force Rebuild option before considering more disruptive actions.