Everything Diacritics Search Not Matching: How to Fix It

When Everything finds ordinary filenames but fails to match accented or non-English characters, the problem is usually narrower than a complete search failure. The most likely causes are the Match Diacritics search option, an active search modifier, unexpected Unicode input, a filter that hides the result, or an index that does not include the file's location. Network shares, portable configurations, Everything Server connections, and command-line parameters can add another layer. The steps below isolate those possibilities without deleting the database or changing unrelated Windows settings.

Everything by voidtools is not Windows Search. Everything primarily searches its own filename index, while Windows Search uses Windows indexing components and can also index file contents and properties. Changing Windows Search settings generally will not fix accent matching inside Everything. Start by proving whether the issue is character matching, result filtering, or indexing.

1. Confirm the Symptom With a Small Safe Test

Create a controlled test before modifying settings. This establishes exactly what Everything is doing and gives you a known result against which to judge each fix.

1.1 Search for a known accented filename

In a local folder that Everything already searches, create a harmless empty text file with a distinctive name such as café-test-9472.txt. Copy the name directly from File Explorer and paste it into Everything. Avoid testing first with a deeply nested NAS file or a name you remember approximately.

Try these searches one at a time:

1. café-test-9472.txt
2. cafe-test-9472.txt
3. diacritics:café-test-9472.txt
4. nodiacritics:cafe-test-9472.txt

If the exact pasted accented name works, Everything has indexed the file and can process its Unicode characters. A failure involving only the unaccented spelling points to diacritic matching behavior, not an index failure. If neither spelling works, search only for 9472. If that also fails, investigate indexing, exclusions, filters, or the file's location before focusing on accents.

1.2 Check what success should look like

With diacritic matching enabled, an accented query is intended to distinguish diacritics. With diacritic matching disabled, searches can ignore those marks, allowing an unaccented query such as cafe to match a filename containing café. The explicit modifiers let you test either behavior without relying on the current global search option.

Stop changing settings as soon as the known file appears under the intended matching mode. At that point, Everything's core Unicode and diacritic behavior is working. Any remaining issue is likely specific to the original filename, query, filter, or indexed location.

2. Check Match Diacritics and Search Modifiers

The Match Diacritics option is the first setting to inspect for Everything diacritics search not matching. It controls whether accented and unaccented letters are treated as distinct during the search.

2.1 Set Match Diacritics for the result you want

Open the Search menu in Everything and locate Match Diacritics. If you want cafe to find café, turn Match Diacritics off. If you want cafe and café treated as different searches, turn it on.

Run the controlled test again after changing only this option. Success means the test file appears under the expected spelling. If it does, leave the option in the mode that matches your normal workflow and stop troubleshooting the index.

2.2 Override the option in a single query

Everything supports search modifiers that control diacritic behavior for an individual query:

• diacritics: requests diacritic-sensitive matching.
• nodiacritics: requests matching that ignores diacritic differences.

For example, use nodiacritics:cafe when you want the query to match both accented and unaccented forms. Use diacritics:café when the accent must be present. Testing both forms is useful when a saved search, bookmark, macro, or remembered search state may be overriding your expectation.

If the modifier works but the plain query does not, the index is probably healthy. Review the Match Diacritics option and any saved query text rather than forcing a rebuild.

2.3 Remove unrelated filters and syntax

Temporarily select the broadest Everything filter, commonly Everything, and reduce the query to the distinctive filename fragment. Remove regular expressions, whole-word matching, path restrictions, extension filters, Boolean operators, and macros while testing. An accent can appear to be the cause when the result is actually omitted by another search condition.

Check the status bar after each test. A nonzero result count indicates that the index returned matches, even if sorting or the current view makes the expected file difficult to spot. Zero results for the unique numeric fragment suggests that the file is absent from the active index or hidden by a filter or exclusion.

3. Verify the Exact Unicode Text Being Searched

Two strings can look identical on screen while being represented differently in Unicode. For example, an accented character may be stored as one precomposed character or as a base letter followed by a combining mark. Keyboard layouts, input methods, copied web text, remote sessions, and file-creation tools can affect the form entered.

3.1 Copy instead of retyping

Copy the filename directly from File Explorer, paste it into Everything, and search for a unique portion. Then type the same visible word manually. If the pasted query works and the typed query fails, Everything has the file, but your keyboard input is producing different characters or combining marks.

