Reliability issue with dupe command

Discussion related to "Everything" 1.5.
ericgl
Posts: 41
Joined: Tue Apr 28, 2020 7:35 am

Reliability issue with dupe command

Post by ericgl »

Hi David/Void,

I've been using Everything 1.5 for a long time.
I always download the latest version as soon as one is published.
I'm currently using v1.5.0.1420b (x64) - which is the latest as of today.

For a long time, I've been having this issue with the dupe command, or more specifically with !dupe:
Almost daily, when I'm at work, I create new files (or modify existing files) on my portable USB drive.
When I get home, I click on a search bookmark which checks for non-duplicates, so I can easily see which new/modified files need to be copied from the portable USB drive to my internal hard-drive. The search bookmark is:

Code: Select all

Q:|K: !dupe: dm:TODAY sort:dm file: !\$Recycle !\"System Volume Information"
Q: is the portable drive.
K: is the internal hard-drive.

The problem is that it seems to be omitting certain files, such as Excel XLSX (not sure about other files).

When I run another search in another tab, for example:

Code: Select all

Q:\ file: dm:TODAY !"\System Volume Information" !\$Recycle.bin
I can see that there are actually more file(s) that need to be copied, usually XLSX file(s).

For example, as can be seen in this screenshot, there are 9 files which were created/modified today on the portable USB drive (Q:):
image.png

However, the search:

Code: Select all

Q:|K: !dupe: dm:TODAY sort:dm file: !\$Recycle !\"System Volume Information"
only shows 8 files, as it omitted the excel file.

I realize this issue may be hard to debug, but hopefully you'll find a solution. I checked every setting in Everything, including the bookmarks parameters. I even deleted the Everything.ini file, so Everything would create a new one. The issue still persists.
You do not have the required permissions to view the files attached to this post.
Last edited by ericgl on Tue Aug 11, 2026 4:32 pm, edited 1 time in total.
therube
Posts: 5804
Joined: Thu Sep 03, 2009 6:48 pm

Re: Reliability issue with dupe command

Post by therube »

Try:
<Q:|K:> !dupe: dm:TODAY sort:dm file: !\$Recycle !\"System Volume Information


< >, are grouping
as it was, your search was doing a Q: OR K: !dupe: ..., with the !dupe: only applying to K:...
ericgl
Posts: 41
Joined: Tue Apr 28, 2020 7:35 am

Re: Reliability issue with dupe command

Post by ericgl »

OK, thanks.

I will try and see if grouping helps. Will report back.
ericgl
Posts: 41
Joined: Tue Apr 28, 2020 7:35 am

Re: Reliability issue with dupe command

Post by ericgl »

I'm now using Everything v1.5.0.1422b.
I'm afraid grouping also does not help.
Seems to be some bug with !dupe: regarding Excel files.
It happened to me again, even with grouping <Q:|K:>, where it missed another Excel file which was newer on the Q: drive, yet did not show up in the results.
When I explicitly search for this file, I can see that the file's Modified date is newer on the Q: drive vs the file present on the K: drive.

Currently, I can't rely on the search :

Code: Select all

<Q:|K:> !dupe: dm:30days sort:dm file: !\$Recycle !\"System Volume Information"
...and I have to re-check using another search.
void
Developer
Posts: 20186
Joined: Fri Oct 16, 2009 11:31 pm

Re: Reliability issue with dupe command

Post by void »

!dupe:
is the same as
unique:name


The xlsx name likely exists on your K: drive.

Does the path change at all, or do you preserve paths?
If you preserve paths, instead of !dupe:, please try:
regex:Q:\\(.*) !fileexists:K:\$1:


This will show files that exist on the Q: drive, but not on the K: drive.



Alternatively, instead of looking for just unique names, please try looking for unique sizes and date modified timestamps too:
unique:name;size;date-modified




Everything doesn't add new results when using unique:
If the file is modified after your search, you'll need to refresh your unique: search with F5.
ericgl
Posts: 41
Joined: Tue Apr 28, 2020 7:35 am

Re: Reliability issue with dupe command

Post by ericgl »

Thanks, void.

I don't usually change paths (folder structure). I have the same paths on both drives for years.

I'll try unique:name;size;date-modified instead of !dupe: and report back.
Logically, it looks promising.