FileSeek RSS: Feature request for path too long https://www.fileseek.ca/Discussions/RSS/?TopicID=220fc2de-30c3-44f4-8311-12fc4b5cadec FileSeek RSS: Feature request for path too long Sat, 02 May 2026 10:10:40 GMT en hourly 1 https://www.fileseek.ca/Discussions/RSS/?TopicID=220fc2de-30c3-44f4-8311-12fc4b5cadec RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#31 Thu, 10 Mar 2016 07:01:43 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#31 FileSeek Use Long Path Tool, Long Path Tool can simplify and probably end your problems in unlocking, managing and renaming files that appear to have a long filename. ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#30 Tue, 18 Jun 2013 09:19:25 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#30 FileSeek Long path tool is the best solution for your problem.try it and solve your problem ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#29 Tue, 28 May 2013 16:21:51 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#29 FileSeek Thanks for the info. Also try long path tool, it helped me with error 1320 in Win7.,:) ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#28 Thu, 09 May 2013 20:17:18 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#28 FileSeek FileSeek 3.0.1 Beta 1 is now available, and this should be fixed up. Please let me know if you still run into the same issue after updating!

Thanks! ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#27 Fri, 03 May 2013 17:10:19 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#27 FileSeek Thanks Pete! I was able to reproduce this here using your instructions, although it seems to be an intermittent issue for sure. We're looking into it and we'll hopefully find a solution to it soon :) ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#26 Thu, 02 May 2013 14:51:35 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#26 FileSeek C:\Temp\test
A - folder name in query
1) Use Delimon to create long path
2) Pick a folder name on Delimon path within standard 260 character limit
3) Search for folder name with only folder names checked returns folder name AND files in that folder (they have foldername as prefix)
4) Click on returned folder name and choose delete. FileSeek deletes all files in this folder and all sub folders but does not remove any folders
B - folder name in include file
Same process same result

Now in all tests I can't delete the returned folder in FileSeek even when I restart the application and it only returns that single item ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#25 Thu, 02 May 2013 13:40:27 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#25 FileSeek Ok, couple more questions:
  • Did you have any searches running in other tabs?
  • Were you searching using query text with match files/folders enabled, or just using the Include Files box?
]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#24 Tue, 30 Apr 2013 20:14:02 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#24 FileSeek Search was completed ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#23 Tue, 30 Apr 2013 17:21:11 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#23 FileSeek Quick question. Was your search still running, or paused while you were trying to delete the file? ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#22 Tue, 30 Apr 2013 17:16:58 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#22 FileSeek Interesting! We'll test this out here and try to reproduce it. ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#21 Fri, 26 Apr 2013 20:59:20 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#21 FileSeek Keith and Jon,
I have just spent half and hour testing the long path feature. The querying works fine and FileSeek will error on long paths if it finds one if the appropriate check box is selected. It will also enumerate correctly if you use a query for a file\folder at the end of long path without the check box.

However, FileSeek is really inconsistent about deleting folders on long paths that may contain subfolders and files. I cannot find any rational. It will not delete either via a right click > delete or highlight and press delete and then some time later it will delete. This is what was happening earlier in the week when I was testing.

OK - I believe I have found what happens. If I now close and reopen FileSeek I can then delete a higher folder on the long path if I just specify that folder as a query.
I suspect if I do a query and FileSeek returns long path and then you try to delete somewhere I believe there is a handle open within FileSeek and it will not delete. Maybe you need to test some more - and provide some deletion error logic?

For reference I was using Delimon to create the paths. Then I made sure nothing else had handle anywhere on the path.

Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#20 Fri, 26 Apr 2013 20:23:12 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#20 FileSeek Keith I think I found it - "Show an error and skip path when longer than 260 characters" ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#19 Fri, 26 Apr 2013 20:16:41 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#19 FileSeek Keith,
I see you released v3 and it handles paths that are too long. However - what was decided about my last question? I don't see anything obvious that is included.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#18 Mon, 22 Apr 2013 20:14:14 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#18 FileSeek Interesting, we've got an idea as to how we might implement that, so I'll let you know as soon as we have something to test :) ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#17 Mon, 22 Apr 2013 16:14:44 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#17 FileSeek Jon and Keith,
Since the changes you have implemented I now have a use question.
In the previous version I would put a query like *.xyz2 that I knew would not exist and FileSeek would error on the long file paths but show them.

