Everything Whole Word Match Hiding Results: How to Fix It

When valid files disappear from voidtools Everything, the index is not always the problem. A common cause is the Match Whole Word search option, which changes how Everything interprets filename boundaries. A partial filename that normally works may suddenly return no results, even though the file remains indexed and accessible. Filters, saved search state, command-line parameters, portable configuration, exclusions, network indexing, and account context can create similar symptoms. The safest approach is to confirm whole-word matching first, then investigate indexing or Windows only if a controlled test shows that the option is not responsible.

1. Confirm the Symptom With a Small Safe Test

Before changing services, rebuilding indexes, or editing configuration files, run a controlled filename test. This separates a search-matching issue from a genuine indexing problem.

1.1 Test a known partial filename

Choose a file that you can already see in File Explorer and whose full name you know. Suppose the file is named quarterly-report-2025.xlsx. Search for several variations in Everything:

1. quarterly-report-2025.xlsx, which tests the complete filename
2. quarterly, which tests a likely complete word
3. quart, which tests a partial word
4. report, which tests text surrounded by punctuation

If the complete filename and complete words appear but quart does not, whole-word matching is a strong suspect. The file is probably indexed, but the active search rule is rejecting the partial token.

Success means the full filename appears and the result changes predictably when you switch between complete and partial words. At that point, do not rebuild the index. Continue directly to the Search menu and modifier checks.

1.2 Compare wholeword and nowholeword directly

Everything supports search modifiers that can override the current matching mode for an individual query. Test the same known filename with these searches:

• wholeword:quart
• nowholeword:quart
• wholeword:quarterly
• nowholeword:quarterly

If nowholeword:quart restores the file while wholeword:quart hides it, you have confirmed an Everything whole word match hiding results issue. The index, file permissions, and storage location are unlikely to be the immediate cause because the same indexed record appears when only the matching rule changes.

Stop changing unrelated settings once this comparison confirms the cause. Disable Match Whole Word or use nowholeword: only for searches where partial matching is required.

2. Check the Search Option and Related Query State

Whole-word matching operates at query time. It does not normally remove files from the database. This distinction is important because rebuilding a healthy index cannot correct a query that intentionally excludes partial words.

2.1 Turn off Match Whole Word in the Search menu

Open the Search menu in Everything and inspect Match Whole Word. If it is checked, select it to turn it off. Clear the search box, type the partial filename again, and compare the result.

Also inspect the status bar. Depending on the Everything interface and configuration, the status area can display indicators for active search modes such as whole-word matching, case matching, path matching, or regular expressions. An unexpected whole-word indicator is evidence that the option is still active, even if the query itself contains no visible modifier.

Success means the partial filename immediately returns the expected files and the whole-word indicator is no longer active. Stop troubleshooting when that happens. No service restart, Force Rebuild, permission change, or antivirus exception should be necessary.

2.2 Reset persistent search options

Everything can preserve search state across searches or launches, depending on its settings and how it was started. If Match Whole Word keeps returning, clear the search box and review every enabled item in the Search menu. Disable Match Whole Word, Match Case, Match Path, and regular expression mode unless they are intentionally needed. Some releases or configurations may provide a reset command in the Search menu. If available, use it to return search options to their normal state, then retest a simple partial filename.

Do not confuse clearing the query text with resetting search options. Deleting text from the search box may leave Match Whole Word enabled. Likewise, changing a filter does not necessarily reset matching modes.

2.3 Check modifiers, bookmarks, macros, and command-line options

A query can enable whole-word matching even when the global menu option is off. Look for wholeword: in the search box, a bookmark, a saved search, a filter macro, or a script that constructs Everything queries. Replace it with nowholeword: for a diagnostic test or remove the modifier when partial matching is desired.

If Everything is launched by a shortcut, batch file, scheduled task, launcher, or portable-app menu, inspect the startup command. A command-line option or preloaded search can reproduce the same behavior on every launch. Test by opening Everything normally from its executable without supplying a search expression.

Success means a plain launch and plain partial query find the file. If only a particular shortcut, bookmark, or automation path fails, repair that entry rather than changing the index.

2.4 Understand hyphens and underscores

Whole-word matching depends on boundaries, not merely on whether text looks visually separate. Everything defines words around alphanumeric sequences, so punctuation can create boundaries. Hyphens and underscores can therefore allow a complete token between separators to match even while a fragment inside that token remains hidden.

For example, with a filename such as client_report-final.txt, a search for report can behave as a complete token because punctuation separates it from neighboring text. A search for repo remains a partial token and can disappear when Match Whole Word is enabled. Hyphens and underscores are visually different, but both should be tested with the exact filename and Everything build in use rather than treated as proof of an indexing failure.

