Everything Attributes Search Not Working: How to Fix It

When an Everything attribute search returns no results, omits known files, or behaves differently from a normal filename search, the problem is usually not the filename index itself. The likely causes are disabled attribute indexing, incorrect attrib: syntax, an active filter, an excluded location, stale index data, a folder or network index limitation, or a mismatch between the Everything instance you configured and the one you are currently using.

This guide focuses specifically on file attributes in voidtools Everything, including hidden, system, compressed, and encrypted attributes. Everything is a separate application from Windows Search. Rebuilding the Windows Search index will not normally repair an Everything attribute query. Start with one known test file, verify each layer in order, and stop as soon as the expected result appears.

1. Confirm the Symptom With a Small Safe Test

Before changing indexing or service settings, determine whether attribute searching is universally broken or only failing for a particular drive, folder, attribute, or Everything instance. A controlled test prevents unrelated files, permissions, and filters from obscuring the problem.

1.1 Create or Select One Known Test File

Create a harmless text file in a local folder that your account can access, such as a folder inside Documents. Give it an unusual name, for example attribute-search-test.txt. Do not use a protected Windows directory for the first test.

Open the file's Properties dialog in File Explorer and select the Hidden checkbox. Alternatively, use an ordinary Command Prompt and run a command such as attrib +h "%USERPROFILE%\Documents\attribute-search-test.txt", adjusting the path if you created the file elsewhere.

In Everything, first search for the exact filename. If the filename itself does not appear, this is broader than an attribute-search problem. Check whether the drive or folder is indexed before investigating attrib:.

If the filename appears, test the hidden attribute with:

attrib:h attribute-search-test.txt

You can also search attrib:h by itself, but including the unique filename makes the result easier to verify. Success means the known file appears. Once it does, stop changing global settings and repeat the same method with the original location or attribute that was failing.

1.2 Understand Attributes Versus File Properties

Windows file attributes are flags maintained by the file system. Common examples include Hidden, System, Read-only, Archive, Compressed, and Encrypted. Everything's attrib: search targets these flags.

Not every item shown in File Explorer's Properties dialog is a file attribute. File ownership, access permissions, document authors, media tags, image dimensions, and many other metadata fields are different properties. Searching attrib: for an owner name or a document tag will not work because those values are not Windows attribute flags.

Attribute letters can also be combined. For troubleshooting, begin with a single known attribute such as attrib:h rather than a complicated expression. This makes it easier to distinguish a syntax mistake from an indexing problem.

2. Check Everything Settings Directly Related to Attribute Results

2.1 Enable Attribute Indexing

Open Everything's Options dialog and inspect the indexing settings for file attributes. Depending on the Everything release and index type, the setting may appear in the general Indexes area or within settings for an indexed volume. Ensure file attributes are included in the database for the location being tested.

Apply the setting and allow Everything to update or rebuild the relevant index. Watch the status bar rather than immediately repeating searches while indexing is still underway. Success means the status indicates indexing has completed and the known attrib:h test returns the hidden file.

Attribute indexing is distinct from indexing names. Everything can find a filename while lacking the indexed attribute information needed to answer an attribute query as expected. That explains the common symptom in which ordinary searches work but hidden, system, compressed, or encrypted searches appear empty.

2.2 Verify the Search Syntax

Use the attrib: search function, followed by the appropriate attribute letter or supported attribute expression. For initial diagnosis, keep the query simple:

• attrib:h tests hidden items.
• attrib:s tests system items.
• attrib:c tests compressed items.
• attrib:e tests encrypted items.

Do not substitute natural-language phrases such as attribute:hidden unless the documentation for your installed build explicitly supports them. Also check for accidental spaces, quotation marks, negation operators, or unrelated terms left in the search box.

Some files can carry multiple attributes. Test each attribute independently before combining conditions. If individual searches work but a combined query does not, the issue is likely the query's logic rather than indexing.

2.3 Clear Active Filters and Result Omissions

An active Everything filter can silently remove the exact files you are trying to find. For example, a filter intended to show documents may omit a hidden folder, a system file, or a file extension not included in that filter.

Switch the Search menu filter to Everything, clear the search box, and then enter only the controlled attribute query. Check whether Match Case, Match Path, Match Whole Word, regular expressions, or other search modes are active. These modes are not inherently wrong, but they can alter a query when combined with a filename or path.

Review any settings that omit results, hide offline items, or exclude system-related locations. Also inspect custom filters for negative terms or path restrictions. Success means the known file appears with the broad Everything filter. If it disappears only under a custom filter, repair that filter instead of rebuilding the index.

2.4 Inspect Exclusions and Indexed Locations

Open the Exclude section in Options and look for excluded folders, files, extensions, hidden items, system items, or wildcard patterns. An exclusion prevents an item from entering the database, so no search expression can recover it from that database.

