Everything Folder Size Not Calculating: How to Fix It

When Everything displays blank folder sizes, calculates them very slowly, or appears to calculate forever, filename indexing may still be working correctly. Folder size calculation is a separate task from finding file and folder names. The most likely causes are disabled folder size indexing, on-demand calculation waiting on a large directory tree, inaccessible network storage, exclusions, a mismatched account or instance, or a user interface setting that prevents the expected values from appearing. The steps below isolate those causes without immediately deleting the database or making broad Windows changes.

1. Confirm the Symptom With a Small Safe Test

Start by determining whether folder sizes fail everywhere or only on a particular drive, share, or directory. This distinction prevents unnecessary rebuilding and helps separate an Everything configuration problem from a storage or permissions problem.

1.1 Create a Controlled Local Test Folder

Create a temporary folder on a local NTFS drive that Everything already indexes. Place two or three small files inside it, wait briefly for Everything to notice the changes, and search for the folder by its exact name. Make the Size column visible if it is hidden.

Then select or sort the results in the way your build uses to request folder sizes. Some Everything configurations maintain indexed folder sizes, while others calculate sizes when the Size column, a size-related search, or a size sort requires them.

The test has three useful outcomes:

• If the local test folder receives a plausible size, calculation works and the original location is the problem.
• If its size remains blank, inspect folder size options and the active Everything instance.
• If it calculates only after a delay, on-demand calculation works but may be expensive on larger trees.

Success means the test folder shows a nonblank, reasonable total and updates after adding or removing a test file. Once that happens, stop changing global settings and troubleshoot only the affected drive or share.

1.2 Verify That File Search Still Works

Search for a known file in the same location. If filenames appear immediately but folder sizes are blank, this is specifically a folder size issue, not a general case of Everything search not working. Everything primarily locates names through its own indexes and, for supported local file systems, file system metadata. Windows Search uses a different indexing system and can index properties or file contents. Repairing or rebuilding Windows Search normally does not fix folder sizes in Everything.

If neither files nor folders appear, investigate the volume index, folder index, exclusions, active filters, service, and account context before concentrating on sizes.

2. Check Folder Size Calculation and Index Settings

2.1 Check the Folder Size Indexing Option

Open Everything Options and inspect the Indexes pages for a folder size indexing setting. The exact wording and location can vary by Everything build. If an option such as Index folder size is available and disabled, enabling it allows Everything to maintain folder totals instead of calculating every requested value from scratch.

After enabling it, allow indexing to finish. Watch the status bar or index status rather than repeatedly restarting the application. Test the small local folder again before opening a huge directory.

Success looks like folder sizes becoming available consistently, including after a restart, and size sorting no longer waiting on every folder. Stop changing settings when that behavior is stable.

2.2 Understand On-Demand Folder Size Calculation

On-demand calculation walks through the files and subfolders below a result when a size is requested. It can be appropriate when you inspect only a few folders and do not want the ongoing memory, database, or update cost of maintaining all folder totals.

A blank value can simply mean that calculation has not been requested, has not reached that result, or cannot traverse part of the directory tree. Display the Size column and request a size sort or other supported size operation. Keep the result set narrow during testing.

Do not begin with the root of a system drive, a user profile containing cloud placeholders, or a large NAS share. Use one known folder. If the small folder calculates and a multi-million-file tree does not finish promptly, the feature works but the workload is too large for convenient on-demand use.

2.3 Treat Sorting by Folder Size as an Expensive Operation

Sorting by name can use information Everything already has. Sorting by folder size may require totals for every matching folder before the final order is known. A broad query can therefore trigger extensive traversal even when individual folder results normally appear instantly.

Reduce the work before sorting:

1. Limit the search to one drive or parent folder.
2. Use Everything's folder-only search syntax or a folder filter.
3. Exclude unrelated system, backup, or archive trees from the test query.
4. Request the Size column or size sort only after the result count is manageable.

Success means a narrow result set completes while a broad one merely takes longer. In that case, there is no broken filename index. Either narrow future size reports or enable folder size indexing if your build and workload support it.

2.4 Check Filters, Exclusions, and Omitted Results

An active filter can hide folders while still showing files, and an exclusion can prevent a tree from entering the relevant index. Reset the search filter to an unfiltered state, clear the search box, and inspect the Exclude page under Options. Also review any result omission feature available in your build.

Do not permanently remove intentional exclusions just to obtain folder totals. Temporarily test one safe path, then restore the original rule if it protects private, noisy, or high-churn locations.

If the folder appears only after resetting a filter or omission, size calculation was not the first failure. Success is the expected folder returning to results and then receiving a size through indexing or on-demand calculation.

3. Check the Active Index, Service, and Instance

3.1 Confirm That You Changed the Correct Everything Instance

