Everything Search Box Autocomplete Not Working: How to Fix It

When Everything search box autocomplete is not working, the usual symptom is simple: you type part of a query you used before, but no previous searches appear. This is normally a search-history, privacy, configuration, write-permission, or profile issue. It is usually not an indexing problem. Everything by voidtools maintains its own filename index and settings, so Windows Search troubleshooting steps rarely fix this particular symptom. Start with the small test below, then stop as soon as suggestions survive a clean restart.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, separate autocomplete failure from missing search results. Autocomplete suggests previous queries in the search box. Search results are the matching files displayed below it. Those features can fail independently.

1.1 Test whether history is being recorded

1. Open Everything normally.
2. Click the search box and enter a distinctive test query, such as autocomplete-test-4821.
3. Press Enter and then replace the query with something else.
4. Start typing the first few characters of the distinctive query.
5. Use the search-box drop-down or the relevant history command if suggestions do not appear automatically.
6. Exit Everything cleanly through File > Exit, reopen it, and repeat the test.

The query does not need to match a real file. This test checks whether Everything records and retrieves search text, not whether its index contains a matching filename.

Success means the distinctive query is offered while the program is running and remains available after a clean exit and restart. If that happens, stop changing settings. The original missing searches may have been cleared previously, expired under the retention policy, or stored by a different Everything instance.

1.2 Identify the failure stage

• No suggestion during the same session: history may be disabled, suggestions may not be displayed, or the current UI mode may suppress them.
• Suggestions work until restart: Everything probably cannot save history, is using a temporary configuration, or is being terminated without a clean exit.
• Suggestions exist but results are missing: autocomplete works; investigate indexing, filters, exclusions, and storage availability separately.
• Only one shortcut loses history: that shortcut may launch another instance, account context, portable copy, or configuration location.

2. Check the Everything History and Search Settings

Open Tools > Options and find the History page. Labels can differ slightly between Everything editions and builds, so look for settings that enable search history, control retention, or always suggest previous searches.

2.1 Enable search history

Make sure search history is enabled. If there is a retention period, confirm it is not set so low that entries disappear before you expect to reuse them. If your build offers an option similar to always suggesting search history, enable it when you want suggestions to appear as you type rather than only through a drop-down or history command.

Apply the change and repeat the distinctive-query test. After the suggestion appears, exit Everything cleanly and reopen it. If the query survives, the Everything search box autocomplete not working fix is complete.

2.2 Review privacy-related behavior

Search history can expose filenames, project names, client names, server paths, or other sensitive terms. Everything therefore allows users to disable or clear history. Review the History and privacy-related options for automatic clearing, restricted retention, or disabled recording.

Do not enable persistent history on a shared workstation without considering who can use the account. If policy requires history to remain disabled, the lack of autocomplete is expected behavior rather than a fault.

2.3 Check whether history was cleared

If someone used a clear-history command, old suggestions cannot normally be reconstructed from the filename index. The index knows filenames; it is not a backup of everything previously typed into the search box.

Create a new test query after confirming history is enabled. Success means new entries appear and persist. Do not rebuild the database merely to recover cleared searches because rebuilding the filename index does not recreate search history.

2.4 Rule out filters and search modes

A filter, case option, whole-word option, regex mode, or search syntax error can make results disappear, but these settings do not normally erase stored history. Set the filter to Everything, clear the search box, and test a simple filename fragment. If suggestions appear but matching files do not, move to result troubleshooting instead of repeatedly changing history options.

3. Verify the Settings and History Storage Location

Everything can use an installed configuration, a portable configuration, multiple named instances, or different settings under different Windows accounts. Autocomplete may appear inconsistent when each launch reads a different history store.

3.1 Check installed and portable configurations

An installed copy commonly stores per-user data in the current Windows profile. A portable copy may keep settings and related data beside the executable, depending on how it is configured and where it is launched. The exact filenames and locations can vary by edition and configuration, so use Everything's Options pages and current documentation to identify the active settings location instead of assuming that the first Everything folder you find is the live one.

