Everything External Drive Not Showing: How to Fix It

When an external USB drive appears in File Explorer but not in voidtools Everything, the drive itself is usually not the problem. The most likely causes are an indexing option that excludes removable volumes, an unsupported indexing method for the drive's file system, a changed drive letter, an exclusion or active search filter, or a mismatch between the account running Everything and the account that can access the drive.

Everything is not Windows Search. Windows Search builds a content-oriented index for selected locations, while Everything is primarily designed for extremely fast filename searching and uses different indexing methods depending on the volume and configuration. A drive working in File Explorer or Windows Search therefore does not guarantee that it has been added to Everything's database. The steps below isolate the failure without deleting the database or changing several unrelated settings at once.

1. Confirm the Symptom With a Small Safe Test

Begin with one known file instead of searching for a broad term. This separates an indexing problem from a query, filter, or filename problem.

1. Connect the external drive and wait for Windows to assign it a drive letter.
2. Open the drive in File Explorer and create a harmless text file named everything-external-test.txt.
3. Confirm that the file opens normally and note the current drive letter.
4. Open Everything, clear the search box, and make sure no restrictive filter is selected.
5. Search for everything-external-test.txt.

If the file appears with the correct external-drive path, indexing is working. Stop changing index settings and investigate the original query, filter, or excluded location instead. If the test file does not appear, continue with the checks below.

1.1 Inspect the status bar and result count

The Everything status bar can provide immediate clues. A rapidly changing object count may mean an index is still building. A search that reports no matches while displaying a restrictive filter or search mode may indicate a query problem rather than a missing volume.

Clear the search box completely and switch to the broad Everything filter before repeating the known-filename test. Also turn off options such as Match Case, Match Whole Word, Match Path, or regular expression searching if they are active. Success means the exact test filename appears under the external drive's current path. Once it does, do not rebuild the database.

2. Check the Indexing Method for the External Drive

The correct fix depends on how Windows presents the volume and which file system it uses. Do not assume that every USB device is treated as removable or that every external disk uses NTFS.

2.1 Check fixed versus removable drive options

Windows can report one USB storage device as a fixed disk and another as removable media. In Everything, open Tools > Options > Indexes and inspect the volume-related settings. Look for options that automatically include new fixed volumes and new removable volumes.

• If the external disk is reported as fixed, enable automatic inclusion of new fixed volumes if that behavior is appropriate.
• If it is reported as removable, enable automatic inclusion of new removable volumes if you want future removable disks indexed automatically.
• If you prefer tighter control, leave automatic inclusion disabled and explicitly include only the required volume.

After applying the setting, allow Everything time to scan or update the relevant index. Repeat the exact test-filename search. Success means the file appears with the correct drive letter. At that point, stop changing settings.

2.2 Verify NTFS removable volume settings

Everything can index local NTFS volumes efficiently by reading NTFS metadata when it has the required access. In the NTFS index options, select the external volume and confirm that it is included in the database. If change monitoring is available and enabled, Everything can keep the results current after the initial index.

An NTFS USB drive may be absent because removable volumes were not automatically included, because that specific volume was unchecked, or because Everything cannot currently access the volume metadata under its running account. Apply one change at a time, then search for the known test file.

If the volume is listed and enabled but the file is missing, use a targeted rescan or Force Rebuild only after checking filters, exclusions, drive letters, and service state. Rebuilding is more disruptive than correcting a single unchecked volume.

2.3 Use folder indexing for non-NTFS drives

External drives commonly use exFAT or FAT32 for compatibility with other operating systems and devices. These file systems do not provide the same NTFS metadata that Everything's NTFS indexing relies on. Add the drive or an appropriate directory through Tools > Options > Indexes > Folders.

Select the drive root, such as E:\, if the entire drive should be searchable. If only one directory matters, add that directory instead to reduce scanning work. Folder indexing also applies to many network and mapped-drive scenarios where direct NTFS volume indexing is not available.

Wait for the folder scan to complete and search for everything-external-test.txt. Success means the result appears with its current path. Folder indexes may update on a schedule or through configured rescans, so review the folder's update settings if new files appear only after a manual rescan.

2.4 Correct a changed drive letter

Windows may assign a different letter after the drive is reconnected, especially when another device has claimed its previous letter. An existing folder index for E:\ will not automatically describe the same storage if Windows now mounts it as F:\.

Compare the letter shown in File Explorer with the location configured under folder indexes. Remove or correct only the stale folder-index entry, then add the current path. For an NTFS volume index, verify that the currently connected volume is selected rather than relying only on a remembered letter.

Success means new results use the current letter and open correctly. Old results pointing to a disconnected path indicate a stale index entry that should be corrected, not a need to alter Windows Search.

3. Check Filters, Exclusions, and Result Omission

If Everything indexes the volume but hides its files from the current result set, rebuilding will not solve the underlying problem. Search-state and exclusion checks should therefore come before a full rebuild.