Confirm that the intended Windows keyboard layout is active. Also test with plain Windows applications such as Notepad rather than copying from a browser, PDF, terminal, or remote clipboard. Do not rename important files merely to make a test pass. A temporary file is enough to identify input differences safely.

3.2 Set realistic language and locale expectations

Match Diacritics is not a translation, transliteration, or language-aware synonym feature. Ignoring accents may help cafe match café, but it does not imply that one alphabet will match a transliteration in another alphabet. Likewise, changing the Windows display language or regional format should not be the first fix for a single filename-matching problem.

Success at this stage means the exact copied Unicode name is searchable and the chosen diacritic mode behaves consistently. If only text from one input method fails, correct that input source rather than rebuilding Everything.

4. Check Whether the File Is Actually Indexed

If the known accented name, its unaccented form, and a unique numeric fragment all return nothing, this is no longer just a Match Diacritics problem. Determine whether Everything indexes the file's volume or folder.

4.1 Distinguish local volumes from folder indexes

Everything can index supported local file systems efficiently, while network shares, mapped drives, NAS folders, and some non-NTFS locations generally require folder indexing or an Everything Server arrangement. Open Everything's Options and inspect the index pages for local volumes and folders. Confirm that the drive or folder containing the missing filename is included.

For a folder index, verify that the configured path still exists and is reachable under the account running Everything. Mapped drive letters can differ between standard and elevated sessions, services, scheduled tasks, and different user accounts. A UNC path can be more consistent than a mapped letter when account mappings vary.

4.2 Review exclusions and omitted results

Inspect the exclusion settings and remove only rules that could cover the test file's path or extension. Also check whether hidden, system, or other result-omission settings are active. Do not broadly remove security-related exclusions or expose private folders simply to test search behavior.

A useful isolation test is to place the temporary accented file in a known indexed local folder. If it appears there but an equivalent file on the NAS does not, diacritic matching is functioning. Troubleshoot the NAS folder index, connection, credentials, or update schedule instead.

4.3 Check the service and account context

The Everything service can support indexing and access to local volumes without requiring the user interface to run elevated. If local results are broadly missing, inspect the service configuration and confirm that the expected Everything service is running. Restarting the application or the service may be reasonable after a configuration change, but it should not replace checking the actual index settings.

For network locations, remember that a Windows service and an interactive user may have different credentials and mapped drives. Confirm access from the same account context used by the relevant Everything process. Success means searching the unique numeric fragment returns the file regardless of whether the filename contains an accent.

5. Inspect Server, Command-Line, and Portable Settings

Power users may search through an Everything client connected to an Everything Server, launch Everything with custom parameters, or carry a portable configuration between computers. In those cases, the visible interface may not be using the index or settings you expect.

5.1 Confirm the active server and data source

If the client uses an Everything Server connection, confirm that it is connected to the intended host and that the server's index includes the relevant location. Test a unique unaccented filename from the same folder. If both accented and unaccented files are missing, the server index or share coverage is the likely cause.

Keep file-search servers limited to trusted networks and properly authenticated configurations. Do not expose a search service directly to the public internet as a troubleshooting shortcut. If a local Everything window finds the file but the server-connected client does not, stop changing local Match Diacritics settings and troubleshoot the server-side index or client query.

5.2 Test without custom launch options

Review shortcuts, scripts, scheduled tasks, and command-line wrappers that start Everything. Custom parameters can select a different configuration, database, instance, server, or search. Launch the normal executable directly for comparison, preserving the existing configuration.

If you use the command-line interface, run the same simple query in the graphical application. Command shells also have quoting and character-encoding considerations. A query that works in the GUI but not through a script points to argument handling, shell input, or the selected instance rather than filename indexing.

5.3 Check portable configuration persistence

A portable copy may store settings beside its executable, while another installation or instance uses a different profile. Confirm which executable is running and whether changes to Match Diacritics persist after a normal restart. Avoid running several instances during the controlled test unless separate instances are intentional.

Success means the same query returns the same known file after reopening the intended portable or installed instance. If settings revert, investigate write permission to the portable configuration location or whether a shortcut starts a different copy.

6. Use Rebuilds and Diagnostics in the Right Order