Portable-app users and power users often run more than one named instance, executable, configuration file, or database. A setting changed in one instance will not repair the window connected to another. This can also explain why an option seems to revert after restart.

Check the application path, instance name, startup shortcut, command-line arguments, and configuration location. If Everything is launched by a script or shortcut, inspect it for options that select another instance, configuration, database, server, or startup mode.

Success means the same instance opens after restart with the folder size setting retained and the same indexed locations visible. Once confirmed, avoid copying configuration files between instances until testing is complete.

3.2 Verify the Everything Service and Account Context

The Everything service helps the application access local file system metadata without requiring the desktop program to run with full administrative rights. Confirm in Everything Options and Windows Services that the intended service is installed and running if your setup relies on it.

Service health alone does not guarantee access to network shares. Windows services often run under accounts that do not have the same mapped drives or network credentials as the signed-in user. A desktop instance may see a mapped drive while a service or server process cannot.

Restarting the service is reasonable after a configuration or account change, but do not repeatedly restart it while an index operation is legitimately progressing. Success means the local indexed volumes appear in Everything and continue updating when a test file is created.

3.3 Review Folder Indexes and Server Connections

Non-NTFS locations, network shares, and selected paths may be included through folder indexing rather than the same mechanism used for local NTFS metadata. Open the Folder indexes page and verify that the affected path is present, enabled, reachable, and scheduled to update appropriately.

If your Everything client receives results from another Everything server, confirm that the server is reachable and that the server-side instance has access to the underlying files. A remote result can contain a name without giving the client permission to enumerate every descendant needed for on-demand size calculation.

Keep file-search servers limited to trusted networks and authenticated or otherwise appropriately protected environments. Do not expose an Everything server directly to the public internet merely to test folder sizes.

4. Check Network, Removable, and File System Conditions

4.1 Test Network Shares Using the UNC Path

Mapped drive letters belong to a Windows logon context. A share mapped as a drive for your interactive account may not exist for an elevated application, service account, scheduled task, or different user. Test the share using its UNC path and confirm that the account running the relevant Everything component can list the folder and its descendants.

Open the folder in File Explorer under the same account context and verify that representative subfolders are accessible. A permission denial deep inside the tree can make an on-demand total incomplete or leave calculation waiting on retries and network timeouts.

Success means the UNC-based folder index updates and a small network test folder receives a size. If local tests work but the share does not, do not rebuild all local indexes. Focus on credentials, share permissions, connectivity, and the folder index for that share.

4.2 Account for NAS Latency and Large Trees

A NAS may answer a filename query quickly while taking much longer to enumerate every file below hundreds or thousands of directories. Sleeping disks, snapshots, high latency, offline nodes, and many tiny files can make folder size calculation look stuck.

Test a shallow NAS folder first. Then increase the scope gradually. Avoid sorting the entire share by size as the first diagnostic action. If small folders work and time rises with tree size, the bottleneck is traversal cost rather than missing results.

For recurring NAS reports, consider maintaining folder size indexing where practical or using storage reporting tools supplied by the NAS. For occasional checks, narrow on-demand calculations are often safer and cheaper.

4.3 Check Removable Drives and File System Type

Removable drives can change letters, disconnect, enter sleep states, or be absent when Everything starts. Confirm the drive is online, has the expected letter or path, and appears in the appropriate volume or folder index page. Reconnect it before forcing any rebuild.

NTFS volumes can be indexed differently from FAT, exFAT, optical media, Linux file systems exposed through another layer, and network shares. A location not handled by Everything's local NTFS indexing usually needs a folder index or another supported indexing method. Folder sizes also require readable descendants regardless of file system type.

Success means Everything finds a newly created test file on that device after the configured update process and can calculate its small parent folder.

4.4 Review Security Software Without Disabling It Permanently

Endpoint protection can slow repeated directory enumeration or block an executable, database location, network path, or server connection. Check security logs for a specific block that matches the time of the failed calculation. If policy permits, use a narrow, temporary test or a vendor-approved exclusion limited to the verified Everything executable or data path.

Do not disable antivirus or firewall protection permanently. For client-server setups, allow only the required application or port on trusted network profiles and limit access to expected hosts. Success is a repeatable calculation with a documented, minimal security rule.

5. Use Built-In Diagnostics Before Rebuilding

5.1 Watch the Status Bar and Options Pages

The status bar can reveal whether Everything is indexing, sorting, querying, or displaying an unexpectedly large result set. Options pages show which volumes and folder indexes are enabled. Compare those facts with the path that is failing.

Wait for active indexing to complete before judging a newly enabled folder size option. If progress continues and disk or network activity is expected, restarting may only discard useful work.

5.2 Use Focused Search Syntax Tests

Use the folder-only operator supported by Everything, such as folder:, together with a distinctive folder name or path. Then restrict the query to the affected drive or parent. The objective is not to create a complex query but to prove that the folder result exists before requesting its size.

