Everything Bookmarks Not Working: How to Fix It

When Everything bookmarks are not working, the bookmark may open with the wrong query, return no results, preserve an unexpected filter, or appear to do nothing. In voidtools Everything, a bookmark can involve more than saved search text. Search options, filters, indexed locations, exclusions, paths, instance settings, and the Windows account running Everything can all change the outcome. Start with a small bookmark test, identify whether the problem is the saved bookmark or the underlying search, and stop as soon as the expected results return.

1. Confirm the Symptom With a Small Safe Test

Before changing indexes or Windows settings, determine whether bookmarks are generally broken or only one saved search is affected. A controlled test prevents an old path, advanced search expression, or hidden filter from distracting you.

1.1 Create a simple test bookmark

1. Create a uniquely named text file in a local folder that Everything already indexes, such as your Documents folder.
2. Wait for the filename to appear in a normal Everything search.
3. Clear the search box and select the Everything filter.
4. Search for the unique filename without regular expressions, wildcards, or path syntax.
5. Create a bookmark from that search and give it a distinctive name such as Bookmark Test.
6. Clear the search, change to another query, and then open Bookmark Test.

Success means the saved text returns to the search box and the test file appears. If this works, Everything can create and open bookmarks. Stop changing global settings and inspect the original bookmark instead. If the test bookmark restores text but does not show the file, test the same text manually. That separates bookmark behavior from an indexing or search-option problem.

1.2 Compare saved search text with active filters

A bookmark's search text and the active filter are separate influences on the result list. For example, a bookmark that searches for a folder name can return nothing if the Images, Audio, Executables, or another restrictive filter remains active. The same text may work immediately when the filter is changed to Everything.

Clear the search box, select the Everything filter, and disable specialized search modes that are not required. Then enter the bookmarked text manually. If the results appear, edit or recreate the bookmark while the intended filter and options are active. Success means opening the bookmark reproduces the same query state and result list as the manual search.

1.3 Check whether search options are part of the mismatch

Options such as Match Case, Match Whole Word, Match Path, Match Diacritics, and Enable Regex can materially change a query. A bookmark may restore saved settings, or the current state may continue to affect the search, depending on how the bookmark was created and configured. Inspect the bookmark in the bookmark organizer rather than assuming it contains only visible text.

Compare the state before and after opening the bookmark. A plain filename should normally be tested with regex disabled and without case, whole-word, or path restrictions. Success means the bookmark opens with the intended options and returns the same results every time. Once it does, do not rebuild the index.

2. Inspect the Bookmark and the Search State Directly

2.1 Edit or recreate the affected bookmark

Open Everything's bookmark organizer and inspect the affected entry. Check its name, search text, filter, and any search options it applies. Remove accidental spaces, stale operators, unmatched quotation marks, and unwanted regular-expression syntax. If the entry is complicated, copy its search text to a text editor before simplifying it.

A reliable troubleshooting method is to reduce the expression to a known filename, confirm the bookmark works, and then add one condition at a time. If the original entry is difficult to understand, recreating that single bookmark is safer than resetting all Everything settings.

2.2 Look for renamed or moved folders

Bookmarks that include a full path will fail when a folder is renamed, moved, disconnected, or mounted under a different drive letter. Search text referring to D:\Projects\Current cannot match files now stored under E:\Projects\Current. Quoted paths, path: conditions, and macros that constrain locations deserve particular attention.

Paste the saved path into File Explorer and verify that the current Windows account can open it. Next, search Everything for a known filename from that location without the path restriction. If the file appears, update the bookmark to use the new path. Success means the updated bookmark returns files from the intended folder without relying on its former name or drive letter.

2.3 Organize bookmarks to prevent state confusion

Descriptive names make bookmark problems easier to diagnose. Include the purpose and scope, such as “NAS PDFs Modified This Month” or “Local Project Logs,” rather than using several entries named “Search.” Keep a separate basic test bookmark and remove obsolete duplicates after confirming they are no longer needed.

For important searches, also keep a plain-text copy of the search expression in your documentation. This makes it possible to compare what the bookmark loads with the known-good query, especially on portable installations or systems managed by several administrators.

3. Verify the Index, Filters, Exclusions, and Result Omissions

3.1 Decide whether the bookmark or the index is responsible

If the bookmarked search text also fails when typed manually, the bookmark is probably not the root cause. Search for a known exact filename from the affected location. Then search for part of the filename with the Everything filter selected and restrictive options disabled.

Everything is a separate application from Windows Search. Standard local NTFS and ReFS indexing in Everything uses filesystem metadata and change information, while folder indexing can cover locations that need periodic rescanning. Rebuilding the Windows Search index generally does not repair an Everything bookmark.

3.2 Check indexed volumes and folder indexes

Open Everything's Options pages for NTFS, ReFS, and Folders, as applicable. Confirm that the volume or folder containing the expected files is included. Folder indexes are especially relevant for network shares, mapped drives, NAS folders, removable media, and filesystems that are not handled through local NTFS or ReFS indexing.

