Everything Case Sensitive Search Problems: How to Fix It

Everything case sensitive search problems usually appear in one of two ways: a search misses a file whose capitalization differs from the query, or a search unexpectedly matches every capitalization. In voidtools Everything, this behavior is normally controlled by the Match Case search option, the case: or nocase: search modifier, a saved filter, or a command-line setting. If only certain disks, folders, or network shares are affected, the more likely cause is an indexing, exclusion, permission, service, or account-context problem rather than case matching itself.

The safest approach is to reproduce the symptom with a small set of mixed-case filenames, verify the active search mode, and stop as soon as the expected files appear. Do not rebuild the index or reset unrelated settings until you know whether the problem is matching, indexing, or access.

1. Confirm the Symptom With a Small Safe Test

Before changing Everything, determine whether capitalization is genuinely controlling the result. A missing file can resemble a case-sensitive search problem even when the file is not indexed at all.

1.1 Create mixed-case test files

In a local folder that Everything normally indexes, create three empty text files with clearly different names:

• CaseTestAlpha.txt
• casetestbeta.txt
• CASETESTGAMMA.txt

Wait briefly for Everything to notice the files, then search for casetest. With case matching disabled, all three filenames should appear. With Match Case enabled, only names containing the exact capitalization entered in the query should appear.

Windows file systems commonly preserve a filename's capitalization while treating names as case-insensitive in ordinary Windows applications. Everything can still compare the capitalization of the displayed filename when Match Case is active. This is a search comparison rule, not evidence that Windows has created three interchangeable files with the same spelling.

1.2 Separate matching problems from indexing problems

Search for the exact full filename of one test file, including its extension. Then search for part of its path. If the file never appears under any capitalization, changing Match Case will not solve the problem. Check whether the folder is indexed, excluded, accessible, or omitted from results.

If the file appears with nocase: but disappears with case:, indexing is working and case comparison is the relevant issue. Stop investigating drives, services, and permissions unless other files remain missing.

2. Check Match Case and Search Modifiers First

The fastest Everything case sensitive search problems fix is usually to correct the active search option or remove an inline modifier. These controls can affect the same query in different ways, so inspect both.

2.1 Toggle Match Case deliberately

Open Everything's Search menu and locate Match Case. If it is checked, uncheck it and repeat the mixed-case test. If your goal is to find only an exact capitalization, enable it instead.

Review the status bar after toggling the option. Depending on the Everything build and interface configuration, the status bar can show active search modes or other clues about the current search. Also inspect the Search menu directly, because a hidden status bar should not be treated as proof that no option is enabled.

Success means that a lowercase query finds all three mixed-case test files when Match Case is off, while an exact-capitalization query narrows the results when Match Case is on. Once that behavior is consistent, stop changing global options.

2.2 Test case: and nocase: explicitly

Everything supports search modifiers that let a query control matching without relying only on the current menu state. Try these searches separately:

• nocase:casetest to request case-insensitive matching
• case:CaseTest to request case-sensitive matching
• case:casetest to verify that differently capitalized names are excluded

If nocase: restores the missing results, an active case option, saved search, filter, macro, or launch configuration is probably influencing the original query. If neither modifier finds a known indexed file, the issue is not limited to case matching.

When testing, type a plain filename term. Remove regular expressions, Boolean operators, quotes, wildcards, size conditions, date conditions, and path restrictions. A complicated expression can hide the effect you are trying to measure.

2.3 Check filters and saved searches

A selected filter can add conditions to a query. Switch to the broadest default filter, commonly named Everything, and clear the search box completely before entering the test term again. If you use custom filters, inspect their search expressions for case:, nocase:, macros, path limits, or regular-expression conditions.

Also check bookmarks, saved searches, keyboard shortcuts, and scripts that insert a prepared query. Success means the same plain query behaves predictably when entered manually with the default filter.

2.4 Reset search options without resetting Everything

A safe reset does not require deleting the database or configuration. Clear the search field, select the default filter, and turn off temporary Search-menu modes such as Match Case, Match Whole Word, Match Path, and Regex unless they are needed. Then test nocase:casetest.

This isolates the case behavior while preserving indexes, exclusions, network settings, and other preferences. Avoid a full configuration reset until a temporary clean-profile test proves that the existing profile is responsible.

3. Review ASCII Comparison and Filename Details

Case behavior can be affected by the characters in the filename and by comparison-related settings. A basic English alphabet test is useful because it separates ordinary ASCII case matching from Unicode, diacritic, normalization, or locale-related behavior.

3.1 Compare ASCII and non-ASCII tests

Start with filenames containing only A to Z, a to z, digits, and a simple extension. If those work but names containing accented letters or other scripts behave differently, review the search and comparison options available in your installed Everything build.

Some Everything configurations expose performance or comparison settings related to fast ASCII searching. The exact label and location can vary, so do not copy a setting from an unrelated version blindly. Record the current value before changing it, change only that setting, and rerun the same test.

