Everything FAT32 Drive Not Indexed: How to Fix It

If a FAT32 or exFAT drive does not appear in voidtools Everything results, the most likely explanation is not a damaged search database. Everything indexes NTFS volumes differently from non-NTFS storage. FAT32, exFAT, many network shares, and some legacy file systems generally need to be added through folder indexing before their files can appear. Other common causes include a changed removable-drive letter, an inactive folder index, an exclusion, a restrictive search filter, a stale scan, or Everything running under a different Windows account context. The steps below begin with a small, safe test so you can identify the actual failure before rebuilding indexes or changing unrelated Windows settings.

1. Confirm the Symptom With a Small Safe Test

Start by proving that the problem is limited to one drive and is not simply a search query issue. Connect the FAT32 or exFAT drive, open it in File Explorer, and create a harmless test folder with an unusual name, such as EverythingFat32Test8472. Inside it, create a text file named index-check-8472.txt.

Open Everything and search for the exact filename:

index-check-8472.txt

If the file does not appear, remove the search text and look at Everything's status bar. A normal installation should report an indexed object count rather than remaining indefinitely in an active scanning state. Then search for a known file on an NTFS system drive. If the NTFS file appears but the FAT32 test file does not, Everything itself is working and the investigation should focus on folder indexing for the non-NTFS drive.

If neither file appears, check whether an Everything filter, search option, server connection, startup command, or broader configuration problem is affecting all results. Do not rebuild anything yet.

1.1 Verify the file system type

In File Explorer, right-click the affected drive, select Properties, and read the value next to File system. FAT32 and exFAT are the relevant cases here. A drive can have the same letter and label as before while using a different file system after reformatting, so confirm rather than assume.

This distinction matters because Everything can use the NTFS Master File Table and change journal for very fast indexing of local NTFS volumes. FAT32 and exFAT do not provide the same NTFS metadata. Everything therefore handles these drives through folder indexing, which scans directories in a more conventional way.

1.2 Check whether the result is merely hidden

Set the Everything filter to Everything. Clear the search box, then enter only the exact test filename. Turn off options such as Match Case, Match Path, Match Whole Word, or regular-expression mode if they are active and unnecessary. Also clear any advanced search expression left from an earlier task.

Success means the test file appears. If it does, stop changing index settings. The drive was indexed, and the original query or filter was excluding the expected result.

2. Add the FAT32 or exFAT Drive Through Folder Indexing

The primary Everything FAT32 drive not indexed fix is to add the drive as a folder index. Merely connecting a removable drive does not guarantee that Everything will index it like an NTFS volume.

2.1 Add the drive from the Folders tab

1. Connect the drive and confirm that Windows has assigned it a drive letter.
2. Open Everything.
3. Open Tools, then Options.
4. Go to Indexes, then Folders.
5. Select Add.
6. Choose the root of the FAT32 or exFAT drive, such as E:\.
7. Confirm the change and allow Everything to scan the folder.

Depending on the Everything release and interface layout, the exact button placement can vary, but the relevant setting is the folder list under the index options. Add the drive root if you want the whole drive searchable. Add only a specific directory if you want a narrower and faster index.

Success means the folder appears in the configured folder-index list and files from it begin appearing in searches. Once your test file is visible, stop changing settings. There is no reason to rebuild unrelated NTFS indexes.

2.2 Allow the initial folder scan to finish

Folder indexing is not as immediate as NTFS metadata indexing. Everything must enumerate directories and files, so scan time depends on the number of objects, directory depth, storage speed, USB connection, network latency, and whether the device is busy. A small flash drive may finish quickly, while a multi-terabyte exFAT disk containing millions of files can take much longer.

Do not judge scan progress only by transfer speed or total capacity. A drive containing hundreds of thousands of tiny files can take longer to enumerate than a drive containing a few large media files. Watch the Everything status bar and test for a newly scanned filename periodically.

Success means the test file and other known filenames appear after the scan. If results are still populating, let the scan finish instead of repeatedly removing and re-adding the folder.

2.3 Use Rescan All Now when the index is stale

If the folder is already configured but recent files are missing, return to Tools > Options > Indexes > Folders and use Rescan All Now. This requests a fresh scan of configured folder indexes.

Use this before forcing a rebuild of every index. It is more targeted and directly addresses an Everything index not updating for a FAT32 or exFAT folder.

Success means the newly created test file appears after the rescan. At that point, stop troubleshooting and review the update schedule only if the problem returns later.

3. Check Settings That Can Omit the Drive or Its Results

If the drive has been added correctly, inspect settings that can hide or omit its files. This is especially important when Everything results are missing only in one saved configuration or portable installation.

3.1 Review exclusions and result omissions