For a folder index, verify the folder path and review its update or rescan behavior. Trigger an appropriate rescan if the indexed folder is available but stale. Success means a newly created test file in that location appears after the configured scan or update. Stop there if the original bookmark also starts working.

3.3 Review exclusions and omitted results

Inspect Everything's exclusion settings for excluded folders, files, extensions, hidden items, or system items relevant to the missing result. Also check whether the current filter or query contains a negation that omits the file. A bookmark can look broken when it faithfully restores an exclusionary query.

Temporarily test with a known file that should not fall under any exclusion. If removing or correcting one exclusion restores the expected results, keep the narrow correction and avoid broadly exposing folders you deliberately excluded for privacy or performance reasons.

3.4 Check filters and search macros

Custom filters can contain their own search expressions. A bookmark that selects a custom filter may therefore combine the visible bookmark text with a less visible restriction. Open the filter editor, inspect the selected filter, and compare the result with the Everything filter.

Success means the bookmark produces the intended result after its custom filter expression is corrected or removed. If changing to the Everything filter solves the issue, there is no reason to alter the index or service.

4. Check Windows, Network, Service, and Instance Context

4.1 Confirm the correct account and instance

Everything can be run with different configurations, named instances, startup arguments, or portable settings. A bookmark created in one instance may not exist in another, and an instance can have different indexes, filters, exclusions, and folder indexes. Check the window title, shortcut target, startup command, and configuration location if behavior differs between launches.

Also compare normal and elevated launches. Mapped drives are associated with a Windows logon context and may not appear identically in an elevated process or another account. Prefer a UNC path such as \\server\share\folder for a folder index when drive-letter mappings are inconsistent, provided the share is securely accessible to the intended account.

4.2 Verify network shares and NAS availability

A bookmark can load correctly while returning no current results because its NAS or network share is offline, authentication has expired, the hostname has changed, or the folder index has not rescanned. Open the exact share in File Explorer under the same account running Everything. Confirm that you can list the folder and open a harmless test file.

If the share is reachable, review its folder index and request a rescan. If it is not reachable, fix connectivity, DNS, VPN, or credentials first. Do not expose an Everything HTTP, ETP, or other search server directly to the public internet as a troubleshooting shortcut.

4.3 Check the Everything service without confusing its role

The Everything service helps the desktop application access local filesystem indexing information without requiring the interface itself to run elevated. Check that the service is installed and running if your configuration relies on it. Restarting a stopped service can resolve local indexing access problems, but it will not repair malformed bookmark text or reconnect an unavailable NAS share.

Success means the affected local volume appears in the index and known filenames can be found after the service is restored. If manual searches work but only one bookmark fails, return to that bookmark rather than repeatedly restarting the service.

4.4 Review firewall and security controls narrowly

Local filename bookmarks normally do not require broad firewall changes. Firewall rules matter when Everything connects to a remote Everything service or when a network architecture explicitly uses a supported server feature. Confirm the server address, port, authentication, and network reachability against your organization's configuration.

Security software can also block configuration writes or network access. Review its logs and allow only the required executable, configuration location, or trusted internal connection. Do not disable antivirus or firewall protection permanently. A successful fix is a specific, documented exception or corrected policy, not an unprotected computer.

5. Verify Portable Settings and Command-Line Startup

5.1 Make sure portable bookmarks can be saved

Portable-app users should confirm that Everything can write to its intended settings location. Running from a read-only folder, protected application directory, locked archive, temporary extraction path, or restricted network share can prevent bookmark changes from persisting. Create a test bookmark, exit Everything normally, relaunch it from the same executable and instance, and check whether the bookmark remains.

If it disappears, move the portable installation to a user-writable folder approved by your organization or correct the folder permissions. Avoid granting broad write access to all users. Success means the test bookmark survives a complete exit and relaunch.

5.2 Inspect shortcuts and command-line options

A shortcut, script, launcher, or scheduled task may start Everything with a named instance, a different configuration, an initial search, or another command-line option. Compare the shortcut target with a direct launch of the intended executable. Also inspect multiple pinned shortcuts because an older shortcut may point to another copy.

If removing an unnecessary startup argument restores the correct bookmarks, update that shortcut and retest. Do not remove enterprise-managed arguments without understanding their purpose. The goal is to launch the same instance and configuration consistently.

5.3 Check server-based searches separately

If a bookmark depends on remote Everything results, test the connection independently from the saved query. First confirm that a basic remote search works. Then run the bookmarked expression manually against the same server context. A local bookmark cannot return remote files when the client is disconnected, targeting the wrong server, or using an account without access.

Success means both a simple query and the bookmarked query work through the intended trusted connection. If only the advanced expression fails, troubleshoot its syntax or filter rather than changing network security.

6. Use Diagnostics Without Destroying Useful State

6.1 Read the status bar and Options pages

The status bar can reveal whether a query returns zero items, whether a filter is limiting results, and whether Everything is still processing an operation. Review the relevant Options pages for bookmarks, search behavior, filters, indexes, exclusions, services, and folder indexing. Record existing values before changing them.

