Everything Folder Index Not Updating: How to Fix It

When an Everything folder index is not updating, existing files may remain searchable while newly added files never appear, deleted files stay in the results, or renamed folders continue to show their old names. This usually points to a folder-index monitoring or rescanning problem rather than a general failure of voidtools Everything. Common causes include a disabled folder index, an interrupted network scan, insufficient permissions, an overflowing change buffer, exclusions, search filters, a different Windows account context, or startup settings that prevent Everything from reaching the folder.

This guide focuses specifically on folder indexing, which Everything can use for network shares, mapped drives, portable storage, and file systems that are not indexed through the NTFS Master File Table. It does not focus on NTFS USN Journal troubleshooting. Everything is also separate from Windows Search, so rebuilding the Windows Search index normally will not repair stale Everything folder results.

1. Confirm the Symptom With a Small Safe Test

Before changing settings, verify that you are testing the folder index you think you are testing. A controlled test distinguishes a genuinely stale index from a hidden result, an active filter, or a search query that does not match the file.

1. Open the indexed folder in File Explorer.
2. Create a harmless text file with a distinctive name, such as everything-folder-test-8472.txt.
3. Open Everything and clear the search box completely.
4. Set the Search menu filter to Everything, or select the equivalent all-results filter in your interface.
5. Search for the exact distinctive filename.
6. Rename the file, search for the new name, and then delete it.

A healthy folder index should eventually show the addition and rename, then remove the deleted entry. The exact delay depends on the folder's monitoring and update interval settings. If the results become correct after waiting for the configured interval, the index is working and you should stop changing settings. You may only need a shorter update interval.

If the old name remains indefinitely or the new file never appears, run a manual rescan next. If the manual scan fixes all three test operations, the stored folder path and permissions are probably usable. The failure is more likely related to automatic monitoring, the update schedule, a full change buffer, or a temporary network interruption.

2. Check the Folder Index Settings Directly

2.1 Verify That the Correct Folder Is Indexed

Open Everything's Options window and go to the folder indexing page, commonly found under Indexes > Folders. Confirm that the affected folder is listed and that its path is correct. Similar share names, old drive letters, and duplicate mapped drives can make Everything index a different location from the one being edited.

For a mapped drive, compare the indexed path with the path shown in File Explorer. A drive letter can point somewhere different under another account or elevated process. Where practical, a UNC path such as \\server\share\folder is often less dependent on a particular user's mapped-drive session.

Success means the configured path opens the intended folder and the distinctive test file exists at that exact location. If the path is wrong, correct it and allow a scan to complete before making any other changes.

2.2 Run Rescan All Now

Use Rescan All Now on the folder indexing options page. This instructs Everything to scan its configured folder indexes again. Keep Everything running and avoid disconnecting the drive or share while the scan is underway.

After the scan, repeat the addition, rename, and deletion test. If the results now match File Explorer, the database content was stale but the folder remained reachable. Do not immediately force a broader rebuild. First investigate why automatic updates were missed.

If a manual rescan does not find the test file, check the path, exclusions, permissions, connectivity, and account context. Repeatedly rescanning an unreachable folder will not correct an access problem.

2.3 Review the Update Interval

Folder indexing can use periodic rescans because not every file system or remote share provides reliable real-time change notifications. Review the update interval configured for the affected folder. A long interval can look like an update failure even when Everything is behaving as configured.

Choose an interval appropriate to the source. A frequently changing working folder may need a shorter interval, while a large archival NAS share may justify a longer interval to reduce network and storage load. Avoid setting an extremely aggressive interval without considering how long a full scan takes.

Success means a new test file appears within the expected monitoring delay or the selected update interval. Once that happens consistently, stop troubleshooting.

2.4 Enable Rescan on Full Buffer

When folder monitoring is enabled, changes may be collected in a finite buffer. If too many files are created, deleted, moved, or renamed quickly, that buffer can fill before Everything processes every event. This can happen during large file synchronizations, archive extraction, software builds, backup restores, or bulk renames.

Enable Rescan on full buffer for the relevant folder index when the option is available. If the buffer fills, Everything can then rescan the folder instead of leaving the index with missed changes.

To verify the fix, perform a modest batch operation in a test subfolder, wait for processing or the next scan, and compare Everything's results with File Explorer. Do not generate a destructive workload merely to test the setting. If the results stay synchronized after normal high-change activity, no additional changes are needed.

2.5 Check Exclusions and Result Omissions

A file can be present in the index but absent from the current results. Review index exclusions, excluded folders, excluded files, wildcard rules, and any settings that omit hidden, system, offline, or other categories of results. Also clear active filters and search modifiers.

Test with the simplest possible query: search only for the unique filename, with the Search filter set to Everything. If needed, search for part of the name without punctuation. Avoid combining path, extension, date, size, or regular-expression conditions until the basic name search works.

