Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
When Everything returns no result for a file you know exists, check the search query and filter first, then verify that the file’s location is indexed. Local NTFS volumes normally use the Everything Service (or the documented elevated-indexing setup); non-NTFS volumes, individual folders, network shares, and mapped drives must be added as folder indexes. Let an initial scan finish before judging the index, and use Tools > Options > Indexes > Force Rebuild only after the likely cause has been eliminated.
Start with the search itself
Everything indexes file and folder names. It is not a full-text content search engine, so a word that appears only inside a document will not produce a result unless that word is also part of the file name or path. Test with a distinctive part of the actual name, such as invoice-8472, rather than a sentence from the document.
Confirm the active filter
Look at the filter control in the search window and select the normal Everything filter. A filter can deliberately limit results to a file type, folder, or other pattern; an unintended filter can make a healthy index look empty. If you recently searched for a particular extension or folder, switch back to the normal filter before changing any index settings.
Turn off restrictive matching options temporarily
In the search options, make sure these settings are not enabled unintentionally:
#1 Best Overall
- Match Case — a capitalization difference can exclude an otherwise matching name.
- Match Whole Word — a partial filename will not match when only complete words are allowed.
- Match Path — this changes whether directory names are considered in the match.
- Match Diacritics — accented and unaccented characters may be treated differently.
- Enable Regex — ordinary text can behave like a regular expression and return nothing or unexpected results.
After clearing those restrictions, search for a short, unmistakable fragment of the filename. Try the same fragment without punctuation or an extension if the exact spelling is uncertain. If that still fails, move on to the location and index checks below. Changing the query first prevents a perfectly healthy index from being mistaken for a permissions or disk problem.
Identify where the missing file lives
The correct fix depends on the storage location. Use the path shown in File Explorer to classify it before changing settings. A drive letter alone does not tell you whether the target is a local NTFS volume or a mapped network location, so inspect the path and the drive’s file-system type.
| Location | How Everything normally finds it | What to check first |
|---|---|---|
| Local NTFS volume | Native NTFS indexing through the Everything Service or the documented administrator-indexing configuration | Service status, included volume, and change monitoring |
| Non-NTFS local volume | Folder indexing | The path is listed under Options > Folders and its first scan is complete |
| A single local folder | Folder indexing | The exact folder (or a parent folder) has been added |
| UNC network share | Folder indexing | The share is added and reachable with the account running Everything |
| Mapped network drive | Folder indexing, with user-session visibility | Run Everything as a standard user, then restart it so the mapping is visible |
Folder indexing is not equivalent to native NTFS indexing. The official guidance describes it as slower, and the first scan can take a few minutes. Files in a folder-indexed location cannot be searched until that initial scan has completed. A location can therefore be configured correctly and still return no result for a short period while its first scan is in progress.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use the location type to choose the troubleshooting branch: NTFS settings for an internal Windows volume, or folder settings for an external file system, selected directory, share, or mapped drive. Do not expect a Force Rebuild to add a location that was never configured.
Fix missing files on an NTFS volume
Most internal Windows disks use NTFS. Everything can obtain the names on those volumes through its service while the main interface runs as a normal user.
Check that the Everything Service is available
- Open Everything and go to Tools > Options.
- Open the service or NTFS-related settings and confirm that the Everything Service is enabled and running, if your installation uses the service.
- Restart Everything after changing the service setting, then search for the distinctive filename again.
Voidtools describes the purpose of the service this way: “The Everything service allows Everything to quickly index NTFS volumes and monitor NTFS volumes for changes without running Everything as administrator.” This design lets the user interface remain a standard-user application while the service performs the NTFS indexing work. It is generally the cleaner arrangement when several local users need filename results without giving the main program elevation.
Confirm that the volume is included
- In Tools > Options, open NTFS (the exact page can vary by Everything version).
- Check that the drive containing the file is listed for indexing and is not excluded.
- If the disk was recently connected or assigned a new drive letter, verify that the listed volume corresponds to the current drive.
- Apply the change and allow the index to update before testing.
An empty result can also occur when change monitoring is disabled or not functioning. The official FAQ recommends checking change monitoring when expected files produce no results. With monitoring active, newly created, renamed, or deleted names can be reflected without waiting for a complete manual rebuild. If an existing file is found but a recently renamed file is not, monitoring deserves particular attention.
Use administrator indexing only when it is the documented alternative
Some Everything configurations index NTFS through an elevated process instead of the service. Follow the administrator-indexing procedure documented for the version you installed; do not assume that running the entire application as administrator is a universal fix. Elevation changes which network locations are visible and can make mapped drives disappear, as described in the next section. The service approach is specifically intended to provide NTFS indexing while allowing the interface to remain a standard-user process.
Add non-NTFS folders, shares, and drives
Everything does not receive native NTFS change notifications for every storage type. Add these locations explicitly as folder indexes. This includes a folder on a removable disk, a volume formatted with another file system, a UNC share, and a path reached through a mapped drive.
Add a folder index
- Open Tools > Options.
- Select Folders.
- Choose the command to add a folder and browse to the exact local folder, network share, or mounted non-NTFS location.
- Apply the settings and leave Everything running while it scans.
- Wait for the initial scan to finish, then test a filename that is definitely in that location.
The first scan may take a few minutes. Until it finishes, the contents are not searchable. The scan can also be slower than native NTFS indexing, so a large external disk or share may take noticeably longer than an internal NTFS volume. Avoid interpreting an empty result during this window as proof that the folder is inaccessible.
Check network access separately from indexing
Adding a share does not bypass Windows permissions. Confirm that the account running Everything can open the folder in File Explorer and enumerate its contents. If File Explorer cannot reach the path, correct the network connection or permissions first; Everything cannot index names it cannot read. Test the exact share and subfolder you added, because access to one directory does not necessarily establish access to every directory beneath a server.
Recommended Free Tools
Make mapped drives visible
Mapped drives are tied to a user session and elevation level. A mapping created for a standard user may not exist in an administrator session. If a mapped drive is absent from the folder picker or returns no results:
- Exit Everything completely.
- Start it as the same standard user who created the mapped drive; do not use Run as administrator for this test.
- Open Tools > Options > Folders and add the mapped path again if necessary.
- Restart Everything after the mapping is available and wait for the folder scan.
The options guidance warns that mapped network drives may not be visible when Everything runs as administrator, while the folder-indexing guidance recommends standard-user execution in that situation. If the mapping is unreliable, add the UNC path directly when your network permissions allow it; the share still needs to be reachable by the account indexing it. Changing elevation without changing the mapped-drive session can make a previously visible path appear to vanish.
Understand permissions without over-elevating
There are two different permissions questions: can Everything obtain a list of names, and can you open the files? The Everything Service can provide any local user with a list of NTFS filenames. It cannot provide access to the file contents themselves. Therefore, a filename appearing in results does not grant permission to read, copy, or modify that file.
For privacy-sensitive computers, this distinction matters: indexing metadata and granting content access are separate operations. Keep the service approach when possible, and grant users access to the underlying folders only when they are supposed to open the files. Elevating the whole application can introduce visibility problems for mapped drives without solving a content-permission denial.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Recognize a permissions symptom
- File Explorer opens the path, but Everything returns nothing: the location may not be indexed, the scan may be pending, or the process may be running in a different user/elevation context.
- Everything lists the name, but opening it fails: indexing is working; Windows file permissions, encryption, offline status, or the share connection is the separate issue.
- A mapped drive exists in File Explorer but not in Everything: compare the user and elevation level used by both applications, then run Everything as the standard user and restart it.
Do not use a successful filename listing as evidence that the service has opened the file. The service’s role is to supply names from NTFS volumes; normal Windows access checks still apply when you open the path. Conversely, a denied file-open operation does not prove that indexing failed if the name is already present in the result list.
When the index is stale, rebuild it
Rebuilding is a repair step, not the first response to every missing result. First verify the query, location type, inclusion, service, permissions, and initial scan. If the index still appears stale, use the documented rebuild command:
- Open Tools > Options.
- Select Indexes.
- Choose Force Rebuild and confirm.
- Keep Everything open while the index is recreated, and wait for indexing to complete before searching.
A rebuild refreshes the database from the locations configured for indexing; it does not automatically add an unlisted drive, repair a disconnected share, or grant access to a protected folder. Recheck those conditions if the same path remains absent after the rebuild. Rebuilding before correcting an absent folder entry simply recreates an index that still has no knowledge of that location.
Check the disk when folders are corrupt
The troubleshooting guidance notes that corrupt files and folders are automatically excluded. If only one directory or disk consistently omits names, check that affected disk for errors using the operating-system disk-check tools appropriate to your Windows edition. Back up important data before repairs, and do not interrupt a repair operation on a disk that is showing signs of failure. A clean rebuild cannot restore names from folders that Windows itself cannot read reliably.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use this decision path for an empty result list
- Test the query: select the Everything filter, remove unintended matching options, and search for a distinctive partial filename.
- Classify the path: decide whether it is local NTFS, another file system, a normal folder, a UNC share, or a mapped drive.
- For NTFS: confirm the Everything Service (or the documented administrator-indexing setup), include the volume under Options > NTFS, and check change monitoring.
- For other locations: add the exact path under Options > Folders, then wait for the first scan to finish.
- For mapped drives: close Everything, run it as the standard user who owns the mapping, restart it, and add the path again if required.
- For a stale established index: run Tools > Options > Indexes > Force Rebuild and wait for completion.
- For persistent omissions: check the affected disk for errors and verify that the account can enumerate the folder in File Explorer.
This order separates query errors from configuration errors and configuration errors from storage failures. At each stage, retest with a known filename in the same path. If the result appears after one stage, stop there rather than making broader permission or administrator changes.
Version and interface caveats
Some service and folder-indexing options are marked by voidtools as requiring Everything 1.5. If a menu item in this guide is missing, check the version shown in your installation and use the matching official documentation. Labels and placement can change between releases, but the diagnostic distinction remains the same: native NTFS indexing is handled differently from folder indexing, and a first folder scan must finish before its contents can be searched. Verify the interface wording for your installed release instead of assuming that a setting with a similar name has identical behavior.
Do not infer content-search capability from a successful filename result. Everything’s index is built around file and folder names and paths; searching text inside a document requires a separate content-indexing or application search feature. A document containing the word you typed is not enough unless that word also appears in its name or path.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What each fix can and cannot solve
| Action | Solves | Does not solve |
|---|---|---|
| Clear restrictive search options | A query that excludes an existing indexed name | A drive or folder that was never indexed |
| Enable the Everything Service | Native NTFS indexing and change monitoring without elevating the main app | Permissions to open file contents or an unconfigured network share |
| Add a folder under Options > Folders | Non-NTFS volumes, selected folders, shares, and mapped paths after scanning | Instant results before the initial scan completes |
| Run as a standard user | Visibility of user-session mapped drives that disappear under elevation | Access to a share the account cannot browse |
| Force Rebuild | A stale or damaged index database for already configured locations | Missing location configuration, disconnected storage, or disk corruption |
| Check the disk for errors | Some omissions caused by corrupt files or folders being excluded | Incorrect filters, absent folder indexes, or denied network access |
Prevent the problem from returning
- Keep the normal Everything filter selected unless you intentionally need a narrower filter.
- When adding an external or network location, add its exact folder and wait for the first scan before relying on search results.
- Keep the Everything Service enabled for NTFS volumes when your security policy permits it, so changes can be monitored while the interface remains a standard-user process.
- Avoid launching Everything elevated by habit; compare the user context whenever a mapped drive behaves differently.
- After changing drive letters, reconnecting storage, or replacing a share path, revisit the corresponding NTFS or folder-index settings.
- If a disk begins producing inconsistent listings, back up important data and investigate disk errors rather than repeatedly rebuilding the index.
The reliable order is query, location, indexing method, user context, scan completion, and only then rebuild. Following that order fixes the common causes without trading away mapped-drive visibility or granting broader permissions than necessary.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Frequently Asked Questions
Does Everything search inside document contents?
No. Everything indexes file and folder names and paths. A word that appears only inside a document will not match; use a filename or path fragment, or a separate content-search feature.
Best Value
Why is a mapped drive visible in File Explorer but missing in Everything?
Mapped drives belong to a user session and elevation level. Exit Everything, run it as the same standard user who created the mapping, restart it, and add the mapped path under Options > Folders. You can use the UNC path directly if that account can reach the share.
How long should folder indexing take?
The initial scan may take a few minutes, and folder indexing is slower than native NTFS indexing. Files in that location cannot be searched until the first scan finishes.
Should I always run Everything as administrator?
No. The Everything Service is designed to index NTFS volumes while the main program runs as a standard user. Running elevated can make mapped network drives disappear, so use administrator indexing only when it is the documented setup for your version.
What does Force Rebuild fix?
Tools > Options > Indexes > Force Rebuild recreates the index for locations already configured. It does not add an unlisted drive or folder, reconnect a share, grant permissions, or repair disk corruption.
Can the Everything Service open files that a user cannot access?
No. The service can provide local users with a list of NTFS filenames, but it cannot provide access to file contents. Seeing a name in results does not grant permission to read, copy, or modify it.
What if only one folder or disk keeps omitting files?
After checking the query and index configuration, check the affected disk for errors. Corrupt files and folders can be automatically excluded, and rebuilding will not restore data that Windows cannot read reliably.
The Bottom Line
Start with the query and Everything filter, then classify the path. Use the Everything Service and included-volume checks for NTFS; add other locations under Options > Folders and wait for the initial scan. Run Everything as the standard user for mapped drives, reserve Force Rebuild for a stale configured index, and investigate disk errors when omissions persist.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