Confirm that the test drive is enabled in the relevant NTFS, ReFS, or folder-index settings. For a folder index, verify that the exact parent folder is listed and that the folder is currently available. A filename found through one indexed source does not prove that every intended source is configured correctly.

If an exclusion is responsible, narrow or remove only the relevant rule. Avoid removing all exclusions without reviewing them. Success means the test file enters the database and appears in a normal filename search as well as the attribute search.

2.5 Confirm You Are Configuring the Active Instance

Portable-app users and administrators sometimes have multiple copies or named instances of Everything. One instance may run from Program Files, another from a portable folder, and another under a different account. Each can use different configuration and index files.

Check the window title, executable location, instance name, configuration path, and startup shortcut. Command-line options in a shortcut can select an instance, configuration file, database, filter, or initial search. Test by launching the intended executable directly without an old search expression in its shortcut.

Success means the instance whose options you changed is the same instance displaying the results. If the portable copy works but the startup copy does not, compare their settings rather than repeatedly rebuilding both databases.

3. Check Storage, Service, Account, and Network Context

3.1 Verify the Everything Service State

Everything commonly uses its service to access NTFS volume information without requiring the user interface to run with elevated rights. Check the Everything service configuration in Options and confirm the Windows service is installed and running if your setup depends on it.

A stopped or mismatched service may affect volume indexing, but do not assume the service is the cause if normal filename results and attribute updates are current. Restarting the Everything application or its service can be a useful controlled step after configuration changes. Permanently running the interface as administrator is not the preferred universal fix.

Success means the intended local volumes are indexed and a newly changed attribute is reflected after Everything processes the update.

3.2 Consider Account Permissions and Startup Behavior

Everything's index design differs from a traditional content search engine, but account context still matters for folder indexing, mapped drives, configuration files, portable folders, and remote shares. A mapped drive visible in your interactive desktop session may not exist in a service account or elevated session.

If the problem appears only after startup, confirm that the network connection is available before Everything scans the folder. Open the share in File Explorer under the same account running Everything, then refresh or rescan the folder index. Check whether a startup shortcut launches a different instance or configuration.

Success means the location remains available to the relevant process and a known file from that location appears after the folder index completes.

3.3 Treat Network Shares and NAS Folders Separately

Everything can use direct file-system indexing for supported local volumes and folder indexing for locations such as network shares or unsupported file systems. Folder indexing is scan-based and does not behave exactly like local NTFS indexing. Attribute availability can also depend on what the remote file system and network protocol report.

Test the same query against one local NTFS file and one file on the share. If the local test succeeds but the NAS test fails, inspect the folder index configuration, scan completion, credentials, and the attributes reported by Windows for the remote file. Some NAS implementations do not preserve or expose every Windows attribute in the same way as NTFS.

Do not infer an Everything-wide failure from one share. Stop changing local-volume settings once the local test works, and focus on the share's folder index and reported metadata.

3.4 Check Firewall, Antivirus, and Server Configuration Carefully

A firewall usually does not affect attribute searches performed entirely inside a local Everything instance. It becomes relevant when you query an Everything server, use remote administration, or depend on a network share. Verify the applicable private-network rule and server address instead of disabling the firewall.

Security software can block database writes, configuration updates, service communication, or access to a portable application's directory. Review protection history and logs for a specific block. If testing an exception is necessary, make it narrow and temporary. Never disable endpoint protection permanently just to make search work.

If you use an ETP, HTTP, or other Everything server feature, determine where the search is actually executed. Test locally on the server first. If attrib:h fails there, repair the server's index. If it works locally but remote results differ, inspect server options, client query behavior, protocol capabilities, authentication, and the instance serving the request. Do not expose an Everything search server directly to the public internet without appropriate access controls and network protection.

4. Diagnose the Index Before Rebuilding It

4.1 Read the Status Bar and Options Pages

The status bar can reveal whether Everything is indexing, updating, or returning zero results from a completed database. Check the displayed result count and any indexing activity after changing a file attribute.

Review the Options pages for indexed volumes, folder indexes, exclusions, attribute indexing, database location, service settings, and update behavior. Capture screenshots or notes before changing anything. This makes it possible to reverse one change instead of guessing later.

4.2 Compare a Normal Search With an Attribute Search

Use this short diagnostic sequence:

1. Search for the unique test filename.
2. Search for attrib:h.
3. Search for attrib:h attribute-search-test.txt.
4. Remove the Hidden attribute and wait for the index to update.
5. Repeat the combined query and confirm the file disappears.
6. Restore the Hidden attribute and confirm it returns.

This proves not only that Everything has an attribute value, but also that it notices changes. If the initial value works but later changes do not, investigate update monitoring, folder rescan intervals, volume availability, and journal processing.

4.3 Review the Index Journal and Debug Output