3.1 Reset the active search conditions

Clear the query and choose the Everything filter. Then type only the literal test filename. Avoid path operators, regular expressions, size conditions, date conditions, macros, and custom filters during this test.

If the filename appears after resetting the search, the drive was indexed correctly. Reintroduce the original query components one at a time until the restrictive condition is identified. Common examples include a path restriction for an old drive letter, a file-type filter that excludes the test file, or Match Path changing how the query is interpreted.

3.2 Review exclusions and omitted results

Open the exclusion settings and look for the external drive letter, its root path, a parent folder pattern, or file attributes that could hide its contents. Also check whether results are being omitted through configured result settings, filters, or launch parameters.

Temporarily disable only the suspected exclusion, apply the change, and repeat the test. If the file appears, refine or remove that rule. Do not disable all protections or unrelated exclusions permanently. The goal is to identify the specific rule responsible for the missing path.

3.3 Check command-line and portable settings

A shortcut can start Everything with command-line options that select a particular database, configuration file, instance, server, or search. Right-click the shortcut, inspect its target, and compare it with a direct launch of the expected Everything executable.

Portable copies deserve special attention because two copies can maintain separate settings and databases. You may have added the external drive to one instance while searching in another. Check the executable path, window title, configuration location, and active instance before editing indexes.

Success means the intended instance displays the test file. If a direct launch works but the shortcut does not, correct the shortcut or its options rather than rebuilding a healthy index.

4. Verify the Service, Server, and Account Context

Everything may run directly under the signed-in user, use its service for privileged NTFS access, or connect to another Everything instance. These arrangements can produce different results when a USB drive is visible only in one Windows session.

4.1 Check the Everything service state

In Everything's options, inspect the service setting. If the service is part of your configuration, confirm through Windows Services that it is installed and running. Restarting a stopped service is safer than changing permissions broadly or running every program as an administrator.

After correcting the service state, reopen Everything if necessary and test the known filename. Success means the external NTFS volume is indexed and the test file appears. If the service repeatedly fails, inspect the Windows Event Viewer and Everything diagnostic output before attempting repeated reinstalls.

4.2 Distinguish local searches from server searches

Some installations connect to an Everything server or another instance instead of searching a local database. A remote server cannot automatically see a USB drive attached to your workstation. Likewise, a client searching a server's database will return files visible to that server, not every drive visible in local File Explorer.

Confirm whether the active window is using a local index or a server connection. If the drive is physically connected to the local PC, test it in a local Everything instance. If it is attached to the server, configure indexing on that server under an account that can access the volume.

Do not expose Everything's server features directly to the public internet as a troubleshooting shortcut. Use authenticated, restricted network access and appropriate firewall rules. Success means the instance responsible for indexing can actually access the drive and returns the test file.

4.3 Compare Windows account contexts

A drive may be available to your interactive account but not to a service account, elevated process, scheduled task, or different signed-in user. This distinction is especially important for mapped network drives, because drive-letter mappings are usually created within a particular user logon context.

If a mapped drive is missing, add its UNC path as a folder index where appropriate, such as \\server\share\folder, and ensure the indexing account has permission. Avoid embedding broadly privileged credentials or granting access to Everyone merely to make search work.

Success means the same account or service responsible for indexing can list the folder and Everything can return the known filename. If direct access fails in that context, fix the Windows or share permission first.

5. Check Reconnect Behavior, Permissions, and Security Software

5.1 Safely eject and reconnect the drive

A drive that was disconnected during a scan may remain unavailable until Windows mounts it cleanly. Close files using the drive, use Windows' safe-eject function, disconnect it, and reconnect it to a stable USB port. Wait until File Explorer can open the root directory before testing Everything.

Confirm the new drive letter after every reconnect. If folder indexing references the previous letter, update that path. Success means the test file appears and opens from the result list. If Windows itself reports disk or file-system errors, resolve those before modifying Everything.

5.2 Verify ordinary read permissions

Open the target folder in File Explorer under the same user account. Try listing the directory and opening the test file. Everything may be able to index a filename while the user cannot open it, or folder scanning may fail because the indexing process cannot traverse the path.

Correct permissions narrowly at the affected folder or share. Do not take ownership of an entire disk or weaken access controls unless that is genuinely required and understood. For managed systems, involve the administrator responsible for the storage permissions.

5.3 Investigate antivirus or endpoint controls carefully

Security software can block metadata access, service activity, executable launches, or folder traversal. Check the product's event history or quarantine records for a specific Everything-related block. If your organization uses application control, verify that the installed or portable executable is approved.

Do not permanently disable antivirus or endpoint protection. If a controlled temporary test is permitted, use the security product's documented process and restore protection immediately. Prefer a narrow allow rule for a verified executable or folder after confirming the block. Success means Everything indexes the drive while security controls remain active.

6. Use Diagnostics Before a Force Rebuild