Portable applications should not be placed in a folder where the current user cannot write, such as a protected application directory, a read-only network location, or read-only removable media. Move a test copy to a normal user-writable folder if necessary. Do not overwrite the existing copy until the test succeeds.

Success means the same test query remains after a clean restart from the same executable. At that point, keep using that configuration or correct the original folder's permissions.

3.2 Test history file write permissions safely

If suggestions work only until Everything closes, inspect the folder that contains the active user settings or portable data. The current Windows account needs permission to create and update its history data there.

1. Close Everything through File > Exit.
2. Open the relevant data folder in File Explorer.
3. Confirm the folder is not read-only storage and that your account can create a harmless temporary text file.
4. Delete the temporary file after the test.
5. Reopen Everything, create the distinctive query, exit cleanly, and test again.

Do not take ownership of system folders or grant broad permissions to all users merely to fix autocomplete. A safer solution is to use the normal per-user data location or place a portable copy in a folder owned by the intended user.

3.3 Compare Windows account and elevation context

Running Everything under another Windows account can produce a separate history. Running one shortcut normally and another with different credentials can also make the program appear to forget suggestions. Compare the shortcut's properties, the executable path, and the account used to launch it.

Avoid routinely running the user interface as administrator solely to preserve history. Correct the data location or permissions instead. Success means both launches use the intended profile and display the same newly created history entries.

4. Check Startup, Security, and Network Context

Windows startup behavior and endpoint controls matter mainly when they prevent a clean save or redirect the application to another profile. Network indexing issues generally affect results, not the search-box history itself.

4.1 Make sure Everything exits cleanly

If Windows shuts down, a script kills the process, or a portable drive is removed while Everything is running, recent history may not be written. Test with File > Exit, wait for the process to close, and then reopen the application.

If that works, review logoff scripts, application launchers, portable-app managers, and cleanup utilities that terminate Everything or erase application data. Configure a narrow exception only when organizational policy permits it. Do not disable antivirus or endpoint protection permanently.

4.2 Inspect shortcuts and command-line launches

Power users and sysadmins often launch Everything through scripts, scheduled tasks, custom toolbar buttons, or portable-app menus. Compare a failing launch with a working direct launch. Look for a different executable path, named instance, configuration choice, working directory, or option that changes how settings are loaded.

Temporarily launch the intended executable directly without custom arguments. Create and save a test query. If autocomplete now persists, add the original arguments back one at a time until the behavior changes.

4.3 Understand mapped drives, shares, and servers

Mapped drives, NAS shares, folder indexes, ETP connections, and Everything server features determine which remote filenames are searchable. They do not normally provide the local GUI's previous-search history. A disconnected share can therefore cause Everything results missing while autocomplete continues to work.

If remote results are missing, verify that the share is available in the same account context, the folder index is configured, and the remote server connection is reachable. Check firewall rules narrowly for the required private-network connection. Never expose an Everything server or file-search service directly to the public internet without appropriate authentication, network controls, and a deliberate security design.

5. Use Diagnostics Without Destroying Useful Data

Diagnostics should answer one question at a time. Avoid deleting databases, settings, and history together because that removes evidence and makes the actual cause difficult to identify.

5.1 Read the status bar and Options pages

The status bar can show whether a query has matches and whether Everything is busy. The Indexes, Folders, NTFS, ReFS, Exclude, and related Options pages explain why results may be absent. They are useful when autocomplete works but the expected files do not appear.

Check these result-related causes:

• The wrong filter is active.
• A folder or file pattern is excluded.
• A folder index points to an unavailable location.
• The application is running under an account that cannot access a share.
• The expected volume or file-system source is not included in the active index configuration.
• A search option or advanced syntax narrows the query unexpectedly.

Once a simple query produces results, stop changing index settings. Result indexing and history persistence are separate troubleshooting tracks.

5.2 Use Force Rebuild only for index symptoms

