Everything Audio Video Picture Filter Wrong: How to Fix It

When an Everything audio, video, or picture filter returns the wrong files, omits expected media, or appears to stop working entirely, the cause is usually narrower than it first seems. In voidtools Everything, the built-in audio:, video:, and pic: macros primarily identify files by extension. They do not automatically inspect every file's contents or understand its media type from metadata. Unexpected results therefore commonly come from an extension that is absent from a filter, an active search option, an incomplete index, an exclusion, a folder or network-share indexing problem, or a customized filter definition.

This guide focuses specifically on the built-in media filters in Everything for Windows. It starts with safe tests that separate filter problems from indexing problems, then covers local disks, folder indexes, mapped drives, portable installations, services, command-line settings, and metadata searches. Change one item at a time and stop as soon as a controlled test produces the correct result.

1. Confirm the Symptom With a Small Safe Test

Before rebuilding an index or changing Windows services, determine exactly what Everything can and cannot find. A small test folder provides a known set of files and avoids drawing conclusions from a large, changing media collection.

1.1 Create a controlled media test

Create a folder on an indexed drive, such as C:\EverythingMediaTest. Copy one ordinary file of each media type into it, using familiar extensions such as MP3, MP4, and JPG. Do not rename unrelated files to media extensions because the built-in filters work from extensions and would treat those renamed files as media.

In Everything, search for the folder name first:

• EverythingMediaTest

If the folder and its files do not appear, the immediate problem is indexing, scope, exclusion, or permissions rather than the media macros. If they do appear, test each macro while limiting the search to the folder:

• EverythingMediaTest audio:
• EverythingMediaTest video:
• EverythingMediaTest pic:

Success means that the MP3 appears under audio:, the MP4 under video:, and the JPG under pic:, without unrelated test files. If this controlled test succeeds, stop changing global index settings. The original problem is probably an unsupported extension, an additional search term, or the location of the missing files.

1.2 Compare the macro with an explicit extension search

Search for a missing file by its exact filename. Then test its extension directly with syntax such as ext:flac, ext:mkv, or ext:webp. Finally, compare that result with audio:, video:, or pic:.

If an exact filename search and an ext: search find the file but the media macro does not, Everything has indexed the file correctly. The macro's extension list is the likely issue. Do not rebuild the index in this situation because rebuilding cannot add an extension to a filter definition.

2. Check the Filter and Search Options Directly Related to the Problem

Everything separates indexing from filtering. The index determines which file and folder names are available to search. A filter or macro narrows those indexed names. Confirm the active filter and search options before investigating Windows itself.

2.1 Reset to the Everything filter

Open the Search menu and select the general Everything filter. This removes an accidentally selected Audio, Video, Pictures, Documents, or custom filter from the result set. Clear the search box and verify that ordinary indexed files return.

Next, enter only one media macro, such as audio:. Avoid combining it with other words until it works alone. A query such as audio: live requires both the audio filter and the word live to match. The second condition may be what removes the expected file.

Success means the broad Everything filter displays normal results and each media macro works when used by itself. Once this happens, add the original terms back one at a time. Stop when you identify the term or option that changes the result unexpectedly.

2.2 Review match options

Options in the Search menu can alter the meaning of a query. Depending on how the original search was written, case matching, whole-word matching, path matching, regular expressions, or diacritic matching may narrow the results. Disable options that are not intentionally part of the test, then repeat the simple macro search.

Regular-expression mode deserves special attention. Search text that behaves normally in a standard Everything query may be interpreted differently when regex mode is active. Likewise, matching the full path can include directory names in the comparison and produce results that seem unrelated when only the filename is being inspected visually.

2.3 Understand extension-based media matching

The built-in media macros classify files according to their extensions. They do not guarantee that a file contains valid audio, video, or image data. A damaged MP3 can still match audio:, while a valid media file with an uncommon or missing extension may not match at all.

This explains two common symptoms:

• A seemingly wrong file appears because its extension belongs to the media filter.
• A legitimate media file is missing because its extension is not included in that filter definition.

Check the complete filename, including the extension. Windows File Explorer can hide known extensions, which makes a file such as cover.jpg.tmp look misleading at a glance. Everything's Name and Extension columns can help reveal what is actually indexed.

2.4 Check customized filter definitions

If audio:, video:, or pic: behaves differently from another Everything installation, inspect the filter definitions available through the Search menu's filter-management or organization command. A built-in filter may have been edited, or a custom filter may use the same keyboard shortcut or a similar name.

Compare the macro and search definition with a known-good installation when possible. Before editing, record or export the existing definition so it can be restored. Add only the nonstandard extensions your environment genuinely uses. For example, a specialist camera, audio workstation, or archive system may create extensions that are absent from a general-purpose media list.

After saving a change, search for one known file with the added extension. Success means it now appears under the intended media macro while unrelated extensions remain excluded. There is no reason to alter the database after a filter-only fix.

3. Verify the Index, Service, Folders, and Exclusions