A Force Rebuild can help when the index is stale or incomplete, but it is not the first fix for a search-option mismatch. Rebuilding will not correct a query typed with unexpected Unicode characters, an active filter, or a folder that was never configured for indexing.

6.1 Decide whether a rebuild is justified

Consider Force Rebuild only after confirming all of the following:

• The file's volume or folder is configured for indexing.
• The unique filename fragment does not appear.
• No filter, exclusion, or result-omission setting explains the absence.
• The location is available to the relevant account.
• The problem affects index freshness, not merely accented versus unaccented matching.

Use the Force Rebuild control in the relevant index options rather than manually deleting database files. Afterward, allow indexing to finish and watch the status information before retesting. Success means the unique fragment and exact accented filename now appear. Stop there rather than resetting additional options.

6.2 Use the Index Journal and debug information selectively

Where available in your Everything setup, the Index Journal and diagnostic or debug output can help establish whether a path was added, removed, excluded, or never observed. Capture only enough information to reproduce the issue, and protect logs that may contain sensitive filenames and paths.

Diagnostics are most useful after the minimal test has separated search matching from index coverage. If nodiacritics: fixes the query, logs are unnecessary. If a known file remains absent by its unique numeric fragment after the folder is confirmed in scope, index diagnostics become relevant.

7. Run a Clean Temporary Test Before Broad Changes

If the behavior remains inconsistent, test with a temporary clean configuration or separate test instance, following the supported configuration methods for your installation. Preserve your current settings and database. The goal is comparison, not destruction.

In the clean test, include only a safe local test folder, create one accented and one unaccented filename, and run exact, diacritics:, and nodiacritics: queries. Do not connect the test instance to an untrusted server or grant it unnecessary access.

If the clean test behaves correctly, the original profile likely contains a search state, filter, exclusion, index selection, command-line override, or persistence problem. Compare settings in small groups. If the clean test fails in exactly the same way, verify the input characters and document the shortest reproducible example before seeking support.

8. Quick Fix Checklist

1. Create café-test-9472.txt in a known indexed local folder.
2. Paste the exact filename into Everything.
3. Search for 9472 to prove the file is indexed.
4. Turn Match Diacritics off when cafe should match café.
5. Use nodiacritics:cafe to test accent-insensitive matching directly.
6. Use diacritics:café to test accent-sensitive matching directly.
7. Select the broad Everything filter and remove unrelated syntax.
8. Compare pasted text with keyboard-entered text.
9. Confirm the relevant volume, folder, share, or server is indexed.
10. Review exclusions, mapped-drive context, portable settings, and launch parameters.
11. Use Force Rebuild only when evidence indicates a stale or incomplete index.
12. Stop as soon as the controlled test produces the intended result.

9. Frequently Asked Questions

9.1 Why does cafe not find café in Everything?

Match Diacritics may be enabled, causing accented and unaccented letters to be distinguished. Turn it off or test nodiacritics:cafe. If that query finds the file, no index rebuild is needed.

9.2 Why does the exact accented filename still return no result?

Search for a unique plain fragment from the same filename. If that also fails, the file may not be indexed, may be excluded, or may reside in an unavailable folder, network share, or server index. If the plain fragment works, copy the exact filename from File Explorer to rule out keyboard or Unicode input differences.

9.3 Does changing Windows Search fix Everything results missing?

Usually not. Everything and Windows Search maintain different search systems. For this symptom, inspect Everything's Match Diacritics setting, query modifiers, filters, and index configuration. Windows permissions and network access can still matter because Everything must be able to index or query the relevant location.

9.4 Should I force rebuild the Everything index?

Only when the file is missing even by a unique unaccented fragment and you have confirmed that its location belongs in the index. A rebuild is unnecessary when nodiacritics: immediately fixes the query.

9.5 Why do accented searches work locally but fail on my NAS?

The local volume and NAS may be supplied by different indexes. Confirm that the NAS share is configured as a folder index or is available through the intended Everything Server, and verify credentials under the account context doing the indexing. If unaccented files from the same NAS folder are also absent, this is a coverage or connectivity problem rather than a diacritic problem.

9.6 Why does the query work in the GUI but not in a script?

The script may pass different Unicode text, use a different Everything instance, or mishandle quoting and command-line arguments. Compare the exact query, executable path, instance, and server selection. Copying the query into the GUI is a useful dividing test.