A forced rebuild can help when Everything's filename database is incomplete or inconsistent. It is not a normal remedy for autocomplete history. Before rebuilding, confirm that actual filenames known to exist are absent even with the Everything filter and a simple query.

If only previous searches are missing, leave the index alone. This preserves a working database and avoids unnecessary scanning or journal processing.

5.3 Use logs and journal information selectively

Debug logging may reveal configuration paths, instance names, access failures, or startup arguments. Index Journal information is more relevant to indexing changes than to search-history suggestions. Enable diagnostics only long enough to reproduce the issue, then review them for failed writes or an unexpected data location.

Logs can contain filenames, paths, searches, and server details. Store and share them carefully, redact sensitive data, and disable verbose logging after testing.

5.4 Test simple search syntax

Turn off regex and enter an ordinary filename fragment without operators. If the status bar reports results but no historical suggestion appears, the index is functioning and the problem remains in history recording or presentation. If the historical query appears but has zero results, autocomplete is functioning and the query or index needs separate attention.

6. Run a Clean Temporary Test

A clean test determines whether the cause is the existing profile or the wider Windows environment. It should not destroy the current settings.

1. Exit the current Everything instance cleanly.
2. Back up the relevant settings and history data without deleting the originals.
3. Use a fresh official portable copy in a new, user-writable local folder, or use an officially supported clean configuration method.
4. Do not connect servers, import settings, or add custom command-line arguments yet.
5. Enable search history if necessary and enter the distinctive test query.
6. Exit cleanly, reopen the same copy, and check autocomplete.

If the clean copy remembers the query, Windows can save history and the original profile, launch command, or storage location is the likely cause. Compare settings gradually rather than copying the entire old profile into the clean test.

If the clean copy also forgets history, check account controls, folder write access, security logs, profile-cleanup software, and shutdown behavior. Stop once a clean restart preserves the test query. Further changes introduce risk without adding useful evidence.

7. Quick Fix Checklist

• Confirm that the problem is missing suggestions, not merely missing filename results.
• Enable search history in Tools > Options.
• Enable automatic history suggestions if your build provides that separate choice.
• Review retention and privacy settings that clear or suppress history.
• Create a distinctive query and test it before and after File > Exit.
• Verify that the active settings or portable folder is writable by the current account.
• Confirm every shortcut opens the same executable, instance, and user context.
• Test without custom launcher arguments, adding them back individually.
• Do not rebuild the filename index when only autocomplete is broken.
• Use a clean temporary profile before resetting the working configuration.

8. Frequently Asked Questions

8.1 Why does Everything show files but not previous searches?

The filename index and search history are separate. Everything can search millions of indexed names correctly while history recording is disabled, cleared, unwritable, or stored under another profile. Check the History options and perform a clean-exit persistence test.

8.2 Why does autocomplete work until I restart Everything?

This strongly suggests a save problem. The data folder may be read-only, a portable copy may be running from protected storage, a cleanup utility may remove history, or the process may be terminated before it saves. A successful clean exit followed by a restart confirms persistence.

8.3 Will Force Rebuild restore search suggestions?

No, not normally. Force Rebuild recreates filename index data. It does not recreate searches that were cleared or never saved. Use it only when known files are missing from results after filters and exclusions have been ruled out.

8.4 Does the Everything service store autocomplete history?

The service supports indexing access without requiring the main interface to run with elevated privileges. Search-box history is associated with the user-facing configuration, not simply the service state. A stopped service may affect indexing behavior, but it is not the first place to look when only suggestions are missing.

8.5 Can a NAS or mapped-drive problem remove autocomplete?

A disconnected NAS or mapped drive can remove or stale the corresponding results, but locally stored previous-query suggestions should usually remain. If both change together, check whether a launcher, server connection, or different Windows account is loading another Everything profile.

8.6 Is Everything the same as Windows Search?

No. Everything by voidtools uses its own indexing and configuration mechanisms, while Windows Search is a separate Windows component. Rebuilding the Windows Search index or changing Windows Search settings is unlikely to repair Everything's autocomplete history. Troubleshoot the Everything History options and active data location first.