If the missing media file cannot be found by exact name or ext: search, investigate the index rather than the media filter. Everything is not Windows Search. Everything maintains its own index and, for local NTFS volumes, can use NTFS file-system information for rapid filename indexing. Changing Windows Search indexing locations does not normally repair an Everything result problem.

3.1 Inspect indexed volumes and the status bar

Open Everything's index options and confirm that the drive containing the missing files is included. Look at the status bar after running a query. It can indicate whether Everything is still scanning, updating, sorting, or processing a demanding search.

Search for the exact parent folder and then the exact filename. If neither exists in the results, confirm that the volume is online and still has the expected drive letter. Removable disks and reassigned drive letters can make a previously valid path disappear.

Success means the exact filename appears without any media macro. At that point, return to the extension and filter checks rather than continuing to change the index.

3.2 Check the Everything service and account context

The Everything service can help the desktop application access local NTFS indexing information without requiring the user interface to run with elevated rights. If indexing changed after an update, reboot, or account switch, inspect the service configuration in Everything's options and confirm the configured service is running.

A service problem is more plausible when an entire local NTFS volume is missing than when only one extension is absent. Restarting the service or application may be a reasonable controlled step, but do not permanently weaken antivirus protection or run every search application as administrator. If the same exact files are indexed correctly after the service is restored, stop there.

3.3 Review folder indexes and file-system type

Network shares, NAS folders, and file systems that are not being indexed through local NTFS mechanisms may need folder indexing. In the folder-index settings, confirm that the path is listed, available, and scheduled or configured to update appropriately.

Folder indexes are scanned rather than updated in exactly the same way as a local NTFS index, so changes may not appear instantly. If an Everything index not updating complaint affects only a NAS or mapped folder, trigger the appropriate folder rescan or update before considering a full rebuild.

Success means a newly created test file on that location appears after the folder index refresh. Then test its explicit extension and media macro in that order.

3.4 Inspect exclusions and omitted results

Review the exclusion settings for excluded folders, files, extensions, hidden items, or system items. A broad path exclusion can silently remove an entire media library. An extension exclusion can create the impression that only one media filter is broken.

Also check any result-omission or hide-result features used in the current profile. If available in your setup, clear temporary omissions and repeat the exact-name search. The safe diagnostic order is to document an exclusion, disable it temporarily, test, and either correct it narrowly or restore it. Do not remove all exclusions permanently without understanding why they were configured.

4. Check Network Shares, Servers, Startup, and Portable Settings

Media searches often expose configuration differences because large libraries are commonly stored on a NAS, searched through an Everything server, or accessed from a portable copy. In these cases, the query can be correct while the connected index is incomplete.

4.1 Confirm mapped drives and network credentials

A mapped drive may exist in one Windows account or logon context but not another. An elevated application can also see a different set of mapped drives from a normally launched application. Open the share in File Explorer under the same account used to run Everything and verify that the test file is accessible.

For UNC paths, verify that the stored credentials still work and that the folder index points to the current server and share name. If the share is temporarily unavailable during startup, the folder index may remain stale until its next update.

Success means Everything can find a newly added, plainly named test file from the share after an index refresh. Only then should you evaluate the media macro.

4.2 Check firewall and security software narrowly

If a client connects to an Everything server and receives no results or an incomplete remote index, verify the server address, port, authentication settings, and whether the server is listening on the intended private interface. Check Windows Firewall or endpoint-security logs for a blocked connection.

Create only the narrow rule required for the trusted local network and the intended executable or port. Do not expose a file-search server directly to the public internet without appropriate network controls, authentication, and a clear security design. Do not disable security tools permanently as a troubleshooting shortcut.

4.3 Compare server-side and client-side searches

Run the exact filename search directly on the machine hosting the index. If it fails there, troubleshoot the host index. If it succeeds on the host but fails on the client, focus on the client connection, server options, query handling, authentication, and the specific index being served.

A remote client may not be searching the same data set as a local Everything window. Confirm the displayed paths and server connection before editing filters. Success means the same known test file appears on both host and client with equivalent searches.

4.4 Review command-line and portable configuration

Everything can be launched with command-line options or separate configuration locations. A shortcut, script, scheduled task, or portable launcher may select a different configuration, database, instance, or startup behavior. This can explain why filters work from one shortcut but not another.

Inspect the shortcut target and startup scripts for extra parameters. Confirm that the portable copy can write to its configuration location and that it is not reading an old or read-only settings file. Compare the active filter definitions and indexed locations with the normally installed copy.

If one launch method works, do not immediately overwrite the failing profile. First identify the relevant difference, such as a separate instance, stale folder index, custom filter, or alternative configuration file.

5. Use Advanced Diagnostics Without Making the Problem Worse

Advanced tools are useful after simple filter and index checks establish where the failure occurs. They should confirm a hypothesis, not create several new variables at once.

5.1 Use search syntax tests as a diagnostic ladder

Test the same known file in this order:

1. Exact filename
2. Exact extension with ext:
3. The relevant audio:, video:, or pic: macro
4. The macro plus the parent folder name
5. The original full query

