Everything Home Search Defaults Wrong: How to Fix It

When voidtools Everything opens with the wrong search text, filter, sort order, Match Case setting, Regex mode, or other search state, the index is not necessarily broken. These symptoms usually come from Everything's Home settings, a startup command-line argument, settings that were not saved, or an unwritable portable INI file. Missing results can also involve exclusions, folder indexes, services, network access, or account permissions, but those are separate from a wrong startup state. The steps below begin with a controlled test so you can identify the responsible setting without resetting a working index or changing unrelated Windows services.

1. Confirm the Symptom With a Small Safe Test

First, separate a startup-default problem from an indexing problem. Open Everything normally and look at the search box, active filter, column headings, sort indicator, status bar, and search-option menu. Note exactly what is wrong before changing anything.

For example, the application may open with old search text, Files or Folders may be selected instead of Everything, Date Modified may replace Name as the sort column, or Match Case may already be enabled. Write down the unexpected state or take a screenshot. This gives you a reliable comparison after each fix.

1.1 Test a Known Local File

Create a harmless test file in a local NTFS folder that Everything normally indexes, such as your Documents folder. Give it a distinctive name such as everything-default-test-4821.txt. Wait briefly, clear the search box, select the Everything filter, and search for the distinctive filename.

• If the file appears, the core local index is working.
• If it appears only after clearing startup text or disabling Regex, the startup search state is responsible.
• If it does not appear, check indexing, exclusions, permissions, and service state later in this guide.
• If local files appear but NAS files do not, investigate the folder index or network account context.

Success at this stage means you can reproduce the problem and know whether it concerns startup defaults, missing results, or both. Stop testing the index if the known file appears and your only issue is the way Everything opens.

1.2 Compare Home With a Cleared Search

Manually clear the search box, select the intended filter, choose your preferred sort column and direction, and turn Match Case, Match Path, Whole Word, or Regex on or off as desired. Run the same known-file search again.

If Everything works after those manual changes but reverts when you invoke Home or restart the program, focus on the Home settings and saved configuration. Do not rebuild the database for that symptom. Rebuilding changes indexed data, not the Home state that controls how the search window is restored.

2. Correct Everything Home And Startup Settings

Everything has Home settings that define what happens when the Home command is used and, depending on the selected behavior, what state a search window starts with. Open Tools > Options and locate the Home page. Exact labels and available choices can differ between maintained Everything releases, so read the descriptions shown in your installed build.

2.1 Review Every Home Category

Check the Home choices related to the search text, filter, sort, view, and search options. A category may be configured to preserve its current state, restore a saved state, or use a defined default. That distinction explains many reports that Everything home search defaults are wrong.

Set each category deliberately:

• Search text: Choose an empty search if Home should clear old queries.
• Filter: Select Everything if startup should not be limited to files, folders, pictures, or a custom filter.
• Sort: Choose the column and direction you want to use as the baseline.
• Search options: Decide whether Match Case, Match Path, Whole Word, diacritics handling, or Regex should be enabled.
• View: Select the preferred result presentation if the Home page offers that control.

Apply the changes, close Options, alter the current search state, and invoke Home. Then exit Everything normally, reopen it through your usual shortcut, and test again. Success means Home and a fresh normal launch now produce the intended empty query, filter, sort, and option state. Once that happens, stop changing settings.

2.2 Fix Unexpected Match Case Or Regex Defaults

Match Case and Regex can make an otherwise valid filename search appear broken. Match Case requires the capitalization to agree. Regex interprets characters such as periods, brackets, parentheses, asterisks, and question marks as part of a regular expression rather than ordinary filename text.

Open the Search menu and inspect the relevant options. Disable Regex for ordinary filename searches and disable Match Case unless case-sensitive matching is intentional. Then return to the Home page and ensure the saved Home search options agree with those choices.

A useful test is a filename containing a period or parentheses. Search for it first with Regex disabled. If it appears, enable Regex and repeat only if you understand the required pattern. If ordinary searches work with Regex off, the index is healthy and no rebuild is needed.

2.3 Remove Unwanted Startup Search Text

If text returns every time Everything starts, it may come from the Home configuration, session restoration, a shortcut argument, a launcher, or automation. Clear the text and save the intended Home state first. Exit through the normal application command rather than ending the process in Task Manager or shutting Windows down immediately.

Next, inspect how Everything is launched. Right-click the shortcut, open its properties, and examine the Target field. The executable path should not be followed by an unwanted search expression, filter, sort instruction, or search-option switch. Also inspect taskbar shortcuts, startup entries, scripts, scheduled tasks, hotkey utilities, and portable-app launchers. They may use different arguments from the shortcut you normally inspect.

Success means launching the executable directly and launching through the usual shortcut produce the same clean search. If direct launch is correct but the shortcut is not, fix the shortcut or launcher and leave Everything's index settings alone.

2.4 Verify The Default Sort

Click the desired column heading to select the sort field and click again if you need to reverse its direction. Then configure the corresponding Home sort choice instead of assuming the current visible sort will become permanent automatically.