Open Everything's options and inspect the exclusion settings. Look for the affected drive letter, volume path, folder name, file extension, or wildcard pattern. An exclusion added for a backup disk can continue to apply after Windows reuses that drive letter for a different device.

Also check any result-omission feature or search expression that excludes paths. A negative path term, macro, bookmark, or filter can make an indexed file invisible without removing it from the underlying index.

Test with the default Everything filter and an exact filename. If the item appears after disabling a relevant exclusion or omission rule, re-enable any unrelated protections and keep only the necessary correction.

3.2 Check portable settings and multiple Everything installations

Portable-app users may have more than one Everything executable and configuration file. You might add the drive in one copy while searching in another. Check the executable path, shortcut target, window title, and configuration location. Close duplicate instances temporarily so you know which profile is being tested.

Command-line options in a shortcut or startup script can also select a different instance, configuration, database, or server. Inspect the shortcut's Target field and remove only options you understand to be related to the problem. Preserve a copy of the original target before editing it.

Success means the same instance that contains the folder-index configuration returns the test file.

3.3 Distinguish local indexes from an Everything server

Everything can be configured to query another Everything instance rather than relying only on local indexes. If you are using an ETP or HTTP-based search setup, the server must index the FAT32 or exFAT drive. Adding the drive to a client computer does not automatically add it to the server's index.

Test the file directly on the computer running the server. If it appears there but not on the client, investigate the client connection, server permissions, address, port, and firewall scope. If it does not appear on the server, add the drive to the server's folder indexes.

Do not expose an Everything search service directly to the public internet merely to solve this issue. Keep access limited to trusted networks or use an appropriately secured remote-access method.

4. Check Drive Letters, Permissions, and Account Context

Folder indexes refer to paths. Removable storage is especially vulnerable to path changes because Windows may assign a different drive letter when devices are attached in another order.

4.1 Correct a changed removable-drive letter

Suppose Everything was configured to scan E:\, but Windows now mounts the same device as F:\. The old folder index points to a path that is unavailable or belongs to another device.

Open Disk Management and confirm the current drive letter. You can either update the folder index to the new path or assign the device a stable letter that is unlikely to collide with other removable devices. If you change a letter, also review backup jobs, scripts, shortcuts, and applications that reference the old path.

Success means the configured folder path opens in File Explorer and the test filename appears after a rescan.

4.2 Verify that the active account can read the drive

FAT32 itself does not provide NTFS-style file permissions, but access can still be affected by device encryption, security software, share permissions, application sandboxing, or the account under which Everything is running. For exFAT removable media, also confirm that the volume is mounted and unlocked before Everything starts scanning.

If Everything runs as a service or under another account, that context may not see the same mapped drives or authenticated network shares as your interactive desktop. Windows drive mappings are commonly specific to a user session. Use a UNC path for an appropriate network folder index when possible, and make sure the account performing the scan has legitimate read access.

Success means the relevant account can open the indexed path and list its files. If File Explorer cannot read the location in the same context, fix access or connectivity before changing Everything settings.

4.3 Handle startup and disconnected removable storage

A removable disk may be absent when Everything starts. Confirm that the folder index remains configured, reconnect the drive, and trigger Rescan All Now. If the drive is routinely connected after sign-in, configure a suitable folder-rescan schedule rather than expecting NTFS-style instant journal updates.

For a portable Everything setup stored on the same removable drive, allow the drive to finish mounting before launching the application. Avoid running multiple startup copies that load different settings.

5. Configure Updates for Non-NTFS Folder Indexes

Adding a FAT32 or exFAT folder once solves initial discovery, but continued accuracy depends on rescanning. Unlike local NTFS journal monitoring, folder indexing generally detects changes through scheduled or manual scans.

5.1 Choose a practical scan schedule

In the Folders index options, review the available update or rescan controls for the configured path. Choose a frequency based on how often the drive changes:

• Use more frequent scans for a small, actively edited work drive.
• Use less frequent scans for a large archive that rarely changes.
• Use manual rescans for media that is connected only occasionally.
• Avoid aggressive scanning if it noticeably affects a slow USB device or network appliance.

The right schedule balances fresh results against I/O load. Everything cannot return a file that has not yet been discovered by a folder scan.

5.2 Understand what scheduled updates can and cannot do

A scheduled rescan is not a repair for an inaccessible path. If the drive letter changed, the share is disconnected, or the scanning account lacks access, repeated scans will not solve the underlying problem. First make the configured path readable, then rescan it.

Success means files created between scans appear after the next scheduled run. If immediate discovery is essential, manually run Rescan All Now after making major changes.

6. Use Targeted Diagnostics Before a Full Rebuild

If folder indexing is configured but Everything search is not working as expected, collect evidence before resetting the application.

6.1 Use the status bar and syntax tests

