Everything Date Modified Search Not Working: How to Fix It

When an Everything date modified search is not working, the usual symptom is a date query that returns files from the wrong period, leaves out files you know were changed, or produces different results depending on the computer, drive, or search method. The likely causes fall into a few categories: incorrect dm: syntax, ambiguous regional date formatting, date-modified indexing being disabled or stale, confusion between created and modified timestamps, exclusions or filters, folder-index limitations, network access problems, or a different Everything instance answering the query.

This guide focuses specifically on date modified searches in voidtools Everything for Windows. Everything is not Windows Search. Everything maintains its own index and has its own search syntax, options, services, exclusions, and server features. Changing Windows Search indexing options will not normally repair an Everything date query.

1. Confirm the Symptom With a Small Safe Test

Before rebuilding an index or changing several settings, create a controlled test that tells you whether the problem affects search syntax, timestamp indexing, or access to a particular location.

1.1 Create a known test file

1. Create a new text file in a local folder that Everything normally indexes, such as your Documents folder.
2. Give it a distinctive name, such as everything-dm-test-unique.txt.
3. Open the file, add a line of text, save it, and close it.
4. Search Everything for the distinctive filename without a date condition.
5. Add dm:today to the search.

A suitable query is everything-dm-test-unique.txt dm:today. Success means the file appears both in the filename-only search and in the date-filtered search. If it appears by name but disappears when dm:today is added, focus on date syntax, the displayed timestamp, and the Index date modified option. If it does not appear even by name, the problem is broader than date searching and may involve the index, an exclusion, the file system, or the Everything instance you opened.

1.2 Test today and thisweek separately

Run dm:today and dm:thisweek as separate searches. Then combine each one with the unique filename. These relative expressions avoid numeric date-format ambiguity and are useful diagnostic controls.

If the file appears with dm:thisweek but not dm:today, inspect its actual Date Modified value and your Windows clock, time zone, and midnight boundary. If both relative searches work but a numeric date fails, the likely problem is date formatting or range syntax rather than indexing. Stop changing index settings and correct the query instead.

1.3 Display the relevant column

Make sure the results list shows the Date Modified column. Do not judge the query using Date Created, Date Accessed, or a date embedded in the filename. A copied or downloaded file can have a creation time that differs substantially from its modification time.

Sort by Date Modified and inspect the test file. Success means the displayed value agrees with when you saved the file and the file matches the expected relative query.

2. Check the Everything Settings Directly Related to Date Searches

2.1 Use the dm syntax correctly

Everything uses the dm: search function for Date Modified. Put the condition in the search box alongside any filename, extension, path, or other search terms. Practical examples include:

• dm:today for files modified today
• dm:thisweek for files modified during the current week
• *.docx dm:today for Word documents modified today
• path:C:\Projects dm:thisweek for this week's changes under a project path
• dm:2025-01-01..2025-01-31 for an explicit date range

Avoid inserting unnecessary spaces inside a date range. Also check whether Match Case, Match Whole Word, Match Path, regex mode, or an active search filter is changing the interpretation of the entire query. Clear the search box and choose the general Everything filter before retesting.

2.2 Prefer ISO-style dates when diagnosing

Numeric dates such as 03/04/2025 are ambiguous. Depending on the locale, that text may be understood as March 4 or April 3. Use an ISO-style year-month-day value such as 2025-03-04 while troubleshooting. This makes your intended date explicit and is easier to compare across machines with different regional settings.

Test a single known date and then a short range. If ISO-style syntax works while a slash-formatted date does not, the index is probably healthy. The fix is to standardize saved searches, scripts, documentation, and command-line queries on unambiguous dates. Once the ISO query returns the expected files, stop rebuilding or reconfiguring Everything.

2.3 Verify Index date modified

Open Everything's Options and locate the index settings for Date Modified. Confirm that Index date modified is enabled when you rely on fast and consistent dm: searches. The exact arrangement of the Options pages can differ between Everything editions and configurations, so look under the relevant Indexes settings rather than assuming Windows Search controls it.

After enabling the option, allow Everything to update or rebuild the affected index. Watch the status bar and avoid repeatedly restarting the program during this process. Success means the known test file appears with dm:today, and its displayed Date Modified value is correct. At that point, no further index changes are necessary.

2.4 Remove filters and result omissions from the test

An active filter can add conditions that are not visible in the text you typed. Exclusions, result omissions, hidden-file rules, and path restrictions can also make a valid date query look broken. Switch to the broad Everything filter, clear any temporary omission, and search for the unique test filename again.

Review exclusions in Options if the failure affects one folder, extension, drive, or share. Do not permanently remove a security or privacy exclusion merely to broaden results. Temporarily test a safe location, determine which rule is responsible, and then narrow the rule only if indexing that content is appropriate.