Create harmless test files such as alpha-beta.txt, alpha_beta.txt, and alphabet.txt. Compare searches for alpha and alph with wholeword: and nowholeword:. This reveals the boundary behavior without modifying important data.

3. Rule Out Filters, Omissions, and Index Configuration

If nowholeword: does not restore the expected result, the symptom is no longer explained by whole-word matching alone. Check other query and index controls methodically.

3.1 Return the filter to Everything

Use the filter selector to choose the general Everything filter. A Pictures, Documents, Audio, Executables, or custom filter can hide a valid file based on its extension, path, or custom search expression.

Clear the search box after selecting the Everything filter, then search for the exact filename. If the result returns, inspect the previous filter rather than rebuilding the database. A custom filter may also contain wholeword: or another restrictive expression.

3.2 Check exclusions and omitted results

Open the index and exclusion-related Options pages. Confirm that the file's parent folder, drive, extension, or filename pattern is not excluded. Also check whether results have been deliberately omitted or hidden through an omission feature, filter, bookmark, or search expression.

A useful comparison is to search for the exact full path or a distinctive parent-folder name. If neighboring files from the same folder are also absent, an exclusion or missing index location is more likely than whole-word matching.

Success means removing the relevant exclusion or omission causes the known file to appear after Everything processes the change. Stop once the file appears consistently in a plain exact-name and partial-name test.

3.3 Verify NTFS, ReFS, and folder indexes

Everything commonly obtains fast local results by indexing supported file-system metadata. Other locations, including some removable media, NAS paths, mapped drives, and shares, may need to be added as folder indexes or supplied by an Everything server.

Open the Indexes section of Options and verify that the relevant local volume or folder is included. If the missing file is on a NAS, do not assume a mapped drive letter makes it part of the local NTFS index. Confirm that the share is configured through the intended folder-index or server method and that the path is currently reachable.

If the entire folder or volume is absent, correct that scope first. If other files in the same folder appear and only partial tokens fail, return to the whole-word and query-state checks.

4. Check Service, Server, and Windows Context Only When Relevant

Windows-level troubleshooting becomes relevant when the exact filename is missing, an entire location is absent, or results differ between accounts. It is usually unnecessary when nowholeword: immediately fixes the search.

4.1 Verify the Everything service state

If your installation uses the Everything service, check its status through Everything's Options and Windows Services. A stopped service can prevent expected local indexing behavior, particularly for standard-user sessions that rely on the service for file-system access.

Restarting a stopped service can be a reasonable test, but do not repeatedly reinstall components when files are already visible with a different query modifier. Success means new and existing files on the configured volume appear under the same user without requiring elevated launch behavior.

4.2 Compare account and startup context

Everything started as an administrator can use different settings or configuration storage from an ordinary-user or portable launch. Similarly, multiple copies can read different INI files. Confirm which executable is running, whether it is installed or portable, and which configuration file it uses.

Close duplicate instances and launch the intended copy directly. If the problem occurs only from a startup shortcut, inspect that shortcut's working directory, arguments, and elevation setting. Portable users should verify that the configuration directory is writable so a corrected Match Whole Word setting can persist.

4.3 Test network shares and Everything servers

For mapped drives and UNC shares, confirm that the same Windows account can open the path in File Explorer. A mapping created under one account or elevation level may not exist in another. If an Everything server supplies the results, confirm that the client is querying the expected server and that the server includes the relevant scope.

Firewall rules may matter when a client cannot connect to a private Everything server, but they do not explain a local query that changes solely between wholeword: and nowholeword:. Do not expose an Everything server directly to the public internet as a troubleshooting shortcut. Keep access limited to trusted networks or an appropriately secured private connection.

4.4 Treat antivirus interference cautiously

Security software can occasionally affect application startup, configuration writes, or network communication, but it is not the first suspect for word-boundary behavior. Review the security product's event or quarantine history instead of disabling protection permanently. If a controlled test is necessary, follow the vendor's safe procedure and restore protection immediately afterward.

5. Use Diagnostics Without Destroying Useful State

Diagnostics should answer a specific question. Start with visible search state and narrow syntax tests before using heavier index operations.

5.1 Read the status bar and result counts

Compare the result count for the same token under wholeword: and nowholeword:. Watch the status bar for active mode indicators and confirm that a restrictive filter is not selected. A large change in count with only the modifier altered is strong evidence of query behavior, not index corruption.

5.2 Use exact syntax comparisons

Test one variable at a time:

• Exact filename with no modifier
• Partial filename with no modifier
• Partial filename with wholeword:
• Partial filename with nowholeword:
• Exact filename under the Everything filter
• Full path or parent-folder token