Success means the ASCII test follows Match Case consistently. If only non-ASCII filenames remain problematic, keep the investigation focused on character handling rather than rebuilding every index.

3.2 Verify the actual stored filename

Do not rely on capitalization shown in a shortcut, application title, recent-file list, or NAS web interface. Open the containing folder in File Explorer and compare the exact stored name with the Everything result. Rename the test file to a temporary, clearly different name if Windows or a synchronization tool appears to retain an old display value.

On a case-sensitive directory or a non-Windows file system, filenames that differ only by capitalization may be distinct. In that situation, confirm the names at the storage source and test both exact spellings. Do not assume every network server applies normal Windows case rules.

4. Check the Index, Exclusions, and Result Omissions

If case modifiers do not find the file, determine whether Everything knows the file exists. Everything is not Windows Search. Everything builds and queries its own indexes, with particularly fast handling of supported local NTFS volumes. Windows Search settings and its content index are therefore not the primary controls for an Everything filename result.

4.1 Confirm that the location is indexed

Open Everything's Options and inspect the relevant index pages. For a local volume, verify that the intended volume is included. For a manually indexed directory, confirm the exact folder path. For a network location, look for the corresponding folder index or server-based configuration.

Search for the parent folder's exact name and browse nearby results. If nothing from the location appears, this is a coverage problem. If neighboring files appear but one file does not, investigate exclusions, permissions, update timing, or the file's actual name.

4.2 Inspect exclusions and omitted results

Review exclusion settings for excluded volumes, folders, files, extensions, wildcards, or attributes. A broad wildcard can unintentionally hide a mixed-case filename, although the exclusion itself may not be case-related.

Also inspect any settings or commands that omit results from the current result list. Clear custom filters and result-removal actions before testing. Success means the known file appears with a broad, case-insensitive query after the relevant exclusion or omission is corrected.

4.3 Check whether the index is updating

If newly created test files do not appear, the Everything index may not be updating. Check the status bar and index information in Options for signs that scanning or updating is still in progress. On supported local volumes, verify that the volume is available and that the expected index update mechanism is functioning. For a folder index, verify its rescan behavior and schedule.

Use a force rebuild only after confirming that the location should be indexed and safer checks have failed. A rebuild can be appropriate for a demonstrably stale or inconsistent index, but it is not the first response to a Match Case option. After rebuilding, success means both existing and newly created test files appear without requiring capitalization tricks.

5. Check Services, Accounts, Shares, and Startup Context

When Everything search is not working only for certain locations, compare how the application was launched and which account can access those locations.

5.1 Verify the Everything service state

If your configuration uses the Everything service, confirm that it is installed as intended and running. Restarting the application is not always the same as restarting its service. However, do not repeatedly reinstall the service if local results are already updating and only Match Case is wrong.

A service problem is more plausible when an indexed local volume disappears, updates stop, or Everything reports an access-related issue. Success means the volume remains available and a newly created test file is detected.

5.2 Compare elevated and normal launches

An application launched under a different account or elevation context can see different mapped drives and network credentials. If a mapped drive appears in one session but not another, test the underlying UNC path, such as \\server\share, using the account that normally runs Everything.

Do not expose an Everything server or file-search service directly to the public internet as a troubleshooting shortcut. Keep server access limited to trusted networks and use appropriate authentication, firewall rules, or a secure remote-access layer.

5.3 Check network shares and NAS behavior

Everything generally needs a folder index, an Everything server connection, or another configured method to search files on a network share. A Windows mapped drive does not automatically make remote files behave like a locally indexed NTFS volume.

Confirm that the share is online, the current account can list the affected directory, and saved credentials have not expired. Check the NAS file system's case behavior and whether two differently capitalized names can coexist. If local mixed-case tests work but NAS tests fail, keep changes limited to the network indexing or server configuration.

5.4 Treat firewall and antivirus changes conservatively

If a remote Everything server cannot be reached, verify its configured address, port, allowed network scope, and the firewall rule for that specific connection. Do not disable the firewall permanently. Likewise, review antivirus or endpoint-security logs for an actual blocked executable, configuration file, or network connection before creating a narrow exception.

Security software is unlikely to cause only a capitalization mismatch. Investigate it when indexing, startup, configuration writes, or server communication is demonstrably blocked.

6. Inspect Command-Line and Portable Configurations

Power users often launch Everything through scripts, shortcuts, scheduled tasks, or portable folders. These launch paths can load different settings or insert search text that changes case behavior.

6.1 Test a direct interactive launch

Close extra Everything windows and start the expected executable directly. Enter the plain mixed-case test manually. Then inspect shortcut targets, batch files, PowerShell scripts, Everything command-line interface calls, and scheduled tasks for search expressions containing case: or nocase:.