Now when I put that query nothing gets returned so I need to verify how I can now get FileSeek to return just file paths that are too long - given not knowing their names before I start? Obviously I don't want to use *.* on a 2 TB fileserver.

Would it be simplest to have a check box somewhere that says "only look for files with paths too long"?

Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#16 Thu, 18 Apr 2013 20:51:54 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#16 FileSeek Awesome, glad to hear it Pete! ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#15 Thu, 18 Apr 2013 20:43:32 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#15 FileSeek Keith and John,
Long path delete for any folder (or intermediate folder) now seems to be working in bv11.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#14 Tue, 16 Apr 2013 20:59:06 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#14 FileSeek So I spoke too soon. Done some more testing. Use Delimon to create long path. Then pick one of the folder names. Use FileSeek to find it and then try and delete it. FileSeek doesn't delete but no error.
This is now with bv10.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#13 Tue, 16 Apr 2013 20:53:01 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#13 FileSeek Awesome, glad to hear it! Just let us know if you do run into any further issues :) ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#12 Tue, 16 Apr 2013 20:51:12 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#12 FileSeek Weird - its working now. Also the method for deleting worked. I will keep testing.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#11 Tue, 16 Apr 2013 20:31:55 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#11 FileSeek Strange! How did you create that test path? I created a really long path using Tools > Create and Test Folders in Delimon, and FileSeek can find folders all the way to the end of the folder chain. I tested in Windows 7 and Windows 8.

Edit: We've just posted Beta 10 as well. Could you give that a try? ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#10 Tue, 16 Apr 2013 19:35:04 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#10 FileSeek Tried this but is doesn't work. However I believe vb9 is broken now for long file paths.
Please see the images for returned folders\files showing in both Delimon and FileSeek.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#9 Tue, 16 Apr 2013 18:44:41 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#9 FileSeek Unfortunately it's more or less impossible for us to determine which folder is past the long path threshold. The character limit is 260 characters, so take this scenario for instance:
  • The full path for "Folder A" is 240 characters
  • "Folder A" has two files, "blahblah" and "blahblahblahblahblahblah"
  • Since "blahblah" is only 8 characters, it fits in the limit, but "blahblahblahblahblahblah" pushes it over the limit
  • So, is "Folder A" an invalid folder that you would want to delete, even though it contains valid files?

I think what would probably work for you, although it's a bit manual, would be to drill down in Explorer to find the folder you want to delete, then just search FileSeek for that folder name (you can put it in the Include Files box). When it shows up in the search result, you can delete it using FileSeek.

Hope that makes sense. If I missed anything, let me know! ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#8 Fri, 12 Apr 2013 21:55:58 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#8 FileSeek Keith and John,
I see you have added the functionality to remove files that exist at the end of a very long path. Can you add some feature to remove the folders as well? I know your tool is FileSeek and we are talking folders now - but it would be great if it could handle theses in some way. I know that one would need to be able to navigate the folder space and decide where along the whole path things broke and remove from there. A typical problem is with Macromedia\Flash files that can create huge path lengths.
Basically removing the file is only half the problem.
Pete ]]> RE: Feature request for path too long https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#7 Fri, 05 Apr 2013 17:41:10 GMT Binary Fortress Software https://www.fileseek.ca/Discussions/View/feature-request-for-path-too-long/?ID=220fc2de-30c3-44f4-8311-12fc4b5cadec#7 FileSeek Thanks Pete! We're currently testing out some stuff and we'll hopefully be able to add full long path support for one of the next couple of betas. We'll keep you posted! ]]>