Remove size conditions during the first test. A size-based condition may omit folders whose totals are not yet available, which can look like Everything results missing. Add the size condition only after the Size column contains a value.

5.3 Inspect Debug Output and the Index Journal

If the basic checks do not explain the issue, enable Everything's supported debug logging or debug console temporarily. Reproduce one small calculation and look for access denied messages, unreachable paths, repeated retries, database errors, or a connection to an unexpected instance.

If your build provides an Index Journal or similar index-change view, inspect it for updates to the test folder. A recorded create or modify event confirms that Everything is receiving index changes even if the aggregate folder total has not updated as expected.

Turn verbose logging off after collecting the evidence. Logs can grow and may contain filenames or paths that should be handled as sensitive information.

5.4 Use Force Rebuild Only After Safer Checks

Force Rebuild can be appropriate when an enabled index is clearly stale, test changes never appear, or diagnostics indicate inconsistent index data. It should not be the first response to slow NAS traversal or disabled folder size indexing.

Before rebuilding, verify the correct instance, enabled volume or folder index, exclusions, connectivity, and available disk space. Trigger the rebuild from Everything's Options interface, allow it to finish, and retest one folder. Do not manually delete the database first.

Success means the test file and folder appear, updates are recorded, and the folder total becomes available. If a fresh rebuild produces the same network-only failure, another rebuild is unlikely to help.

6. Run a Clean Temporary Test

When many settings have changed over time, create a temporary clean Everything profile or named instance instead of altering the working configuration repeatedly. Keep the normal database intact. Configure only one small local test location and, if needed, one small network test location.

1. Launch the clean profile using the documented portable or named-instance method for your installation.
2. Confirm that its configuration and database paths are separate from the normal instance.
3. Enable the minimum required local volume or folder index.
4. Enable folder size indexing if available, or request one on-demand calculation.
5. Compare the result with the normal profile.

If the clean profile works, the cause is likely a filter, exclusion, instance argument, stale configuration, or index setting in the normal profile. Compare settings methodically rather than replacing everything at once. If both profiles fail only on the same share, investigate that share and its account context.

7. Quick Fix Checklist

• Test one small folder on a local indexed drive.
• Show the Size column and request calculation for a narrow result set.
• Enable folder size indexing if available and appropriate for the workload.
• Reset active filters and inspect exclusions or omitted results.
• Confirm the affected volume or folder index is enabled and current.
• Verify that you are editing the same Everything instance you use.
• Check the Everything service without assuming it can access mapped drives.
• Use a UNC path and verify network permissions under the relevant account.
• Avoid sorting an entire NAS or system drive by folder size during diagnosis.
• Review debug output before using Force Rebuild.
• Use a temporary clean profile before making multiple permanent changes.
• Stop once a small test updates reliably and isolate remaining work by location.

8. Frequently Asked Questions

8.1 Why Are File Sizes Visible but Folder Sizes Blank?

A file's size is stored as file metadata. A folder's total size normally has to be derived by adding the files below it, potentially across many nested directories. Everything can know the names and individual file sizes while still lacking a completed aggregate for the folder. Enable folder size indexing where available or request an on-demand calculation for a narrow set of folders.

8.2 Why Does Everything Freeze When I Sort by Folder Size?

It may be calculating totals for every folder in the current results before it can establish the final order. Narrow the search to one drive or parent path, use a folder-only filter, and then sort. If this is a frequent task, folder size indexing may provide a better experience, subject to its resource cost.

8.3 Why Do Local Folder Sizes Work but NAS Sizes Do Not?

The NAS may require slower recursive enumeration, and the Everything service or server may not have your interactive user's credentials. Test a small UNC path, verify permissions for the actual process account, and confirm that the share is included in a folder index. Network latency and inaccessible descendants can also delay or prevent a complete total.

8.4 When Is Folder Size Indexing Not Worth the Cost?

It may not be worthwhile when you rarely inspect folder totals, index very large or high-churn trees, use slow removable media, or access a NAS where continuous rescanning creates unwanted load. In those cases, calculate sizes on demand for tightly scoped results. Indexing is more attractive when you sort folders by size frequently and need immediate, repeatable totals.

8.5 Will Rebuilding the Windows Search Index Fix Everything?

Usually not. Everything and Windows Search use different indexing systems. Rebuilding Windows Search may help Start menu, File Explorer, content, or property searches handled by Windows, but it does not normally repair Everything's volume indexes, folder indexes, filters, service, or folder size calculations.

8.6 Should I Delete the Everything Database?

Not as a first step. Check folder size options, the active instance, indexed locations, filters, exclusions, service state, permissions, and network access first. Use Everything's Force Rebuild command if there is evidence that the index is stale or inconsistent. Manual database deletion removes diagnostic context and may create unnecessary reindexing without addressing the real cause.