Everything Size Search Not Working: How to Fix It

When an Everything size search is not working, the symptom usually falls into one of four categories: the query uses the wrong size syntax, file sizes are not included in the relevant index, some results have unknown sizes, or Everything must retrieve and sort more metadata than expected. Network shares, folder indexes, exclusions, filters, portable settings, and the account running Everything can also affect what appears.

Everything by voidtools is not Windows Search. It builds its own filename index and can read NTFS metadata very quickly, but optional properties such as file size require the correct index settings or additional metadata collection. Follow the checks below in order. Once a small test returns the correct files and size sorting behaves normally, stop changing settings.

1. Confirm the Symptom With a Small Safe Test

Start with a controlled test instead of searching every indexed disk. This reveals whether the problem is syntax, missing metadata, a particular location, or simply the cost of processing a very large result set.

1.1 Create files with known sizes

Create a temporary folder on a local indexed drive. Place several files in it with clearly different sizes, such as a small text file, a file larger than 1 MB, and a file larger than 10 MB. You can copy existing non-sensitive files instead of generating new data.

Open Everything, search for the temporary folder's name, and confirm that its files appear. Then add a size expression. Useful tests include:

• size:>1mb
• size:>10mb
• size:1mb..20mb
• size:empty for zero-byte files

Everything supports size constants such as kb, mb, gb, and tb. A query such as size:>1gb asks for items whose indexed or retrieved size exceeds one gigabyte. Use a colon immediately after size, and do not insert unrelated text inside the expression.

Success means the files with known sizes are included or excluded as expected. If this local test works, the core size function is operational. Focus next on the affected drive, folder index, remote server, filter, or application profile rather than changing global settings.

1.2 Separate filtering from size sorting

A size search and a size sort are different operations. size:>1gb filters results using size metadata. Clicking the Size column sorts the current results, potentially requiring Everything to obtain and compare sizes for many items.

Test them separately. First run a narrow filename or path search and add size:>1mb. Then remove the size expression and click the Size column. If filtering is fast but sorting a broad query is slow, the likely cause is the quantity of results or missing indexed size data, not broken search syntax.

1.3 Check whether the Size column is blank

Enable the Size column in the results view if it is hidden. Blank size cells usually indicate that the size is unknown or not applicable. Folders do not have a simple stored file size like regular files, and calculating their total contents can require substantial work. Offline files, inaccessible paths, disconnected shares, and metadata supplied by a remote Everything instance can also produce unknown sizes.

Do not treat an unknown size as zero. A filter for zero-byte files and a result whose size is unavailable represent different conditions.

2. Check the Everything Settings Directly Related to Size

2.1 Enable Index file size for the affected index

Open Everything's Options and inspect the index page for the source containing the missing files. For an NTFS volume, select that volume under the NTFS index settings and verify that Index file size is enabled when you need consistently fast size filtering and sorting.

Apply the change and allow Everything to update the index. Watch the status bar rather than repeatedly changing settings while indexing is underway. Retest the small local query afterward.

Success means the Size column is populated for ordinary accessible files, size:>1gb returns the expected large files, and sorting a reasonable result set completes normally. At that point, stop. A rebuild or clean profile is unnecessary.

2.2 Inspect every relevant volume or folder index

Settings can differ between indexed sources. Enabling file-size indexing for one NTFS volume does not prove that another volume, a manually added folder index, or a network share is configured the same way.

In Options, identify where the affected path comes from:

• An automatically indexed NTFS volume
• A ReFS volume or another supported source
• A manually configured folder index
• A mapped drive or UNC network path
• An ETP or other remote Everything connection
• A file list created earlier

Review the selected source rather than assuming a global option covers it. If results from drive C have sizes but results from a NAS share do not, the difference is almost certainly source-specific.

2.3 Understand the cost of folder size indexing

File size indexing concerns the sizes of individual files. Folder size indexing is different because Everything must aggregate the contents beneath each folder and maintain those totals as files change. On a large tree, removable drive, or NAS, this can consume additional indexing time, memory, storage, and network activity.

Enable folder size indexing only if your workflow genuinely requires searchable or sortable folder totals. If your objective is simply to find files larger than 1 GB, indexing individual file sizes is the relevant setting. Turning on folder size calculations may make the interface appear slower without improving that query.

Success for folder sizes means totals eventually appear and stabilize after indexing finishes. If file searches already work and you do not need folder totals, leave folder size indexing off and stop troubleshooting that aspect.

2.4 Clear filters and result omissions

An active filter can silently narrow the result set. Switch to the Everything filter and clear the search box before entering a controlled size query. Also inspect any configured result omissions, exclusions, or exclude filters that could hide the target path or file type.