Success means the file appears after removing the filter or exclusion. In that case, the folder index was not stale. Restore only the filtering rules you actually need.

2.6 Review Server and Command-Line Options

If Everything is started by a shortcut, script, scheduled task, launcher, or portable-app manager, inspect how it is launched. Command-line options can select a named instance, load a particular configuration, specify a database location, or change startup behavior. You may be editing one instance's folder settings while searching another instance.

The same issue can occur with Everything's server features. A client may display results supplied by another Everything instance or server rather than the local folder index you just changed. Confirm the instance name, configuration location, database, and server connection in use.

Success means the Options window and search window belong to the same intended instance, and a test file appears there. Do not expose an Everything server directly to the public internet as a troubleshooting measure. Keep access limited to trusted networks and configure authentication and firewall controls appropriate to your environment.

3. Check Windows Access and Storage Conditions

3.1 Test Permissions Under Everything's Account Context

Everything must be able to enumerate the folder and read enough metadata to index filenames. In File Explorer, test access using the same Windows account and elevation context that runs the relevant Everything instance. Being able to open a parent folder does not guarantee permission to enumerate every child folder.

On a network share, both share permissions and NTFS permissions can apply. Ask the storage administrator to confirm that the account has the intended access. Do not grant broad permissions merely to make indexing work.

After correcting a legitimate permission issue, run Rescan All Now. Success means the previously missing test file appears and inaccessible subfolders can be enumerated. If access remains denied outside Everything, resolve that Windows or server permission problem first.

3.2 Check Mapped Drives and Startup Timing

Mapped drives are usually associated with a user session. An elevated application, background task, service, or different user may not see the same mappings. In addition, Everything can start before Windows reconnects a mapped drive, especially on laptops, VPN-dependent systems, and domain networks.

Check whether the mapped drive is connected before Everything scans it. Open the drive in File Explorer, confirm that the share is available, and then run a rescan. If startup timing is the cause, use a reliable UNC path where suitable or arrange for the network connection to become available before the folder scan.

Success means the indexed path remains reachable after sign-in or restart and updates without manually opening the drive first.

3.3 Account for Network Interruptions During a Scan

A brief Wi-Fi drop, VPN reconnection, NAS sleep cycle, server restart, or credential interruption can prevent a scan from completing correctly. Verify that the share is stable, then run Rescan All Now while the connection remains available.

For large shares, allow enough time for the scan to finish. Avoid closing a portable Everything instance, suspending the computer, or disconnecting the network midway through the test. If results become accurate after a stable scan, no database deletion is necessary.

3.4 Consider the File System and Device Behavior

Folder indexing is particularly relevant to non-NTFS volumes, network shares, and locations where Everything cannot use its usual NTFS indexing method. Removable drives may receive different drive letters, and NAS devices may vary in how reliably they report directory changes.

Confirm that the indexed path still identifies the same device after reconnecting it. For removable media, a stable mount arrangement can prevent a saved folder index from pointing to the wrong or absent volume. For network storage with unreliable change notifications, periodic rescans provide a practical fallback.

3.5 Evaluate Firewall and Security Software Carefully

A local firewall or endpoint security product may affect access to a remote share or an Everything server connection. First determine whether the folder itself opens and can be enumerated in File Explorer under the same account. Review security logs and create a narrow, documented exception only when evidence identifies a blocked trusted connection or process.

Do not permanently disable antivirus or firewall protection. A temporary diagnostic test should follow your organization's security policy and should be reversed immediately. If File Explorer also cannot reach the share, troubleshoot Windows networking rather than repeatedly rebuilding Everything's index.

4. Use Everything's Diagnostic Tools Without Guessing

4.1 Watch the Status Bar and Options Pages

The status bar can reveal whether Everything is scanning, loading, or returning a limited result set. The folder options page shows which locations are configured and provides the safest place to trigger a manual scan. Observe the interface before and after creating the test file.

If a scan is active, wait for it to finish. Changing several settings during a long scan makes it difficult to identify the cause. Once the scan completes, search for the exact test filename again.

4.2 Use Force Rebuild Only After Safer Checks

A force rebuild can recreate Everything's indexes, but it should not be the first response. It may take time on large local or network collections, and it will not fix an unreachable share, incorrect path, exclusion, or missing permission.

Consider Force Rebuild after you have confirmed that the path is accessible, filters are clear, exclusions are appropriate, and a normal rescan still produces incorrect results. Keep all indexed locations available throughout the rebuild.

Success means the completed rebuild contains the correct current filenames and subsequent normal changes update as expected. If the rebuilt index immediately becomes stale again, focus on monitoring, buffer, interval, network, or startup behavior.

4.3 Review the Index Journal and Debug Output

Where available in your Everything build, the Index Journal can help show whether additions, deletions, and renames are being recorded. Debug logging can provide more detail about scans, path access, and update activity. Enable diagnostics only long enough to reproduce the safe test, then turn them off to avoid unnecessary log growth.

Look for evidence tied to the affected path and time, such as access failures, disconnected locations, full-buffer behavior, or scans that restart or do not complete. Avoid assuming every warning is relevant. The useful event is the one that corresponds to your controlled filename operation.

4.4 Test Search Syntax Separately From Indexing

A complex query can create the impression of missing results. Clear the search box and search for the distinctive filename alone. Then add path restrictions or other operators one at a time. This identifies the exact search term that removes the result.

If the filename appears with a plain query but disappears with a path expression, verify path spelling, quoting, separators, and whether the query refers to the mapped path or UNC path stored in the index. At that point, indexing is working and further rebuilds are unnecessary.

5. Run a Clean Temporary Test Before Changing Everything

If the cause remains unclear, use a temporary Everything instance or clean profile that does not alter your working configuration. The goal is to index one small test folder and reproduce the update behavior with minimal variables.

1. Create a local test folder containing a few harmless files.
2. Start a separate temporary or named Everything instance using documented instance options.
3. Add only the test folder as a folder index.
4. Use straightforward monitoring and update settings.
5. Create, rename, and delete a uniquely named file.
6. Repeat the test with the affected network or removable folder if the local test succeeds.

If the local folder updates but the remote folder does not, investigate network availability, credentials, permissions, mappings, and remote change behavior. If both work in the clean instance, the original profile likely contains an exclusion, filter, instance mismatch, launch option, or damaged configuration.

Do not copy every old setting into the clean profile at once. Reintroduce settings in small groups and test after each group. Stop when you identify the option that reproduces the problem.

6. Quick Fix Checklist

• Clear the search box and select the Everything filter.
• Create a uniquely named test file in the affected indexed folder.
• Confirm the exact folder or UNC path under the folder index settings.
• Open the path using the same Windows account context.
• Run Rescan All Now and wait for completion.
• Set a practical update interval for the folder's size and activity.
• Enable Rescan on full buffer when bulk changes may overflow monitoring.
• Check folder, file, wildcard, hidden, system, and offline exclusions.
• Verify mapped drives and VPN connections are available before scanning.
• Check whether a shortcut or script starts another instance or configuration.
• Use a stable network connection for a full rescan.
• Review the Index Journal or temporary debug log if the failure persists.
• Try a clean temporary instance before modifying many production settings.
• Use Force Rebuild only after path, access, filters, and rescan checks.

Stop changing settings as soon as additions, renames, and deletions consistently appear within the expected monitoring delay or update interval. Continuing to modify a working configuration can introduce a second problem and obscure the original cause.

7. Frequently Asked Questions

7.1 Why Does Rescan All Now Fix the Results Only Temporarily?

A successful manual rescan proves that Everything can reach and enumerate the folder at that moment. If updates become stale again, automatic monitoring may be unavailable or unreliable, the update interval may be too long, the change buffer may fill, or the network location may disconnect. Enable rescan on full buffer where appropriate and choose a realistic periodic update interval.

7.2 Why Are Deleted Files Still Showing in Everything?

Stale deleted entries usually mean the folder index missed a deletion event or has not completed its next rescan. Confirm that the indexed location is online and run Rescan All Now. If the entry remains, make sure you are viewing the correct instance and that the result does not come from another indexed path containing a file with the same name.

7.3 Why Do New Files Appear but Renames Do Not?

Partial updating can occur when monitoring events are missed during rapid activity or a network interruption. It can also be a search issue if the old name remains in the query. Clear the query, search for both names separately, enable rescan on full buffer, and perform a stable rescan.

7.4 Does Rebuilding Windows Search Fix Everything?

No. voidtools Everything and Windows Search use separate indexing systems. Rebuilding the Windows Search index generally does not update an Everything folder index. Use Everything's folder index settings, rescanning controls, diagnostics, and rebuild option instead.

7.5 Should I Delete Everything's Database?

Not as a first step. A deleted database does not repair a wrong path, missing permission, disconnected share, exclusion, or instance mismatch. Start with a controlled test, Rescan All Now, access checks, monitoring settings, and a temporary clean profile. Use Everything's Force Rebuild function only after those safer checks.

7.6 Why Does Everything Work Locally but Not on My NAS?

The NAS path may be unavailable at startup, require different credentials, use a mapped drive that is invisible to the running account, or provide unreliable change notifications. Confirm the UNC path and permissions, maintain a stable connection during scanning, and configure an appropriate periodic rescan. If a manual rescan consistently works, the issue is more likely monitoring or connectivity than filename search itself.