Everything Empty Search Shows No Results: How to Fix It

When an empty search in voidtools Everything shows no results, the problem is usually not the search box itself. With no search text entered and the Everything filter active, the results pane should normally display the full set of currently visible indexed items. A blank pane can therefore point to a restrictive Home search setting, an active filter, result omissions, an empty or unavailable index, an unexpected server connection, or a startup option that changes the normal view.

This guide focuses specifically on what happens when the search box is empty. Everything is a filename indexing and search application, not the Windows Search interface. Its indexing model, service, filters, and network options are separate from Windows Search, so rebuilding the Windows Search index will not normally fix this symptom.

1. Confirm the Symptom With a Small Safe Test

Before changing index settings, verify that the search field is genuinely empty and that Everything is expected to show all results. This prevents an invisible search condition, active filter, or interface setting from being mistaken for a damaged index.

1.1 Clear the search and select the Everything filter

1. Open Everything and click inside the search box.
2. Press Ctrl+A, then Backspace or Delete.
3. Open the Search menu and select the Everything filter.
4. Wait briefly and inspect the results pane and status bar.

If the interface has a filter selector, confirm that it also says Everything. Filters such as Audio, Documents, Folders, Pictures, or a custom filter can restrict the empty view because a filter is effectively an additional search condition.

Success means the results pane fills with indexed files and folders, and the status bar reports a nonzero result count. If that happens, stop troubleshooting. The index is working, and the original cause was the search text or filter state.

1.2 Run a known-name search

Search for a common file or folder that you know exists on an indexed local NTFS volume, such as Windows, Users, or explorer.exe. Avoid beginning with a mapped drive or NAS share because those locations may require separate folder indexing or network access.

• If a known-name search returns results but the empty search does not, the index is probably populated but the default view is being restricted or hidden.
• If searches return nothing and the status bar reports zero indexed objects, investigate the index, service, and indexed locations.
• If searches work only for some drives, inspect the index configuration, exclusions, file system type, and drive availability.

This distinction matters. A populated index hidden by a filter calls for a settings correction, while a genuinely empty index calls for an indexing diagnosis.

2. Check Settings That Directly Control the Empty View

2.1 Review Home search settings

Everything can restore a configured Home state when it starts, when a window opens, or when the Home command is used. Depending on the installed release and configuration, Home settings can include the search text, filter, sort, view, and search options.

Open Tools, Options, and locate the Home settings. Check whether Home is restoring a search expression or a restrictive filter. Set the Home search to empty and the Home filter to Everything, or choose the applicable default or current-state controls that produce an unrestricted view.

After applying the change, invoke Home or restart Everything normally. Success means the search box remains visibly empty, the Everything filter is active, and the full result list appears. Once this works, do not rebuild the index.

2.2 Reset the active filter

Select Search, then Everything. If a filter bar or filter selector is visible, reset it there as well. Custom filters may contain search syntax even when the main search box is empty, which can make the result pane appear inexplicably blank.

If selecting Everything immediately restores results, the active filter was the cause. You can later review custom filters through the filter management interface, but there is no need to change indexing options.

2.3 Turn off restrictive search modes

Inspect the Search menu for enabled options such as Match Case, Match Whole Word, Match Path, regular expressions, or diacritic matching. Most of these should not suppress a truly unrestricted empty query, but they become relevant if Home or a custom filter silently restores search text or syntax.

Reset unusual search modes, clear the box again, and select the Everything filter. Stop when the full index reappears. Avoid changing unrelated options after confirming success.

2.4 Inspect result omissions

Some Everything configurations can omit results through an omission list, filter, search rule, or related results setting. Menu names vary between stable and preview builds, so look for settings labeled Omit, Omissions, Exclude, or Results.

Temporarily disable user-created omissions or review their expressions. A broad rule aimed at hiding temporary files, system folders, or a drive can accidentally hide nearly everything. Do not remove rules permanently until you identify the one responsible.

Success means disabling one omission restores the expected result count. Re-enable other rules individually and keep only the problematic rule disabled or correct its scope.

2.5 Check whether the results are hidden by the interface

A populated result set can look empty if the results pane is collapsed, columns are arranged unexpectedly, the window layout is corrupted, or the text and background colors are difficult to distinguish. Maximize the window, restore a standard view from the View menu where available, and verify that the result list has usable height.

The status bar is decisive here. If it reports thousands or millions of results while the pane looks blank, the index is not empty. Focus on the view, theme, columns, or profile settings rather than rebuilding the database.

3. Verify That Everything Has a Usable Index

3.1 Read the status bar before changing anything