6.1 Review index information and the Index Journal

Everything's index-related views and journal information can help establish whether the external volume was added, scanned, removed, or changed. Look for activity corresponding to the drive's connection time and the creation of the test file.

If the drive is present but the new file is absent, trigger the appropriate folder rescan or confirm change monitoring for the NTFS volume. If no activity refers to the drive at all, return to the volume inclusion and folder-index settings.

6.2 Capture debug output

Use Everything's supported diagnostic or debug logging facilities to reproduce one simple event: connect the drive, create or rename the test file, and search for it. Keep the test short so the relevant messages are easier to identify.

Look for access failures, unavailable paths, service connection problems, invalid folder locations, or an unexpected configuration instance. Debug logs can contain filenames and paths, so review and redact sensitive information before sharing them with support staff.

6.3 Use Force Rebuild only after configuration checks

A Force Rebuild is appropriate when the correct drive is included, access works, filters and exclusions are clear, and the index still appears stale or inconsistent. Open the index options and use the available Force Rebuild control, then wait for indexing to finish.

Do not repeatedly rebuild while changing other settings. One controlled rebuild provides a useful result; repeated rebuilds conceal the original cause and waste time. Success means the test file and other current filenames appear under valid paths after the rebuild.

7. Run a Clean Temporary Test

If the normal profile still produces Everything results missing from one drive, run a temporary clean configuration without destroying the working profile. Use a separate verified copy or instance configured according to the application's supported portable or instance behavior. Do not overwrite the existing configuration or database.

1. Close or clearly distinguish the normal instance.
2. Start the temporary instance with clean settings.
3. Add only the affected volume using NTFS volume indexing or folder indexing as appropriate.
4. Create a second uniquely named test file on the drive.
5. Wait for indexing and search for that exact filename.

If the clean instance finds the file, the hardware, file system, and basic Everything indexing path work. The normal profile likely contains an exclusion, stale folder path, alternate database, command-line setting, or filter. Compare settings methodically instead of replacing the entire profile.

If the clean instance also fails, focus on volume detection, account access, service operation, security controls, and Windows storage health. Stop experimenting once a test succeeds, then apply only the identified correction to the normal setup.

8. Quick Fix Checklist

• Confirm Windows can open the external drive and note its current letter.
• Create and search for one unique test filename.
• Clear the query and select the broad Everything filter.
• Disable Match Path, regex, and other restrictive search modes for testing.
• Check whether Windows reports the disk as fixed or removable.
• Enable or explicitly include the appropriate external volume.
• For NTFS, verify the volume is included in the NTFS index.
• For non-NTFS drives, add the drive through folder indexing.
• Update folder-index paths after a drive-letter change.
• Review exclusions, omitted results, shortcuts, and command-line options.
• Confirm you are using the intended local, portable, or server instance.
• Verify the Everything service is running if your setup uses it.
• Check account access to mapped drives and network shares.
• Safely eject, reconnect, and wait for Windows to mount the drive.
• Use a targeted rescan before attempting Force Rebuild.
• Run a clean temporary profile test if the normal configuration remains suspect.

9. Frequently Asked Questions

9.1 Why can File Explorer see my USB drive when Everything cannot?

File Explorer displays storage that Windows has mounted for your account. Everything searches its own filename database, which must include the volume through a compatible volume index or folder index. The drive can therefore work normally in File Explorer while remaining absent from Everything's database.

9.2 Does an external drive need to be NTFS?

No. The practical indexing method changes with the file system. Local NTFS volumes can use Everything's NTFS indexing capabilities. Drives formatted as exFAT, FAT32, or another file system can generally be searched by adding an accessible path through folder indexing. Folder indexing may take longer and may rely on scheduled or manual rescans.

9.3 Why did Everything stop finding the drive after reconnection?

The drive letter may have changed, the device may not have mounted cleanly, or a removable-volume setting may no longer match the connected device. Confirm the current letter in File Explorer, compare it with configured folder indexes, and test one known filename after reconnecting.

9.4 Should I delete the Everything database?

Not as a first step. First check the active filter, search modes, exclusions, drive inclusion, folder path, service state, account context, and instance. Use Force Rebuild only when the configuration is correct but the index remains stale. A temporary clean instance is often a safer diagnostic test than deleting the existing database.

9.5 Why are new external-drive files missing while older files appear?

The initial index exists, but change monitoring or folder rescanning may not be updating it. For an NTFS volume, verify that the volume remains connected and monitoring is enabled where appropriate. For a folder index, inspect its rescan or update behavior and run one targeted rescan. Success means a newly created unique test file appears.

9.6 Can Everything search a NAS or mapped network drive?

Yes, when the accessible network location is configured through an appropriate folder index or indexed by an Everything instance running on the server. Mapped letters may not exist for services or other user accounts, so a UNC path is often more reliable. Ensure the indexing account has read access, and keep any server interface restricted to trusted networks.