For example, a custom filter limited to documents can make a correct size:>1gb search appear incomplete if the large files are disk images or archives. Likewise, an excluded backup folder will remain absent regardless of its files' sizes.

Success means the expected files appear after selecting the Everything filter or temporarily removing the relevant exclusion. Restore intentional exclusions afterward and adjust only the rule responsible for the omission.

2.5 Compare local and server-provided results

If you connect to another Everything instance, the remote server determines what metadata is indexed and returned. A locally enabled size option cannot add missing size information to remote results. Test the same query directly on the server, if you administer it, and check the server's index settings.

Keep Everything servers restricted to trusted networks and authenticated configurations appropriate to your environment. Do not expose a file-search service directly to the public internet merely to test it.

If the query works on the server but not the client, review the connection, client query, filters, and server capabilities. If it fails on both, correct the server-side index first.

2.6 Check command-line and portable settings

A shortcut, script, or command-line launch can open Everything with a different configuration, search expression, instance name, database location, or server connection. Compare the shortcut's Target field with a normal launch from the installed application.

Portable copies are especially easy to confuse. Each copy can have its own INI file and index. Confirm that you are changing Options in the same executable and instance that displays the faulty results. Closing one window and launching the intended executable directly is a useful check.

Success means both the normal interface and your shortcut or script return the same size results. Once they agree, correct the shortcut or automation rather than rebuilding a healthy index.

3. Check Windows, Storage, and Account Context

3.1 Verify service state and privileges

Everything commonly uses the Everything Service to access NTFS indexing information without requiring the user interface to run as administrator. In Everything's Options, verify that the service configuration matches your intended setup. You can also check Windows Services for its state.

Restarting a stopped service is reasonable, but first note whether Everything reports indexing activity or an access problem. Avoid repeatedly switching between service mode and running the interface as administrator, because that can obscure which configuration actually solved the issue.

Success means the indexed local volume becomes available, its file count stabilizes, and the controlled size query returns expected results under your normal Windows account.

3.2 Check network-share identity and availability

Mapped drives belong to a Windows logon context. A drive mapped in your interactive session may not exist for a service, scheduled task, elevated process, or different account. When practical, test the share using its UNC path, such as \\server\share, and verify that the account performing folder indexing can read it.

Open the affected directory in File Explorer under the same account. If Windows cannot enumerate it or read file properties, Everything cannot reliably collect sizes either. Reconnect the share and confirm permissions before forcing an index rebuild.

Success means the share is reachable, newly created test files become visible after the configured update cycle, and their sizes are populated. If the source is slow but accurate, reduce the scope of the folder index instead of repeatedly rescanning the entire NAS.

3.3 Account for file-system differences

Everything's exceptionally fast local indexing is closely associated with NTFS metadata and the change journal. A network share, FAT or exFAT removable disk, and other sources may be handled through folder indexing or another mechanism. Those sources can update more slowly and may require periodic rescanning.

Check the file system in the drive's Windows properties, then examine how that source is listed in Everything's Indexes options. Do not assume NTFS-specific behavior applies to a NAS or removable disk.

3.4 Review security software without disabling protection permanently

Security software can block database writes, service operation, configuration files, or access to protected folders. Look for a specific alert, quarantine event, or blocked-access record involving the signed Everything executable, service, database, or intended indexed path.

If your organization permits it, create a narrowly scoped allow rule only after confirming the block. Do not permanently disable antivirus or firewall protection. For a remote connection, verify that the required application and network profile are allowed only on trusted networks.

4. Use Everything's Diagnostics Before Rebuilding

4.1 Read the status bar and index state

The status bar can show result counts and indexing activity. If Everything is scanning a large folder index or rebuilding metadata, size results may remain incomplete until that operation finishes. Wait for activity to settle, then repeat the same test query.

A constantly changing count suggests an update is still underway. A stable count with missing files suggests an exclusion, inaccessible source, stale index, or incorrect instance rather than ordinary indexing delay.

4.2 Check the Index Journal

Use the Index Journal when you need to determine whether Everything observed a file-system change. Create or copy a harmless test file into the affected location, wait briefly, and look for the corresponding update.

If the journal records the file but its size remains unknown, focus on size-property indexing or metadata retrieval. If the change never appears, investigate the source index, update schedule, service, permissions, or journal availability.

4.3 Run focused syntax comparisons

Use pairs of queries that isolate one factor at a time:

• path:"C:\TestSize" followed by path:"C:\TestSize" size:>1mb
• size:>1gb with the Everything filter selected
• A filename-only query before and after sorting by Size
• The same query on a local volume and an affected network source
• The same query in the graphical interface and your normal shortcut