Search for the unique test filename, then search for part of its parent folder name. Next, restrict the query to the expected path using Everything's path-search features or select Match Path and enter enough of the full path to identify it. These tests distinguish a missing index entry from a filename-query mistake.

Observe the status bar for result counts and indexing activity. If the exact filename produces zero results but neighboring files from the same drive appear, the folder index may simply need a rescan. If no files from the path appear, verify the configured folder and exclusions.

6.2 Inspect debugging information carefully

Everything provides diagnostic and debugging facilities that can help reveal inaccessible paths, scan activity, configuration loading, or connection problems. Enable debugging only long enough to reproduce the issue, then review messages associated with the affected drive or folder. Debug output can contain local filenames and paths, so redact sensitive information before sharing it.

If your release exposes an Index Journal or similar index-change view, use it to inspect relevant index activity, but do not assume an NTFS journal will exist for FAT32 or exFAT. The core diagnostic question is whether the folder scan opened the path and enumerated its contents.

6.3 Use Force Rebuild only after targeted checks

A force rebuild can be useful when multiple known entries remain inconsistent after path, filter, exclusion, and rescan checks. However, it is broader than necessary for most FAT32 cases and may temporarily remove searchable results while indexes are recreated.

Before using Force Rebuild, confirm that the FAT32 or exFAT root is actually present in the Folders list. Rebuilding cannot index a location that was never configured. Prefer Rescan All Now for a stale non-NTFS folder.

7. Run a Clean Temporary Test Before Changing Many Settings

If the behavior remains unexplained, test with a temporary clean Everything profile or a separate portable copy from the official source. Do not overwrite your working configuration. Close the normal instance, start the temporary copy with isolated settings, add only the affected drive under folder indexing, and search for the unique test file.

This test separates application configuration from Windows-level access. If the clean profile finds the file, the original profile likely contains an exclusion, filter, alternate instance setting, server configuration, or command-line option. Compare settings methodically instead of deleting the original database or configuration.

If the clean profile also fails, verify that the temporary instance can open the drive path, confirm the file system and current drive letter, and inspect security software logs. Antivirus or endpoint controls may block unusual removable-media access, but do not disable security tools permanently. Use approved exclusions only when logs clearly identify a false positive and organizational policy permits the change.

Success means the clean instance indexes and returns the test filename. Stop there, preserve the result, and compare one settings category at a time with the original profile.

8. Quick Fix Checklist

1. Confirm the drive is FAT32 or exFAT in File Explorer properties.
2. Create a uniquely named harmless test file on the affected drive.
3. Set the active filter to Everything and clear restrictive search options.
4. Open Tools > Options > Indexes > Folders.
5. Add the current drive root, such as E:\, if it is missing.
6. Confirm the removable drive letter has not changed.
7. Use Rescan All Now and allow the scan to complete.
8. Review folder-index update scheduling for future changes.
9. Check exclusions, result omissions, saved filters, and path restrictions.
10. Confirm you are using the intended local, portable, or server instance.
11. Verify that the scanning account can read the path.
12. Try a clean temporary profile before forcing a complete rebuild.

As soon as the unique test file appears and newly created files show up after the expected rescan interval, the issue is resolved. Further changes create risk without adding value.

9. Frequently Asked Questions

9.1 Why does Everything index NTFS but not my FAT32 drive automatically?

Everything is exceptionally fast on NTFS because it can use NTFS metadata such as the Master File Table and change journal. FAT32 and exFAT lack those NTFS structures. Their contents therefore need to be added and scanned through folder indexing.

9.2 Does the Everything service make FAT32 indexing automatic?

Not by itself. The service helps Everything perform certain indexing operations and run with suitable access, but it does not turn FAT32 into NTFS or automatically add every removable drive as a folder index. You still need to configure the relevant path.

9.3 Why are old FAT32 files visible but new files are missing?

The existing folder index is probably stale. Run Rescan All Now, then review the folder's scheduled update settings. Also make sure the drive has the same letter used by the configured index.

9.4 Will Force Rebuild fix an unlisted FAT32 drive?

No, not if the drive was never added under folder indexing. First add the drive in the Folders tab. Use a targeted rescan before considering a complete rebuild.

9.5 Why can File Explorer find the file when Everything cannot?

File Explorer browses the currently mounted folder directly. Everything searches its own filename index. This is also different from Windows Search, which uses Microsoft's separate indexing and search system. A file can exist and be accessible in Explorer while remaining absent from Everything until its folder index is scanned.

9.6 Can Everything index an exFAT NAS share or mapped drive?

Everything can folder-index an accessible share regardless of the NAS device's underlying file system, but the scanning account must be able to reach it. Mapped drives may not exist in a service account's session, so an accessible UNC path is often more dependable. Scan speed and update frequency will depend on network and NAS performance.