2.5 Confirm which Everything instance receives the query

Portable installations, named instances, command-line switches, Everything Search clients, and server connections can point at different indexes. One instance may have Date Modified indexing enabled while another does not. Check the window title, configuration location, connection settings, and launch shortcut.

If a shortcut or script starts Everything with command-line options, compare its behavior with a normal interactive launch. If a remote Everything server supplies the results, test directly on the server or host when possible. Success means the same known file and date query return consistently from the intended instance. Stop modifying the local index if the query is actually being answered by another instance.

3. Check Index Coverage, Services, Permissions, and Storage

3.1 Determine how the affected location is indexed

Local NTFS volumes, manually configured folder indexes, removable drives, mapped drives, and NAS shares do not necessarily update through the same mechanism. First determine whether the missing file is on a local indexed volume or in a folder index.

If only a NAS share or mapped drive is affected, review the corresponding folder-index entry and its update or rescan settings. Confirm that the path still resolves. A drive letter mapped in your interactive account may not exist for a service running under another account. Using the appropriate UNC path can avoid drive-letter context problems, provided the account has permission to access that share.

3.2 Check the Everything service state without confusing its role

The Everything service helps Everything access and monitor supported local volumes without requiring the user interface to run with elevated rights. If the service is configured, confirm it is running and that the Everything client can communicate with it. Restarting a stopped service can be reasonable, but repeatedly reinstalling it is not the first response to a numeric date-format problem.

Success means local changes appear promptly in a plain filename search and the same files pass dm:today. If filenames update correctly but only numeric dates fail, return to syntax and locale testing rather than continuing service work.

3.3 Compare account context and permissions

A folder index can only read locations available to the process and account performing the scan. Network credentials, service accounts, scheduled tasks, elevated sessions, and standard user sessions may see different mapped drives and shares. Confirm that the same account context can open the affected folder in File Explorer.

For a NAS, verify that the share is connected and the files are readable when Everything performs its scan. Do not expose an Everything server or its search interface directly to the public internet as a troubleshooting shortcut. Keep remote access limited to trusted networks and use properly secured remote-access methods.

3.4 Consider the file system and update mechanism

If results are correct on one drive but stale on another, compare the file systems and indexing methods. A location handled through periodic folder scanning may not reflect changes as immediately as a locally monitored volume. This can explain why a newly modified network file appears after a rescan but not instantly.

After confirming the configured update method, trigger the safest available refresh for that specific folder index. Success means the file's displayed Date Modified value changes after the refresh and the date query includes it. If so, adjust the folder's rescan schedule only as needed rather than rebuilding every index.

3.5 Review antivirus and firewall effects carefully

Security software can sometimes block service communication, server connections, configuration writes, or access to a protected folder. Check the product's logs and Windows event information before changing protection. If an approved exception is needed, scope it to the trusted executable, local connection, or folder involved.

Never disable antivirus or firewall protection permanently to make search work. For a remote Everything connection, confirm the correct host, port, network profile, and firewall rule, and keep access private. Success means the existing security controls permit the intended local or trusted-network connection without exposing the service broadly.

4. Refresh and Diagnose the Index Safely

4.1 Read the status bar before rebuilding

The status bar can reveal whether Everything is indexing, rescanning, or returning an unexpectedly small number of results. Wait for active indexing to finish before judging a date query. Test the unique filename again after activity settles.

If the result count changes while the index is updating, the apparent failure may simply have been temporary. Once the correct file appears and passes the date test, stop. Additional rebuilds can waste time and obscure the original cause.

4.2 Use Force Rebuild only after focused checks

A Force Rebuild is appropriate when the indexed Date Modified values are demonstrably stale or inconsistent across many local files, and simpler checks have ruled out syntax, filters, exclusions, instance mismatch, and an in-progress update. It should not be the first step.

Before rebuilding, note your current options and make sure important folder indexes and exclusions are understood. Use Everything's supported Force Rebuild control rather than manually deleting database files. Allow the rebuild to complete, then repeat the same controlled queries. Success means the test file and a sample of previously missing files now show correct timestamps and match dm:today or the intended ISO range.

4.3 Inspect the Index Journal and diagnostic output

If changes remain missing, the Index Journal or available diagnostic information can help show whether Everything noticed an update, rescanned a folder, lost access to a volume, or encountered another indexing event. Debug logging is most useful when you reproduce one specific action: save the test file, wait briefly, and run the date query.

Keep logs only as long as needed and review them for sensitive filenames or paths before sharing. Record the exact query, file path, displayed timestamp, expected timestamp, indexing method, and whether a filename-only search succeeds. This evidence is far more useful than a general report that Everything search is not working.