Be aware that some sorts need additional indexed properties or more work than a basic name sort. That affects performance, but it should not cause the program to choose a different startup sort. If Home restores the chosen column and direction consistently after a normal restart, the issue is fixed.

3. Make Sure Everything Can Save Its Settings

A correct setting that disappears after restart usually indicates a configuration persistence problem. This is especially common with portable installations, read-only folders, application-management tools, multiple instances, or abnormal termination.

3.1 Exit Normally And Confirm Persistence

Change one harmless visible option, apply it, and exit Everything normally. Reopen the same executable using the same Windows account. If the change persists, configuration writing is functioning. If it does not, avoid making ten more changes because they will probably be lost for the same reason.

Check whether Everything remains running in the notification area after you close its window. Closing a window and fully exiting the application may be different actions. Use the program's Exit command when testing whether settings are written on exit. Also allow it a moment to finish rather than immediately terminating the process.

3.2 Check Portable INI Write Permissions

A portable copy commonly stores configuration beside its executable in an INI file. That location must be writable by the account running Everything. Portable copies placed under protected directories, extracted from read-only media, synchronized into a restricted folder, or launched from a share may fail to preserve changes.

Close Everything and inspect the portable folder. Confirm that the INI file is not marked read-only and that your account can create, modify, and rename a small test file in the directory. Do not weaken permissions across an entire protected system folder. Instead, move the portable installation to a user-writable folder intended for applications or correct the permissions only where appropriate.

Also check whether a deployment tool, backup restore process, synchronization program, or portable launcher replaces the INI file at each launch. If its modification timestamp changes and then rolls back, the external tool may be restoring old defaults.

Success means a single Home-setting change survives a complete exit and restart from the same portable executable. Stop once persistence is confirmed.

3.3 Check For Multiple Executables Or Instances

It is easy to configure one Everything installation and later launch another. Search for Everything executables in your installed-program and portable-app locations. Compare the executable path shown by Task Manager or shortcut properties with the copy you intended to configure.

Named instances can also maintain distinct settings and indexes. A work instance, portable instance, and default instance may therefore open differently without any corruption. Use the same shortcut and instance for both configuration and verification.

4. Investigate Missing Results Separately

If the startup state is now correct but expected files remain absent, move to index troubleshooting. Everything is a dedicated filename search application and is not the same as Windows Search. Windows Search indexing settings, Start menu search behavior, and content-indexing controls do not automatically determine Everything's results.

4.1 Check NTFS Indexes, Folder Indexes, And File Systems

Everything can index local NTFS volumes efficiently through filesystem metadata. Other filesystems and network locations generally require appropriate folder-index or server arrangements. A mapped NAS drive is not equivalent to a local NTFS volume.

Open the index-related pages in Options and verify that the relevant local volume or folder is included. For a folder index, confirm the path is still valid and review its update behavior. Removable-drive letters, mapped-drive letters, and share paths can change, leaving the stored folder path pointed at the wrong location.

Success means the known test filename appears under the expected full path and remains present after an index update. Do not change Home settings if only one drive or share is missing.

4.2 Review Exclusions And Result Omissions

An exclusion can hide a volume, folder, filename pattern, or file type from the index. Search filters and result-omission features can also hide indexed items from the current result list. Review the exclusion page and temporarily test only the specific rule that could match the missing path.

Before deleting a rule, record it. If disabling that rule makes the known file appear, narrow or correct the rule instead of removing all exclusions. Also select the Everything filter and clear the search box to ensure a custom filter is not suppressing the result.

4.3 Check Service And Account Context

The Everything service helps the client obtain the access needed for efficient local NTFS indexing without requiring the user interface to remain elevated. If local NTFS results are incomplete, inspect the service-related options and Windows Services to confirm that the configured Everything service is present and running.

Network shares are different. Services often run under an account that does not have the same NAS credentials or mapped drives as your interactive user. Drive mappings are also account and session specific. Prefer a valid UNC path where appropriate, and make sure the component reading the share runs under an account authorized to access it.

Do not expose an Everything server directly to the public internet. If you use ETP, HTTP, or another server feature, restrict it to trusted networks, use appropriate authentication where supported, and enforce access with network and firewall controls. A remote server selection can also explain why results differ from the local index.

4.4 Consider Firewall And Antivirus Only When Relevant

A firewall matters when Everything is connecting to or serving results over a network. It does not normally explain an incorrect local Home sort or Regex default. Verify the specific application, port, address, and network profile involved rather than disabling the firewall globally.

Security software may block configuration writes, executable launches, service communication, or access to a protected folder. Review its event history or logs and add a narrow, justified allowance only after identifying a block. Never disable endpoint protection permanently as a generic Everything troubleshooting step.

5. Use Built-In Evidence Before Rebuilding

The status bar and Options pages usually provide enough evidence to distinguish an empty index from a restrictive query. Check the result count, active filter, search mode, and whether Everything is scanning or updating. A very small result count with a visible query points toward search state, while a missing volume points toward index configuration.

5.1 Run Simple Search Syntax Tests

Start with an empty search and the Everything filter. Then test the exact filename without operators. Next, search for a unique substring. Finally, test the full path if necessary. Keep Regex, Match Case, and custom filters disabled during this baseline.

If the plain substring works but a complex expression fails, troubleshoot the expression rather than the index. Add one operator at a time until the failure returns. This is faster and safer than rebuilding a healthy database.

5.2 Use Force Rebuild Only For Index Evidence

Force Rebuild is appropriate when an included index is demonstrably stale or inconsistent, not when Everything merely opens with the wrong filter or sort. Before rebuilding, verify the indexed volumes, folder paths, exclusions, service state, and account access. Rebuilding an incorrectly configured index will reproduce the same omission.

After a justified rebuild, wait for indexing activity to complete and repeat the known-file test. Success means the test file and expected neighboring files appear. If they do, stop. Repeated rebuilds are unlikely to fix a persistent permission, path, or exclusion problem.

5.3 Use Debug Logs And The Index Journal Selectively

Diagnostic logging can help reveal startup arguments, configuration loading, index updates, and access failures. Enable diagnostics only long enough to reproduce the problem, record the time, and then disable them. Logs may contain filenames, paths, share names, or search terms, so redact private information before sharing them.

If your build provides an Index Journal or index-change view, use it to determine whether a file creation, rename, or deletion reached the index. A recorded change with a missing visible result suggests a filter or query issue. No recorded change suggests an indexing, monitoring, path, or access issue.

6. Run A Clean Temporary Test

When settings remain confusing, run a temporary clean test before resetting your working configuration. Obtain Everything from the official voidtools site and place a portable copy in a new user-writable folder. Keep your existing installation and configuration backed up and unchanged.

Launch the clean copy in a way that keeps it separate from your normal configured instance. Do not add startup arguments, import an old INI file, or configure servers initially. Search for the known local test file and inspect the default Home behavior.

• If the clean copy behaves correctly, the original configuration, launcher, or INI persistence is the likely cause.
• If both copies show missing local files, inspect volumes, the service, filesystem support, and account access.
• If only network results are missing, test the share path and credentials from the same account context.
• If the clean copy inherits old behavior, verify that you actually launched the new executable and a separate instance.

Change only one Home option in the temporary copy, exit normally, and reopen it. If the option persists, compare the temporary and original environments rather than replacing files blindly. The goal is diagnosis, not immediate migration.

7. Quick Fix Checklist

1. Record the unwanted search text, filter, sort, and search-option state.
2. Clear the query and select the Everything filter.
3. Disable Regex and Match Case for a plain filename test.
4. Search for a uniquely named local test file.
5. Configure search text, filter, sort, and options on the Home page.
6. Exit Everything normally and reopen the same executable.
7. Inspect shortcut, launcher, startup, and scheduled-task arguments.
8. Confirm that a portable INI and its folder are writable.
9. Check for multiple installations or named instances.
10. For missing results, review volumes, folder indexes, exclusions, and omissions.
11. Check the service for local NTFS indexing and account access for shares.
12. Use Force Rebuild only after evidence shows an index problem.
13. Run a separate clean portable test before resetting many settings.

The repair is complete when a normal launch opens with the intended search state, Home restores the intended defaults, settings survive restart, and the known test file appears from every location that is supposed to be indexed. At that point, stop changing options and remove the temporary test file.

8. Frequently Asked Questions

8.1 Why Does Everything Open With My Previous Search?

The Home search-text behavior may be configured to preserve or restore a query, or a shortcut may be supplying search text at launch. Set Home to use an empty search, exit normally, and inspect the shortcut Target field if the text returns.

8.2 Why Does Everything Start In Regex Mode?

Regex may be part of the saved Home search options, restored session state, a command-line argument, or a launcher profile. Disable Regex in the Search menu, update the Home options, and verify that your startup shortcut contains no option that enables it.

8.3 Why Does Everything Forget My Default Sort?

The sort may not be configured as the Home sort, or the configuration may not be written on exit. Set the Home sort explicitly, exit normally, and test whether another simple setting persists. For portable installations, verify INI write permissions.

8.4 Should I Delete The Everything Database?

Not as a first step. Deleting or rebuilding the database will not correct a Home filter, startup query, Regex default, unwritable INI file, exclusion, invalid network path, or launcher argument. Use Force Rebuild only after the index configuration is correct and evidence shows stale or inconsistent indexed data.

8.5 Why Are Files On My NAS Missing?

A NAS share is not indexed like a local NTFS volume. Verify the configured folder index or remote-server arrangement, the UNC path, update behavior, and the credentials available to the process doing the indexing. A mapped drive visible to your desktop account may not exist for a service account.

8.6 Is Everything The Same As Windows Search?

No. Everything is a separate filename-search application with its own indexes, filters, services, configuration, and optional server features. Changing Windows Search indexing locations will not normally fix Everything's Home defaults or exclusions. Troubleshoot the application that is actually producing the results.