The status bar can reveal the current result count and whether indexing activity is underway. An empty search with a large result count indicates a display problem. A zero result count with indexing still in progress may simply require time. A persistent zero count suggests that no usable locations are indexed or that the application is running in an unexpected mode.

Wait for active scanning or updating to finish before testing again. Success means the indexed-object or result count becomes nonzero and filenames appear.

3.2 Review NTFS and ReFS index settings

Open Tools, Options, Indexes and review the available volume pages. Confirm that the expected local volumes are listed and enabled for indexing. Everything commonly uses file system metadata for fast indexing on supported local file systems, particularly NTFS. A removable disk that is disconnected, a volume with a changed drive letter, or an unchecked volume can explain missing results.

If the expected drive is present but disabled, enable it and allow indexing to complete. If it is absent, verify in Windows Disk Management or File Explorer that the volume is mounted and accessible under the current account.

Success means the volume appears in the index configuration and its files become searchable. Stop changing settings once the expected drive and result count return.

3.3 Verify folder indexing for NAS and unsupported locations

Mapped drives, UNC shares, NAS folders, and locations that cannot use Everything's normal local volume indexing may need to be added as folder indexes. Open the Folder index settings and verify that the required path is present, reachable, and scheduled or configured to update appropriately.

A folder index is a scanned catalog. It does not necessarily update in exactly the same way or at the same speed as a local NTFS index. If the share was offline when Everything started, the existing folder index behavior depends on its configuration and availability.

Test the path in File Explorer using the same Windows account. If prompted, authenticate normally, then request a folder-index rescan from Everything. Success means the indexed share contributes results after the scan finishes.

3.4 Review exclusions

In the Indexes or Exclude settings, look for excluded volumes, folders, files, wildcards, or attributes. A broad path such as a drive root, an overly general wildcard, or multiple inherited rules can leave the effective index empty.

Temporarily disable only the suspicious exclusion, then allow Everything to update. Do not erase the entire exclusion list without recording it. Success means the missing locations return after one specific exclusion is corrected.

3.5 Use Force Rebuild only after configuration checks

If expected volumes are enabled, exclusions are reasonable, the service is available, and the status still indicates an empty or inconsistent index, use the Force Rebuild control in the index options. A rebuild recreates Everything's own database from configured sources. It does not rebuild Windows Search.

Let the process finish before judging the result. Repeatedly rebuilding while changing filters or network settings makes diagnosis harder. Success means the indexed count rises and an empty query displays the full visible index.

4. Check Windows, Service, Network, and Account Context

4.1 Confirm the Everything service state

Many installations use the Everything service to obtain the file system information needed for indexing without running the interface as an administrator. Open the relevant Everything service options or the Windows Services console and confirm that the service is installed and running if your configuration depends on it.

If it is stopped, start it through the normal interface or Windows service controls. If startup repeatedly fails, note the Windows error and check the application's troubleshooting information. Do not disable antivirus or endpoint protection permanently. Instead, review alerts and create a narrowly scoped exception only when your organization's policy permits it and the official executable has been verified.

Success means the service remains running and the index populates after Everything reconnects or restarts.

4.2 Compare normal and elevated account contexts

Settings and accessible network resources can differ between a standard launch and Run as administrator. Mapped drives are especially prone to appearing in one logon context but not another. Portable copies may also maintain a separate configuration beside the executable.

Launch Everything the same way you normally use it and verify the NAS path in File Explorer under that account. Do not use elevation as a permanent workaround for a mapping or credential issue. Prefer a UNC path for a folder index when that produces more consistent access.

4.3 Check network and firewall conditions

If Everything is acting as a client of an Everything server, ETP server, or another remote indexing setup, a disconnected server can leave the client with no remote results. Review the connection target, host, port, credentials, and whether the server is reachable on the trusted network.

Use firewall rules that are limited to the required application, port, and trusted network scope. Do not expose an Everything file-search server directly to the public internet. Use an approved VPN or similarly protected private connection for remote access.

Success means the client reconnects and the remote index count returns. If local results are expected instead, disconnect from the unintended server mode and launch the local instance.

4.4 Confirm startup behavior and portable settings

Inspect the shortcut used to launch Everything. Its Target field may contain command-line options that select a configuration, instance, server, search, or other startup behavior. Rather than guessing which argument is responsible, close Everything and launch the trusted executable directly without additional arguments.

If the direct launch works, compare the shortcut and startup entry with the official command-line documentation. Remove or correct only the option responsible for the restricted state.

For a portable installation, check whether Everything can read and write its configuration location. A read-only folder, changed executable path, synchronized configuration, or multiple portable copies can load unexpected settings. Preserve the existing INI file before testing a clean one.

5. Use Focused Diagnostics When the Cause Is Still Unclear