Record which query first makes the result disappear. This is especially useful for sysadmins comparing user profiles, portable deployments, server clients, or scripted searches.

5.3 Inspect the Index Journal and debug information

If a newly created or renamed file never appears even by its exact name, inspect Everything's Index Journal or available diagnostics to determine whether the change reached the index. Debug logging can also help identify startup arguments, configuration loading, service connection problems, and folder-index failures.

Enable detailed logging only long enough to reproduce the issue, because logs can grow and may contain filenames or paths. Store and share them as potentially sensitive operational data.

5.4 Use Force Rebuild only after safer checks

A Force Rebuild can be appropriate when exact-name searches fail, the index is demonstrably stale, and the configured volume or folder should contain the file. It is not an appropriate first fix when only partial-word searches fail.

Before rebuilding, verify the search mode, filter, exclusions, indexed scope, service state, and file location. If you do rebuild, wait for indexing to complete and retest the known filename. Do not delete database files manually before trying the supported rebuild function and preserving any configuration you may need.

6. Run a Clean Temporary Test Before Broad Changes

If the active configuration remains confusing, run a separate temporary test with a clean profile. The goal is to isolate saved options without destroying your normal settings.

1. Close or leave the regular instance unchanged.
2. Use a separate trusted copy of Everything in an isolated temporary folder or a supported clean configuration method.
3. Do not import bookmarks, filters, or the existing INI file.
4. Index or add only a harmless test folder if the clean instance requires its own scope.
5. Create files such as alpha-beta.txt, alpha_beta.txt, and alphabet.txt.
6. Compare wholeword:alpha, wholeword:alph, and nowholeword:alph.

If the clean profile behaves correctly, the original profile probably contains a persistent search option, custom filter, macro, bookmark, command-line query, exclusion, or portable configuration issue. Compare settings gradually rather than replacing the working profile immediately.

If both profiles fail to show the exact filename, investigate index scope, folder accessibility, service operation, or file-system support. If both show the exact filename but hide only the partial token under wholeword:, that is expected matching behavior rather than a damaged installation.

7. Quick Fix Checklist

• Search for a known file by its complete filename.
• Test a partial token with wholeword: and nowholeword:.
• Open Search and turn off Match Whole Word.
• Check the status bar for an active whole-word indicator.
• Reset unintended Search menu options and regular expression mode.
• Select the Everything filter instead of a restrictive custom filter.
• Inspect bookmarks, macros, shortcuts, and scripts for wholeword:.
• Test hyphenated and underscored names with complete and partial tokens.
• Check exclusions only if exact-name searches also fail.
• Verify folder indexes or server scope for NAS and network files.
• Confirm the intended installed or portable configuration is running.
• Use Force Rebuild only when the exact filename is genuinely absent from a configured index.

The fastest stopping rule is simple: if disabling Match Whole Word or adding nowholeword: restores the expected partial-name result, the problem is fixed. Avoid changing services, permissions, firewalls, or databases after that point.

8. Frequently Asked Questions

8.1 Why does Everything find the full filename but not part of it?

Match Whole Word is probably enabled, either through the Search menu or a wholeword: modifier. The indexed record still exists, but the partial text does not satisfy the active word-boundary rule. Disable the option or test with nowholeword:.

8.2 Does Match Whole Word remove files from the Everything index?

No. It changes which indexed records satisfy the current query. If changing only the whole-word mode makes the file reappear, rebuilding the index is unnecessary.

8.3 Why do hyphenated or underscored filenames behave differently from longer words?

Punctuation creates visible and logical boundaries within filenames. A complete token next to a hyphen or underscore may satisfy whole-word matching, while a fragment inside an alphanumeric sequence does not. Use controlled filenames and compare wholeword: with nowholeword: to verify the exact boundary behavior.

8.4 Why is Match Whole Word enabled again after restarting?

A saved configuration, portable INI file, bookmark, startup shortcut, command-line expression, custom filter, or launcher may be restoring it. Confirm which executable and profile are running, then inspect the Search menu and startup arguments.

8.5 Is Everything the same as Windows Search?

No. voidtools Everything is a separate filename-search application with its own index, service, query syntax, filters, and configuration. Changing Windows Search indexing options will not normally fix an Everything whole-word query. Troubleshoot the Everything Search menu and index scope first.

8.6 When should I rebuild the Everything index?

Consider a supported Force Rebuild only when the exact filename is missing, the correct volume or folder is configured, exclusions do not explain the omission, and the index appears stale. Do not rebuild merely because a partial token disappears while Match Whole Word is active.