voidtools forum

For a test case I added d: to both NTFS indexes and to the folders. There are now no other drive/folder . After indexing dupe: lists duplicate files and !dupe: -non duplicate files. Surprisingly d: being a low capacity drive still lists around 20 non duplicate files. One amongst them is xyz.jpg. But if I search for xyz.jpg it perfectly returns two identical files sizes path etc!
Something wrong here...In a high capacity drive non duplicate files number to 17000 which is also obviously wrong....

dupe: is going to find duplicate files irrespective of other filtering.

So you cannot say, "find dups on drive X:, alone".

It will find dups on ALL drives.
Though the results displayed in its list will be filtered per your criteria.

So if you have 3 dups of "abc123", two on drive C: & one on drive X: & your search is:
> dupe: X: abc123
The results list will show "abc123", once, the one on drive X:, only.

I added d: to both NTFS indexes and to the folders. There are now no other drive/folder

Will have to experiment with that?

Will have to experiment with that?

Sorry , not too clear with this? In my test case I had included only one drive d: in both NTFS and "Folders" . Hence dupe: in my case would return only duplicates from d:. The point is !dupe is listing some files which are also covered in dupe: , which cannot be..
Meanwhile where is David? Is this project in a pause mode for the time now?

Quit (Ctrl+Q) & restart Everything a few times.
See if that doesn't make a difference?

Search: KIMM .JPG (there are 18 instances)
Then modified with: dupe: or !dupe:

First time, after only selecting NTFS: C, & Folder: C, I returned 18 results for KIMM .JPG.
(Seemingly I should have gotten 36?)

Adding dupe: gave me 18 results.
Adding !dupe: gave me, like you & unexpectedly, 1 result; KIMM_8981.jpg
(I would have expected no results.)

Next I removed NTFS: C, so all there was to search was Folder: C.
At that point KIMM .JPG returned 18 results.
KIMM .JPG !dupe: returned 18 results.
KIMM .JPG dupe: returned 0 results.
All expected.

Then I added NTFS: C back in, so back to NTFS: C & Folder: C.
Then Quit ... & waited a number of seconds, & restarted.
At that point KIMM .JPG returned 36 results.
(Different from initially.)
KIMM .JPG !dupe: returned 0 results.
KIMM .JPG dupe: returned 36 results.
Again expected.

(& at that point thought I might have had something figured out. ... UNTIL...)

I went through it again, where I was then back with that one odd, unexpected !dupe: result, so ... got me, but something not quite right?


I was doing this via: everything.exe -instance TEST, so perhaps with the service running, or with the existing instances of everything.exe, or ... who knows?

Would be safe to conclude this as a bug....

I got a similar problem with dupe.

I have two drives, both holding the same files with the same names, filesize etc., so they're proper 1:1 copies of each other.
but if I search with the query "path:<d:|e:> !dupe", I get a few results back, but only from one drive.

Rebuilding the index and restarting Everything does nothing.

Searching for some of those results individually shows both copies on each drive, so Everything has registered them properly. No idea why some of those files aren't being registered as dupes.

I'd like to push this bug up again.

File structure: the search syntax is showing "rfuihjoakpsdijuhtzfr.txt", although it's only a dupe if the path: query would be

This is a limitation with Everything.

dupe: shows duplicates for the entire index not the search results.

dupe: works best when used with a file type limiter, eg: I will look into support for finding dupes in results in a future release.

Thanks!

Barring (insert appropro word) the drives I DONT want to be searched seems to work, in order to find duplicates on specific drives:
I.e.
!C:\ !D:\ !E:\ !I:\ dupe: