Everything Hidden System Files Not Showing: How to Fix It

When hidden or system files do not appear in voidtools Everything, the cause is usually not the Windows Explorer visibility setting. Everything builds and searches its own filename index, so Explorer's Show hidden files option does not determine what Everything can display. The most likely causes are an active filter, an attribute-related search, an exclusion rule, incomplete folder indexing, a service or account-context problem, or insufficient permission to scan a non-NTFS location.

The troubleshooting steps below move from safe, reversible checks to more disruptive repairs. After each change, repeat the same controlled search. Once the expected test file appears, stop changing settings. This prevents a successful fix from being obscured by several unrelated configuration changes.

1. Confirm the Symptom With a Small Safe Test

Before changing Everything's configuration, verify exactly what is missing. A known test file helps distinguish an indexing problem from a search-query problem, a permissions issue, or an application that simply cannot open the result.

1.1 Create known hidden and system test files

Create a temporary folder in a location that Everything normally indexes, such as a folder under your user profile. Do not perform this test in Windows, Program Files, or another protected directory.

1. Create a folder named EverythingAttributeTest.
2. Inside it, create three empty text files named normal-test.txt, hidden-test.txt, and system-test.txt.
3. Open Command Prompt and apply the attributes with attrib +h "C:\path\EverythingAttributeTest\hidden-test.txt" and attrib +s "C:\path\EverythingAttributeTest\system-test.txt".
4. In Everything, search for normal-test.txt, hidden-test.txt, and system-test.txt separately.

Use the real folder path in place of the example. Applying the system attribute to a disposable test file is safer than changing attributes on an operating-system file.

If all three names appear, Everything is indexing hidden and system entries. The original problem is probably caused by the original query, a filter, a path restriction, or confusion between finding and opening a file. If only the normal file appears, inspect exclusions and indexing settings. If none appear, confirm that the test location is indexed at all.

1.2 Separate filenames from file access

Everything can sometimes show a filename even when the current Windows account cannot open the file. Conversely, a file may be accessible through another application while absent from Everything because its volume or folder was never indexed.

Right-click a result and try opening its containing path. If the filename is listed but Windows denies access, search is working and the remaining issue is Windows permissions. Do not rebuild the index for an access-denied message. If the filename is absent, continue with the indexing and filtering checks below.

2. Check Everything Settings Directly Related to Missing Results

2.1 Clear the query and active filters

An active filter is one of the easiest causes to overlook. A Documents, Audio, Executables, or custom filter can remove valid results even when the filename matches. Select the broad Everything filter from the Search menu, then clear the search box and enter only the exact test filename.

Also remove search modifiers such as path restrictions, regular-expression mode, whole-word matching, case matching, and attribute tests. If the file appears after selecting the Everything filter, indexing is healthy. Stop troubleshooting and correct or disable the restrictive filter.

2.2 Test attribute search syntax correctly

Everything supports attribute-based searches through the attrib: search function. Common attribute letters include h for hidden and s for system. For example, attrib:h searches for entries carrying the hidden attribute, while attrib:s targets the system attribute. A combined test can be written according to the search behavior supported by the installed Everything release, or the two searches can be run separately to avoid ambiguity.

Attribute-specific searching depends on file attributes being available to the index. Open Everything's indexing options and look for the file-attribute indexing setting. The exact page layout can differ between stable and alpha builds, so use the option's label rather than assuming every installation has an identical menu arrangement. Enable attribute indexing if it is off, allow the index to update, and rerun attrib:h or attrib:s.

Success means the known test file appears in both a plain filename search and the corresponding attribute search. If it appears by name but not with attrib:, focus on attribute indexing rather than rebuilding unrelated volume indexes.

2.3 Inspect hidden and system exclusions

Open Tools, Options, Indexes, and inspect the Exclude page or similarly named exclusion controls. Look for settings that exclude hidden files and folders, system files and folders, specific paths, wildcard patterns, or regular expressions. A broad exclusion can hide far more than intended.

Temporarily disable only the rule that could match the test path. Do not remove a long exclusion list without recording it. If the file appears, refine the offending rule so it excludes only the intended content.

Check parent folders as well. Excluding a folder normally removes everything beneath it, regardless of each child's individual attributes. A hidden file inside an excluded directory will remain absent even if hidden-file indexing itself is allowed.

2.4 Check omitted results and custom filters

Some Everything configurations or builds can omit results temporarily or through saved rules. Review result-omission controls, custom filters, bookmarks, and macros that may be applied to the current search. Start a plain search from an empty query rather than reusing a saved search.

