Search for folders with files above 260 path limit

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
JTCGiants56
Posts: 190
Joined: Fri Nov 28, 2014 3:58 pm

Search for folders with files above 260 path limit

Post by JTCGiants56 »

Hello, so I know how in advanced search to find files themselves with 260+ character file paths.

But I'm looking for a way to find all FOLDERS (which may not have over 260 characters themselves) with files in them that are over the 260 character path limit.

Please let me know if this is possible.

Thank you
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Search for folders with files above 260 path limit

Post by void »

Unfortunately, Everything does not have a direct search to do this.

You could do this with a 2 stage search:
  • In Everything, type in the following search:
    path:len:>=260
  • From the File menu, click Export....
  • Change Save as type to EFU Everything File List.
  • Choose a filename and click Save.
  • From the File menu, click Open File List....
  • Select the file list you saved earlier.
  • Search for:
    childfilecount:
When you are done with the results, close the file list:
  • In Everything, type in the following search:
  • From the File menu, click Close File List....

I'll consider adding a childlen: / path:childlen: search.
JTCGiants56
Posts: 190
Joined: Fri Nov 28, 2014 3:58 pm

Re: Search for folders with files above 260 path limit

Post by JTCGiants56 »

void wrote: Sat Oct 31, 2020 12:05 am Unfortunately, Everything does not have a direct search to do this.

You could do this with a 2 stage search:
  • In Everything, type in the following search:
    path:len:>=260
  • From the File menu, click Export....
  • Change Save as type to EFU Everything File List.
  • Choose a filename and click Save.
  • From the File menu, click Open File List....
  • Select the file list you saved earlier.
  • Search for:
    childfilecount:
When you are done with the results, close the file list:
  • In Everything, type in the following search:
  • From the File menu, click Close File List....
T

I'll consider adding a childlen: / path:childlen: search.
Thanks so much this is what I was looking for!
For some reason childfilecount:1 is showing folders with more than one files in it? Does that look correct to see folders with just 1 file?

Edit: Oh I see, it looks like its kept the folders from before I added the "1" since its a file list.
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Search for folders with files above 260 path limit

Post by void »

childfilecount: will match folders that contain 1 or more child files.
childfilecount: is the same as childfilecount:>0

childfilecount: does not count child folders. Use childcount: to count child folders and child files.

childfilecount:1 will match folders that contain exactly 1 child file.
JTCGiants56
Posts: 190
Joined: Fri Nov 28, 2014 3:58 pm

Re: Search for folders with files above 260 path limit

Post by JTCGiants56 »

Thanks!
raccoon
Posts: 1015
Joined: Thu Oct 18, 2018 1:24 am

Re: Search for folders with files above 260 path limit

Post by raccoon »

void: What are the differences between path:len:>=260 and just len:>=260. Am I to guess that omitting path: will also search for file names and folder names that themselves exceed 260 characters, and so including path: will speed up processing?

Also, what considerations are there (if any) for paths that contain WCHAR double byte unicode characters, or UTF-8/UTF-16 encoded 3+ byte characters (i think windows does that now? I'm not sure?).
void
Developer
Posts: 15096
Joined: Fri Oct 16, 2009 11:31 pm

Re: Search for folders with files above 260 path limit

Post by void »

With Match Path disabled under the Search menu:
len: will match only the basename (name part)
eg: length of c:\windows\notepad.exe is 11 characters.

With Match Path enabled under the Search menu: or with the path: search modifier
path:len: will match the full path and filename.
eg: length of c:\windows\notepad.exe is 22 characters.

len: would be slightly faster than path:len:
path:len: should still be instant.

Everything uses UTF-8 internally.
Lengths are converted to UTF-16 for the len: search function.
Also, what considerations are there (if any) for paths that contain WCHAR double byte unicode characters, or UTF-8/UTF-16 encoded 3+ byte characters (i think windows does that now? I'm not sure?).
len: only looks at the UTF-16 character count. Surrogates pairs are incorrectly treated as two characters.
Everything 1.5 will offer a chars: search function to search for true unicode characters.
Everything 1.5 will also offer a utf8len: search function to search the internal lengths (very very fast)
Post Reply