Record which comparison changes the result. This is more useful than changing several unrelated options and being unable to identify the fix.

4.4 Use debug logging for repeatable failures

If a specific operation consistently fails, enable Everything's diagnostic or debug output using the official troubleshooting procedure for your installed release. Reproduce the problem once, then inspect the output for access failures, unavailable volumes, connection errors, or configuration-path differences.

Logs may contain filenames, paths, server names, and search terms. Remove sensitive information before sharing them. Disable extra logging after the test so it does not create unnecessary noise or storage use.

4.5 Use Force Rebuild only after safer checks

A forced rebuild can correct a genuinely stale or inconsistent index, but it also creates avoidable work on large disks and network folders. Before using it, confirm that you opened the correct Everything instance, checked the source settings, cleared filters, verified access, and allowed pending indexing to finish.

If those checks pass and new files or size changes still do not enter the index, use the Force Rebuild control for the affected index. Let it complete without changing more options. Retest the same known files afterward.

Success means the expected files and sizes appear after the rebuild and continue updating when a test file changes. Do not delete the database manually if the built-in rebuild resolves the problem.

5. Run a Clean Temporary Test

A clean temporary test distinguishes a damaged or conflicting profile from a system-wide problem. It should not overwrite your normal database or configuration.

1. Download Everything only from the official voidtools website.
2. Use a separate portable folder that does not contain your existing INI or database.
3. Close other Everything windows to avoid confusing instances.
4. Launch the temporary copy and configure only one small local test source.
5. Enable file-size indexing for that source.
6. Run the known-size tests and sort a narrow result set by Size.

If the clean instance works, your Windows file metadata and the basic Everything size feature are functional. Compare the old and temporary configurations, especially filters, exclusions, indexed sources, server connections, instance names, and size-indexing options.

If the clean instance fails on the same local NTFS test, investigate service access, file-system health, security events, and diagnostic output. Keep the temporary test isolated and remove it when finished. Do not replace the working profile until you understand which setting differs.

6. Quick Fix Checklist

1. Test a known local folder with size:>1mb or size:>1gb.
2. Confirm that ordinary filename results from the folder appear.
3. Select the Everything filter and clear unintended query modifiers.
4. Check the Size column for blank or unknown values.
5. Enable Index file size for the affected source.
6. Wait for indexing to finish and watch the status bar.
7. Check exclusions, result omissions, and custom filters.
8. Identify whether results come from NTFS, a folder index, NAS, file list, or server.
9. Verify share access under the account or service performing the indexing.
10. Compare a normal launch with portable, scripted, or command-line launches.
11. Use the Index Journal or diagnostic output for a repeatable update failure.
12. Force a rebuild only after the safer checks fail.
13. Use a separate clean portable profile as the final isolation test.

Stop as soon as the controlled query returns the correct files, their sizes are populated, and a new test file updates normally. Further changes can introduce a second problem into an already working setup.

7. Frequently Asked Questions

7.1 Why does size:>1gb return no results?

The most common causes are that no indexed file actually exceeds 1 GB, file sizes are not indexed for that source, an active filter or exclusion hides the files, or the source reports unknown sizes. Test the query against a known large local file and confirm that its Size column is populated.

7.2 Why is sorting by size slow when searching is fast?

Everything can find filenames quickly while still needing to retrieve or compare size metadata for a large number of results. Narrow the query before sorting and enable file-size indexing for the affected source. Sorting millions of broad results will naturally require more work than sorting one folder.

7.3 Why are folder sizes blank or inconsistent?

Folders do not have a single stored length equivalent to a file's size. Their totals must be calculated from their contents and maintained as those contents change. Folder size indexing can be expensive, particularly across large trees and NAS shares. Enable it only when required and allow indexing to complete.

7.4 Why do local files have sizes while NAS files do not?

Local NTFS volumes and network folder indexes use different update and metadata paths. A NAS may be offline, inaccessible to the indexing account, slow to scan, excluded, or configured in another Everything instance. Verify the UNC path, permissions, folder-index settings, and update state.

7.5 Does Everything use the Windows Search index?

No. Everything maintains its own index and is configured separately from Windows Search. Rebuilding the Windows Search index will not normally repair Everything size filtering. Use Everything's Indexes options, service status, journal, and built-in rebuild controls instead.

7.6 Should I delete the Everything database?

Not as a first step. Check syntax, filters, size indexing, sources, permissions, instance identity, and indexing activity first. If evidence points to a stale index, use Everything's built-in Force Rebuild. Manual deletion can discard useful state and cause an unnecessary full reindex.