5.1 Compare status counts with search syntax tests

With the Everything filter selected, compare three tests: an empty query, a known filename, and a path-limited query for an indexed local drive. Use search syntax supported by your installed build and consult the official search documentation instead of relying on syntax copied from another application.

If the known filename appears but the empty query does not, revisit Home, filters, omissions, and the view. If no query finds anything and the indexed count is zero, revisit volumes, folders, service state, and server mode.

5.2 Review the Index Journal where available

Some Everything builds provide index journal or indexing diagnostics that show recent index activity. Use these tools to determine whether volumes were added, removed, rescanned, or unavailable. A journal that shows active indexing while the interface reports no visible results can help separate an indexing issue from a results-display issue.

Do not treat journal entries as instructions to delete the database. Record the relevant event and correlate it with drive changes, service restarts, or network outages.

5.3 Capture debug information carefully

If Everything provides a debug console or logging option in your build, enable it only long enough to reproduce the empty-search symptom. Look for errors involving volume access, folder scans, configuration loading, server connections, or database updates.

Logs can include local paths, filenames, hostnames, and share names. Remove sensitive information before sharing them publicly or with support. Disable extra logging after the test unless ongoing diagnostics require it.

6. Run a Clean Temporary Test Before Changing Many Settings

A temporary clean profile can reveal whether the problem belongs to the current configuration or to the Windows environment. First, close Everything and back up its configuration files. Do not delete the existing database or settings as your first step.

1. Download or use a trusted copy of the appropriate Everything executable from voidtools.
2. Place a portable test copy in a new writable folder.
3. Launch it directly without an old shortcut or command-line arguments.
4. Use a fresh configuration and enable only one known local volume if prompted.
5. Wait for indexing to complete, clear the search, and select the Everything filter.

If the clean instance shows the full index, Windows and the basic indexing method are functioning. The fault is likely in the original Home settings, filter, omissions, exclusions, server mode, startup arguments, interface profile, or portable configuration.

If the clean instance is also empty, investigate service access, supported volumes, account permissions, security alerts, and whether any index source is actually configured. Change one item at a time and repeat the same empty-query test after each change.

7. Quick Fix Checklist

• Clear the search box with Ctrl+A and Delete.
• Select Search, then Everything to reset the active filter.
• Check the status bar for a nonzero result count.
• Reset Home search text and the Home filter.
• Temporarily disable suspicious result omissions.
• Restore a standard results view if the count is nonzero but the pane is blank.
• Verify expected NTFS or ReFS volumes in Indexes.
• Check folder indexes for NAS, UNC, mapped-drive, or unsupported locations.
• Review broad exclusions affecting drive roots or all filenames.
• Confirm the Everything service is running when required.
• Check whether the application connected to an unintended remote server.
• Launch the executable directly to bypass shortcut arguments.
• Test a backed-up, clean portable profile before deleting anything.
• Use Force Rebuild only after verifying sources, filters, and exclusions.

The correct stopping point is simple: the search box is empty, the Everything filter is active, the status bar shows the expected nonzero count, and the results pane displays the indexed files and folders. Once those conditions are met, avoid additional changes.

8. Frequently Asked Questions

8.1 Should an empty Everything search show every indexed item?

Normally, yes. With no search text and the Everything filter active, Everything should display all indexed items that are not removed by exclusions, filters, omissions, or the current data source. Home settings and remote-server modes can modify that behavior.

8.2 Why does the status bar show results while the list is blank?

A nonzero result count indicates that the query produced matches. The likely issue is the interface, including a collapsed results pane, unusual view, color configuration, column layout, or profile corruption. Do not rebuild the index solely because the visible pane is blank.

8.3 Why does Everything find a filename but show nothing for an empty search?

This pattern points toward a Home setting, active filter, result omission, or interface state rather than an empty index. Reset the filter to Everything, clear Home search settings, and compare the status-bar counts.

8.4 Does rebuilding Windows Search fix Everything?

No. voidtools Everything and Windows Search are separate systems. Everything maintains its own index and can use file system metadata, folder indexes, services, and remote connections. Use Everything's own index controls when a rebuild is genuinely necessary.

8.5 Why are files from my NAS missing?

A NAS share generally needs an appropriate folder index or a configured Everything server arrangement. Confirm that the UNC path is accessible under the same account, review folder-index settings, rescan when appropriate, and check firewall rules on trusted networks.

8.6 Is it safe to delete the Everything database?

Deleting the database should not be the first troubleshooting step. First reset the filter, inspect Home and omission settings, verify index sources, check the service, and run a clean temporary profile. Use Force Rebuild through the application when configuration is correct but the index remains inconsistent.