If resetting to an unrestricted search restores the file, there is no need to modify the service, permissions, or database. The omission or custom search rule is the complete explanation.

2.5 Confirm the correct volume or folder is indexed

Everything can index local NTFS volumes efficiently from the NTFS metadata. Other file systems and network locations generally require folder indexing or another supported indexing method. Open the Indexes pages and confirm that the drive, folder, mapped location, or share containing the missing file is included.

For a folder index, verify that the displayed path still exists and points to the intended location. Drive-letter changes, disconnected removable disks, altered NAS share names, and portable installations moved between computers can leave an old path in the configuration.

Success means the target location is listed, available, and produces current results after an update. If only one share or removable disk is affected, avoid rebuilding healthy local NTFS indexes.

2.6 Review server and command-line restrictions

If you connect to another Everything instance through an ETP, HTTP, or other supported server interface, troubleshoot the server's index and search settings rather than only the client. The client can display only the results supplied by the server. Check whether the same filename appears when searching directly on the server computer.

Portable shortcuts, scripts, and launchers may also pass command-line options that select a different configuration, instance name, database, search, filter, or index behavior. Start Everything directly from its executable without the usual launcher. If results return, compare the shortcut's Target field and startup script with the official command-line documentation.

Do not expose an Everything server directly to the public internet merely to test connectivity. Keep testing inside a trusted network or use an appropriately secured remote-access method.

3. Check Windows Access and Storage Context

3.1 Compare the service and user account context

On local NTFS volumes, the Everything service can provide the access needed to read filesystem metadata without running the full interface as an administrator. Open Everything's options and verify that the service is installed and running if your setup relies on it.

If the service is stopped, restart it through the supported Everything option or Windows Services management console. Then check Everything's status area for indexing activity. Running the interface as administrator can be a useful diagnostic comparison, but it should not become the automatic long-term solution when the service is the intended configuration.

If results appear only under a different account or elevated session, investigate service state, folder permissions, and configuration location. Different Windows accounts may load different Everything settings, filters, and folder indexes.

3.2 Verify permissions for folder indexes

Folder indexing requires the indexing process to enumerate the target path. Confirm that the relevant account can list the folder and its subfolders. Test this by navigating to the path in File Explorer or using dir from the same account context.

Permission inheritance can differ for hidden or system-marked folders, although the attributes themselves are not access-control permissions. Check the folder's Security properties if enumeration fails. Grant only the access genuinely required by your environment, and do not take ownership of protected system folders simply to make search results appear.

3.3 Reconnect mapped drives and NAS shares

Windows services run in a different session and may not see drive mappings created interactively for a user. A mapped drive visible as Z: in Explorer may therefore be unavailable to a service. Where supported, configure folder indexing with a UNC path such as \\server\share\folder and credentials appropriate for the indexing context.

Confirm that the share is online before Everything starts its scan. NAS sleep, VPN timing, Wi-Fi delays, and startup scripts can make a path unavailable during application launch. Reconnect the path and trigger an index update. If current files then appear, the problem was path availability rather than hidden attributes.

3.4 Consider file system type

NTFS metadata indexing and folder indexing behave differently. FAT32, exFAT, many removable devices, Linux-backed shares, and NAS locations do not provide the same NTFS metadata source. Ensure such locations are configured as folder indexes or through another method supported by your Everything installation.

Do not assume that seeing the drive in Explorer means Everything automatically indexes it. Explorer browsing and Everything indexing are separate operations.

3.5 Check firewall and antivirus only when relevant

A firewall is relevant mainly when a client communicates with an Everything server. Confirm that the required connection is allowed on the trusted network and that the server is listening on the expected interface. Do not disable the firewall permanently.

Security software may interfere with an executable, configuration file, database file, or network connection, but this is less common than filters and exclusions. Review the product's event history or quarantine first. If testing an exception is necessary, make it narrow and temporary. Restore protection after the test.

4. Use Everything Diagnostics Without Destroying Useful State

4.1 Read the status bar

The status bar can reveal the number of indexed objects, the number of matching results, and whether Everything is scanning or updating. Search for the exact filename and compare the result count before and after each change.

A zero-result query with a healthy, stable object count suggests a search restriction or missing indexed location. A rapidly changing count suggests indexing is still underway. Wait for activity to settle before judging the fix.

4.2 Review the Options pages systematically

Check one category at a time: active filters, indexed volumes, folder indexes, exclusions, attribute indexing, service configuration, and server settings. Record the original value before changing it. Screenshots are useful when troubleshooting a production workstation or shared administrative tool.