If direct use works but a script fails, the script's query or launch context is responsible. Stop changing the GUI configuration and correct the narrow automation issue.

6.2 Confirm which portable profile is active

A portable copy may read configuration from its own directory, while another installation uses settings associated with a different location or Windows account. Confirm the executable path and configuration files being used. Ensure the portable directory is writable if settings are expected to persist.

Startup behavior is a clue: if Match Case returns after every restart, a shortcut, saved state, read-only configuration, profile-management tool, or portable launcher may be restoring it. Change the option, close Everything normally, reopen it, and check whether the option persisted.

7. Use Diagnostics Without Making Broad Changes

Diagnostics are most valuable after a controlled test identifies the failing layer. Capture evidence before rebuilding indexes or replacing configuration files.

7.1 Read the status bar and index information

Use the status bar to compare result counts and identify active search behavior. Review the Options pages for indexed volumes, folder indexes, exclusions, and relevant search settings. The goal is to answer three questions:

1. Does Everything index the location?
2. Does a case-insensitive query find the file?
3. Does an exact-case query include only the intended filename?

If all three answers are yes, the system is working. Further changes add risk without improving the result.

7.2 Use debug logging for reproducible failures

If the problem survives a simple test, use Everything's supported diagnostic or debug facilities for your installed build. Reproduce the issue once, record the exact query and file path, and look for index, database, service, connection, or configuration errors. Avoid leaving verbose logging enabled indefinitely when it is not needed.

For local NTFS update issues, journal-related diagnostics can help determine whether changes are being detected. Journal investigation is useful when new files fail to appear, not when nocase: immediately solves the query.

7.3 Rebuild only when evidence points to the index

Use Force Rebuild when known files on an included location remain absent, updates are clearly stale, or diagnostics indicate index inconsistency. Record important settings first and allow the rebuild to finish before judging results.

Do not delete the Everything database manually as an opening step. A controlled rebuild is safer and easier to interpret. If the rebuilt index finds the test files, stop. If it does not, return to location coverage, permissions, exclusions, and file-system support.

8. Run a Clean Temporary Test

When the normal profile remains confusing, run a temporary clean test rather than changing many production settings. Back up or record the current configuration, then use a separate temporary configuration or portable test copy according to the official documentation for your build.

Index only a small local test location if the test mode permits it. Create the three mixed-case filenames, select the default filter, and compare plain, case:, and nocase: queries. Do not connect the temporary instance to sensitive remote servers or import the old configuration before completing the test.

If the clean instance works, the cause is likely a setting, filter, macro, startup command, or profile persistence issue in the original environment. Compare settings in small groups. If the clean instance fails on the same location, investigate the location, file system, permissions, or build-specific behavior instead.

9. Quick Fix Checklist

1. Create three harmless files with uppercase, lowercase, and mixed-case names.
2. Clear the query and select the default Everything filter.
3. Turn off Match Case and confirm a lowercase query finds all test files.
4. Test nocase: and case: explicitly.
5. Check the Search menu and status bar for active modes.
6. Remove Regex, Match Path, Match Whole Word, and unrelated query conditions.
7. Verify the affected volume, folder, share, or server is indexed.
8. Review exclusions and result omissions.
9. Confirm new files appear before considering an index rebuild.
10. Check service state, account context, and mapped-drive visibility when locations are missing.
11. Inspect shortcuts, scripts, command-line queries, and portable-profile persistence.
12. Use a temporary clean profile before resetting the main configuration.

Stop at the first point where plain searches, case:, and nocase: produce the expected results. Troubleshooting beyond that point can obscure the original cause.

10. Frequently Asked Questions

10.1 Why does Everything find FileName.txt when I search filename.txt?

Match Case is probably disabled, so Everything is performing a case-insensitive filename comparison. This is normal for broad searches. Enable Match Case or use case: when exact capitalization matters.

10.2 Why does Everything miss a file after I enable Match Case?

The query's capitalization must match the relevant filename text. Confirm the actual stored filename in File Explorer, simplify the query, and test with nocase:. If nocase: also fails, check indexing and exclusions.

10.3 Do case: and nocase: change the index?

No. They control how the query compares text; they do not add files to the index. If a file is absent from the index, neither modifier can make it appear.

10.4 Why are Everything results missing only from a NAS?

The share may require a folder index or Everything server configuration, and the current account must be able to access it. NAS file systems can also use different case rules. Test a local folder first, then verify the share path, credentials, indexing method, and server connection.

10.5 Should I rebuild the index to fix case matching?

Usually not. First disable Match Case, test nocase:, clear filters, and confirm that the file appears under some query. Rebuild only when files from an included location remain missing or the index is demonstrably stale.

10.6 How can I safely reset Everything search options?

Clear the search box, select the default filter, and disable temporary Search-menu modes. This resets the immediate search state without deleting indexes or configuration. If needed, use a temporary clean profile to test defaults before changing the primary setup.