The first failing step identifies the layer to inspect. Failure at step one indicates an index or scope issue. Failure at step three suggests a filter-definition or extension-classification issue. Failure only at step five means another search term or option is excluding the file.

5.2 Treat metadata tag searches separately

A filename index and a metadata search are not the same operation. Searches involving media properties or tags may require Everything to read file properties from individual files, depending on the installed build and configuration. Reading tags across thousands of files, especially over a NAS, can be much slower than matching filenames and extensions.

First verify that audio: or video: returns the expected extension-based set. Then test a metadata condition against a small folder. Watch the status bar and allow the operation to finish. A slow artist, album, dimension, duration, or similar property search does not prove that the basic media filter is broken.

5.3 Use Force Rebuild only after safer checks

A Force Rebuild can help when an index remains demonstrably stale or inconsistent after the correct volume, service, folder update, and exclusions have been checked. It is not the first fix for a missing extension in a macro.

Before rebuilding, note the active indexed volumes and folders. Run the rebuild from the relevant index options, wait for indexing to complete, and test the controlled folder again. Success means exact-name and extension searches now reflect current files. If the macro still omits only a nonstandard extension, return to the filter definition.

5.4 Review debug logs and the Index Journal

When a repeatable indexing failure remains, enable Everything's debugging facilities only long enough to reproduce it. Look for access failures, unavailable paths, service connection problems, folder-scan errors, or repeated update failures. Avoid publishing logs without reviewing them because paths and filenames can contain sensitive information.

Where an Index Journal is available in the installed configuration, use it to inspect recent index changes and confirm whether a file addition, rename, or deletion reached the index. The goal is to establish whether the file was never indexed, was excluded, or was indexed and then filtered from the visible results.

6. Run a Clean Temporary Test Before Broad Changes

If the voidtools Everything fix remains unclear, compare the current setup with a temporary clean profile or separate portable test. This is particularly useful when long-standing custom filters, command-line options, or migrated settings may be involved.

Back up or record the current configuration first. Launch a separate test instance or portable copy according to the official documentation, using a writable temporary folder and no inherited custom filter changes. Index only a small safe test location where practical. Do not point two instances at configuration or database files in a way that risks conflicting writes.

Repeat the diagnostic ladder: exact filename, ext:, and media macro. If the clean profile works, the Windows files and extensions are valid, and the original profile contains the relevant difference. Compare filters, exclusions, indexed locations, search options, and launch parameters one category at a time.

If the clean profile fails in exactly the same way, look for a shared cause such as an unsupported extension, inaccessible share, security restriction, or misunderstanding of extension-based matching. Stop making profile changes once the controlled result is correct.

7. Quick Fix Checklist

• Reset the Search menu to the general Everything filter.
• Clear the query and test audio:, video:, and pic: separately.
• Search for one missing file by exact name.
• Compare the media macro with an explicit ext: search.
• Confirm the complete extension, including hidden or double extensions.
• Review custom filter definitions for missing nonstandard extensions.
• Disable unintended regex, whole-word, case, path, or diacritic options.
• Confirm the correct volume or folder is indexed.
• Check exclusions and temporarily omitted results.
• Refresh a folder index for NAS, share, or non-NTFS locations.
• Verify the Everything service when an entire local NTFS volume is absent.
• Check mapped-drive visibility under the same Windows account context.
• Compare server-side and client-side exact-name results.
• Inspect shortcut and portable-launch parameters for separate configurations.
• Use Force Rebuild only after proving that the index itself is stale.

8. Frequently Asked Questions

8.1 Why does audio: return a file that is not really audio?

The built-in macro generally classifies files by extension rather than validating their internal contents. A mislabeled, corrupt, or unrelated file with an included audio extension can therefore match. Check the complete filename and verify the file type with an appropriate trusted application.

8.2 Why is a valid media file missing from pic: or video:?

First search for the exact filename, then use ext: with its extension. If those searches work, the extension is probably absent from the macro's filter definition or the active filter has been customized. Add the extension narrowly if it is a genuine format used in your environment.

8.3 Does rebuilding the database repair a wrong media filter?

Not when the problem is the filter's extension list. Rebuilding is relevant only when exact-name searches prove the index is stale or incomplete. If ext: finds the file but audio: does not, inspect the filter instead.

8.4 Why are Everything results missing from a NAS?

A NAS or network share commonly relies on a folder index or remote Everything server rather than local NTFS indexing. Verify share access, account credentials, folder-index updates, exclusions, and server connectivity. Test a new plain text file first to separate access and indexing from media classification.

8.5 Why is a metadata tag search much slower than audio:?

The audio: macro can narrow indexed names by extension, which is fast. A metadata query may need to obtain properties from many individual files. Network latency and large libraries amplify that cost. Test tags within a small folder and let the status bar show whether processing is ongoing.

8.6 How do I know when troubleshooting is finished?

Stop when the known test file appears by exact name, matches its explicit extension, and appears under the intended media macro. Then confirm one real file from the original library. Once both tests succeed, avoid unrelated service, firewall, index, or security changes. A precise fix is safer and easier to maintain than a broad reset.