If the problem is intermittent, use Everything's available index-journal or debugging facilities to determine whether the file was added, updated, excluded, or removed. Enable diagnostic output only for long enough to reproduce the issue, because verbose logs can grow and may contain filenames or paths that should be handled securely.

A useful diagnostic record includes the time the attribute changed, the full path, the active instance, the query used, and whether Everything was indexing. Success means you can see the relevant update and the result changes accordingly. If the journal shows the update but the query remains wrong, return to syntax, filters, and attribute-index settings.

4.4 Use Force Rebuild Only After Safer Checks

A Force Rebuild can repair a stale or inconsistent Everything database, but it should not be the first action. It will not fix an excluded folder, an unavailable share, a disabled attribute-index option, a wrong instance, or incorrect syntax.

Before rebuilding, confirm the indexed locations and exclusions are correct, enable the required attribute option, and allow ordinary updating to finish. Then use the application's supported Force Rebuild command if the known file still has stale attribute data. Do not manually delete database files as an initial troubleshooting step.

Success means the completed rebuild returns the controlled test file and reflects attribute changes. Once that happens, stop changing options and test the original file set.

5. Run a Clean Temporary Test Before Making Broad Changes

If the main profile contains years of custom filters and portable settings, a temporary clean test can separate a configuration problem from a storage or application problem. Back up the existing configuration first. Use a separate portable copy or named instance supported by Everything, and keep its database and configuration separate from the production instance.

Configure only one safe local test folder, enable attribute indexing, and create the hidden test file. Avoid attaching a large NAS share or changing service ownership during this experiment. If necessary, exit the production interface or use a properly isolated named instance so the test does not overwrite its files.

If attrib:h works in the clean instance, the application and local file system are capable of producing the result. Compare filters, exclusions, indexed locations, command-line options, and attribute settings with the original profile. If the clean test also fails, verify the test file's actual attributes in Windows, confirm the syntax, and collect debug information before escalating the issue.

Do not replace the working production profile immediately. Transfer one verified setting at a time. Success is a repeatable result in both the clean test and the corrected primary instance.

6. Quick Fix Checklist

• Create one local file with a unique name and assign it the Hidden attribute.
• Confirm the file appears in a normal filename search.
• Test attrib:h and then combine it with the unique filename.
• Enable file-attribute indexing for the applicable index or volume.
• Switch the active filter to Everything and clear restrictive search modes.
• Review exclusions, omitted results, indexed volumes, and folder-index entries.
• Confirm you changed the configuration used by the active Everything instance.
• Wait for indexing to finish and watch the status bar.
• Test local storage separately from mapped drives, NAS folders, and remote servers.
• Verify the Everything service and account context when the setup requires them.
• Use logs or the Index Journal to confirm that an attribute change was observed.
• Run Force Rebuild only after settings, syntax, filters, and locations are verified.

Stop troubleshooting when the known test file appears under the expected attribute query and disappears after that attribute is removed. At that point, apply the same comparison to the original files. Continuing to alter unrelated options after a successful controlled test can introduce a second problem.

7. Frequently Asked Questions

7.1 Why Does Everything Find the Filename but Not Its Hidden Attribute?

Name indexing and attribute indexing are separate concerns. The file may be present in the filename database while attribute information is disabled, stale, unsupported for that source, or filtered from the current results. Enable attribute indexing, remove active filters, and test one known local file.

7.2 Does attrib:h Search Hidden Files and Folders?

It searches items carrying the Windows Hidden attribute, subject to the indexed data, search syntax, filters, and exclusions. A folder that merely looks unusual in File Explorer is not necessarily hidden. Confirm its actual attributes in Properties or with the Windows attrib command.

7.3 Why Are Compressed or Encrypted Results Missing?

First verify that Windows reports the Compressed or Encrypted attribute on a known file. Compression inside a ZIP archive is not the same as the NTFS Compressed attribute, and password protection inside an application is not the NTFS Encrypted attribute. Then test attrib:c or attrib:e with attribute indexing enabled.

7.4 Will Rebuilding Windows Search Fix Everything?

No. voidtools Everything maintains its own database and indexing configuration. Windows Search is a separate Windows component. Repair Everything's indexed locations, settings, service, folder index, or database through Everything itself.

7.5 Why Does Attribute Search Work Locally but Not on My NAS?

Local NTFS indexing and network folder indexing use different mechanisms. The NAS may not expose every Windows attribute, the share may be unavailable under the active account, or its folder index may be incomplete. Verify the remote file's reported properties in Windows and confirm the folder scan has finished.

7.6 Should I Delete the Everything Database?

Not as a first step. Check syntax, filters, exclusions, attribute indexing, active instances, and indexed locations first. If the database appears stale after those checks, use Everything's supported Force Rebuild function. That is safer and more informative than manually deleting database files.