Change one setting at a time and rerun the simple test bookmark. This creates a clear cause-and-effect trail. Once the expected file appears and the bookmark consistently reproduces the intended query, stop changing settings.

6.2 Test search syntax in stages

Complex saved searches should be decomposed. Begin with one filename term. Add the path condition, extension, date or size expression, and other operators individually. Keep regex disabled unless the expression is intentionally a regular expression. Check quotation marks around paths containing spaces.

The first condition that changes a working query into a failing query identifies the likely problem. Correct that expression in the bookmark, then test it after clearing the search and relaunching Everything.

6.3 Review the Index Journal and diagnostic output

When files are missing despite correct bookmark state, Everything's Index Journal can help determine whether index changes are being processed. Diagnostic or debug output can also expose configuration, instance, index, and connection issues. Use voidtools documentation for the supported diagnostic method in your installation, and avoid publishing logs without reviewing them for filenames, paths, hostnames, and other sensitive information.

If diagnostics show that the file never enters the relevant index, focus on the volume, folder index, exclusion, permissions, or connectivity. If the file is indexed and a plain search finds it, focus on the bookmark expression and active search state.

6.4 Use Force Rebuild only after safer checks

A Force Rebuild can be appropriate when a local Everything index is demonstrably inconsistent and normal updates do not correct it. Before using it, verify the bookmark text, filter, search options, path, exclusions, indexed locations, service, and share availability. Rebuilding does not repair an incorrect path or unwritable portable configuration.

After a rebuild, allow indexing to complete and test a known filename before opening the original bookmark. Success means the known file and bookmarked results return. Do not repeatedly rebuild if the symptom persists, because the cause is probably elsewhere.

7. Run a Clean Temporary Test Before Broad Changes

If the cause remains unclear, run a temporary clean test that does not overwrite your working configuration. Back up or copy relevant settings first, then launch a separate test instance or use a separate temporary configuration according to voidtools guidance. Do not replace or delete the current database as your first step.

1. Start the temporary instance without importing complex filters or bookmarks.
2. Confirm that it indexes only the safe local test location required for diagnosis.
3. Create the unique test file and verify a manual search.
4. Create a simple bookmark and relaunch the test instance.
5. Add the affected path or folder index only if the simple test succeeds.
6. Recreate the original search one condition at a time.

If the clean test works, the issue is likely in the original bookmark, filter, exclusion, startup context, or configuration. Compare settings selectively rather than replacing everything. If the clean test also fails to index a known local file, investigate service access, filesystem support, permissions, or security policy.

8. Quick Fix Checklist

• Select the Everything filter and disable unintended regex, case, word, or path matching.
• Type the bookmarked text manually to separate bookmark failure from search failure.
• Create and reopen a simple bookmark for one known local filename.
• Inspect the bookmark's saved text, filter, and search options.
• Update bookmarked paths after folders, shares, or drive letters change.
• Confirm the expected volume or folder is indexed and not excluded.
• Rescan a reachable folder index when NAS or share results are stale.
• Check that the Everything service is running if local indexing depends on it.
• Launch the same Everything instance and review shortcut arguments.
• Verify that portable settings are stored in a writable location.
• Test remote connectivity separately from the bookmarked expression.
• Use Force Rebuild only after safer checks indicate index inconsistency.

9. Frequently Asked Questions

9.1 Why does my Everything bookmark open but show no results?

The bookmark may be restoring valid text while a restrictive filter, search option, stale path, exclusion, or unavailable indexed location removes all matches. Switch to the Everything filter, simplify the query, and search manually for one known file. If the manual search also fails, investigate the index or location rather than the bookmark.

9.2 Does an Everything bookmark save filters and search options?

Bookmarks can include more state than the visible search text, depending on how the entry is configured. Inspect the bookmark's properties and compare the filter and search-option state before and after opening it. Recreate the bookmark with the intended settings if its behavior is ambiguous.

9.3 Why did a bookmark stop working after I renamed a folder?

A saved query containing the old full path will no longer match the renamed folder. Confirm the new path in File Explorer, verify that Everything indexes it, and replace the old path in the bookmark. A path-independent filename query may still work if the files remain indexed.

9.4 Why do portable Everything bookmarks disappear after restart?

The portable installation may be unable to write its settings, or a launcher may be opening a different copy or instance. Test whether a new bookmark survives a normal exit, confirm the settings folder is writable, and ensure every shortcut starts the same executable and instance.

9.5 Will rebuilding Windows Search fix Everything bookmarks?

Usually not. Everything and Windows Search use different applications and indexing systems. Test the query in Everything and inspect Everything's own indexes, folder indexes, exclusions, and service state. Only troubleshoot Windows Search when the problem actually occurs in File Explorer or the Windows search interface.

9.6 When should I use Force Rebuild?

Use Force Rebuild only when expected files are on a correctly configured and accessible indexed volume, are not excluded, and still remain absent after normal updates. Do not use it to fix malformed bookmark syntax, a renamed folder, an offline NAS, the wrong instance, or settings that cannot be saved.