4.4 Separate created and modified date tests

A file's creation time is not interchangeable with its modification time. Copying a file can produce a new creation timestamp while preserving or changing its modified timestamp depending on the application and destination. Extracting an archive, synchronizing with a NAS, restoring a backup, or downloading a file can also produce timestamp combinations that seem surprising.

Inspect the Date Modified property in Windows and compare it with Everything's Date Modified column. If both agree, dm: is working from the available metadata even if the date is not when you personally received or copied the file. Use the appropriate created-date search function when your actual question is when the destination file was created.

4.5 Account for time zones and recent changes

Relative searches such as today depend on calendar boundaries. A file changed near midnight, a recent time-zone change, an incorrect Windows clock, or timestamps supplied by a remote system can make a file fall on the adjacent day. Network devices may display or store times differently, although Windows and applications often convert timestamps for presentation.

Check Windows date, time, time zone, and synchronization status. Compare the file's exact displayed time rather than relying on memory. Test both dm:today and dm:thisweek, followed by an explicit ISO date range covering the adjacent day. If the wider range finds the file and the timestamp is consistent across Everything and file properties, the issue is a boundary or expectation problem, not a missing index entry.

5. Run a Clean Temporary Test Before Changing More Settings

If the current configuration has years of saved filters, exclusions, portable files, server settings, or command-line customization, run a temporary clean test. Preserve the existing configuration and do not delete the database as a first move.

1. Close unnecessary Everything windows so you know which instance is being tested.
2. Back up or note relevant settings before experimenting.
3. Launch an isolated portable or named test instance using the supported method for your setup.
4. Index only a small, safe local test location when configuration permits.
5. Enable Date Modified indexing for the test.
6. Create and save the unique test file.
7. Run filename-only, dm:today, dm:thisweek, and ISO-date searches.

If the clean instance works, the Windows timestamp and basic Everything behavior are sound. Compare the original instance's filters, exclusions, Date Modified index option, folder indexes, server target, and startup command line one category at a time. If the clean instance also fails, capture the exact query and timestamp before seeking support.

Change only one variable between tests. As soon as the known file appears under the correct date condition and representative real files also return, stop changing settings. A successful controlled test is stronger evidence than applying every possible fix.

6. Quick Fix Checklist

• Confirm the file appears in a filename-only search.
• Show and inspect the Date Modified column.
• Test dm:today and dm:thisweek.
• Use ISO-style dates such as 2025-03-04.
• Verify that you need Date Modified, not Date Created.
• Choose the general Everything filter and clear result omissions.
• Review relevant exclusions without removing privacy protections broadly.
• Confirm Index date modified is enabled.
• Wait for active indexing or folder scanning to complete.
• Check whether the affected path uses a local index or folder index.
• Verify NAS access, UNC paths, credentials, and account context.
• Confirm the Everything service or trusted server connection is available.
• Check portable, named-instance, and command-line settings.
• Use Force Rebuild only after targeted checks indicate stale indexed metadata.
• Run a clean temporary test before making widespread configuration changes.

7. Frequently Asked Questions

7.1 Why does dm:today return no files?

The most common reasons are that no matching file has the expected Date Modified timestamp, Date Modified indexing is unavailable or stale, a filter or exclusion is active, or the query is running against a different Everything instance. Create a unique file, save it, verify its displayed Date Modified value, and search for its name with dm:today.

7.2 Why does a date range return the wrong month or day?

A slash-formatted numeric date may be interpreted according to regional settings. Replace ambiguous values with ISO-style year-month-day dates and retest. If the ISO range works, keep that format in saved searches and scripts.

7.3 Why are files from my NAS missing from date searches?

The share may depend on a folder index, periodic rescanning, network credentials, or a mapped drive that is unavailable to the account performing the scan. Confirm that the path is reachable, review the folder-index update settings, and test with a known file on the share.

7.4 Does rebuilding the Windows Search index fix Everything?

Normally, no. voidtools Everything maintains its own index and configuration. Windows Search troubleshooting is relevant only if your problem is actually occurring in Windows Search rather than Everything. Use Everything's Options, status information, index controls, and diagnostics for this issue.

7.5 Should I delete the Everything database?

Not as a first step. Start with syntax, timestamps, filters, exclusions, Date Modified indexing, service state, folder access, and instance selection. If evidence shows widespread stale metadata, use the supported Force Rebuild option before considering manual file removal.

7.6 When is the problem considered fixed?

The fix is successful when a known saved test file appears by name, matches dm:today and dm:thisweek, displays the correct Date Modified value, and representative files from the affected location match an explicit ISO date range. Once those checks pass consistently, stop changing settings and document the setting or syntax that resolved the issue.