This controlled approach makes the result reproducible. Once the test file appears, retain the successful change and revert unrelated experiments.

4.3 Use Force Rebuild only after targeted checks

A force rebuild can repair an index that is stale or inconsistent, but it should follow the safer checks above. Rebuilding cannot fix an active filter, an excluded path, unavailable network credentials, or a command-line option that loads the wrong configuration.

If the correct location is enabled, the service is healthy, and known changes are not entering the index, use the Force Rebuild control in the relevant indexing options. Allow the process to finish. Success means both the controlled test file and recently changed real files appear afterward.

4.4 Inspect the Index Journal and debug output

Where available in your installed build, the Index Journal can help determine whether Everything noticed a filesystem change. Debug output can also reveal failed folder scans, unavailable paths, access errors, and startup options.

Use the diagnostic controls documented for your exact release. Avoid copying undocumented command-line switches from random forum posts. Logs can contain usernames, paths, server names, and filenames, so redact sensitive details before sharing them.

5. Run a Clean Temporary Test Before Changing More Settings

If the normal profile still omits hidden or system files, run a temporary clean test. Exit the existing instance first, preserve the current configuration, and start a separate portable or named instance according to the official documentation. Configure only one safe local test location.

Create the same normal, hidden, and system test files. Search by exact name first, then test attrib:h and attrib:s after enabling attribute indexing if required.

• If the clean instance finds every file, the original profile contains a filter, exclusion, omission, or stale configuration.
• If both instances fail on one location, examine that location's indexing method, permissions, and file system.
• If plain searches work but attribute searches fail, inspect attribute indexing rather than general indexing.
• If local files work but NAS files fail, focus on folder indexing, credentials, startup timing, and share availability.

Do not delete the existing database or configuration before this comparison. A clean temporary instance provides the same diagnostic value while preserving rollback options.

6. Quick Fix Checklist

1. Select the unrestricted Everything filter and clear the query.
2. Search for one exact, known filename without modifiers.
3. Confirm Explorer's hidden-file display setting is not being treated as an Everything setting.
4. Test a disposable normal file, hidden file, and system file in the same indexed folder.
5. Enable file-attribute indexing if attrib:h or attrib:s searches are required.
6. Check hidden, system, path, wildcard, and regular-expression exclusions.
7. Review omitted results, custom filters, bookmarks, and saved searches.
8. Confirm the correct NTFS volume or folder index is enabled.
9. Verify that folder indexes and network shares are accessible in the indexing account context.
10. Check the Everything service if the installation relies on it.
11. Start the executable without a portable launcher or custom command line.
12. Use a targeted force rebuild only after configuration and access checks pass.
13. Run a clean temporary instance before deleting any database or configuration.

Stop as soon as the controlled test succeeds and the original missing files appear. Additional changes after success make it harder to identify the real cause.

7. Frequently Asked Questions

7.1 Does Show hidden files in File Explorer control Everything?

No. File Explorer's visibility setting controls what Explorer displays. Everything uses its own index, filters, exclusions, and search syntax. Changing Explorer's setting may help you inspect a path manually, but it does not instruct Everything to include hidden or system entries.

7.2 Does Everything normally find hidden and system files?

Everything can index and find them when the containing location is indexed and no exclusion or filter removes them. Attribute searches additionally require attribute information to be present in the index. Installation-specific settings can change the observed behavior.

7.3 Why does attrib:h return nothing when the filename appears?

The most likely explanations are that attribute indexing is disabled, the file does not actually have the hidden attribute, or another active query component is restricting the result. Verify the attribute with the Windows attrib command, simplify the query, and check Everything's attribute-indexing option.

7.4 Why can Everything find a file but not open it?

Finding a filename and opening the file are different operations. Everything's index can contain an entry while Windows access-control rules prevent the current user from reading it. Check the file or parent folder's permissions instead of rebuilding the search index.

7.5 Why are hidden files missing only from a NAS?

A NAS is normally handled as a folder or network index rather than a local NTFS metadata index. Verify the share path, credentials, availability, folder-index settings, and whether a service can see the user's mapped drive. Also check whether the NAS exposes Windows hidden and system attributes consistently through its file-sharing protocol.

7.6 When should I force a rebuild?

Use Force Rebuild after confirming that the correct location is indexed, the path is accessible, filters are cleared, exclusions are correct, and the service is working. Rebuild when the index remains stale or misses a known file despite those checks. Do not rebuild first, because it cannot correct a restrictive configuration.