Windows users may run into so-called long path issues when a path exceeds the maximum length of 260 characters.
It is quite easy to run into the issue. Maybe by connecting a Flash drive that you use on Linux for the most part -- which does not have this limit -- or by trying to extract an archive that is so deep in terms of directory structure, that you will end up hitting the limit.
While there are ways around this, for instance by renaming directories or by using the Long Path Fixer Tool for Windows, it may be useful sometimes to scan a system for long path issues to fix them asap.
Too Long Paths Detector is a free open source program for Microsoft Windows that you may run to scan for issues related to too long paths on Windows.
The program is provided as a 32-bit and 64-bit portable version that you can run from any location. The program does not require elevated privileges, and is pretty bare bones.
The application displays a prompt on start that gives you two choices: run the scan by selecting a root folder, or scan all drives connected to the PC at the time.
Once you have made the decision, you are asked to select a character limit. The default is 200, and the author recommends to pick a limit that is below the maximum.
Too Long Paths Detector scans the selected folder structure or all drives on the system afterwards. It places an icon in the system tray area that you may interact with to suspend the operation or exit the program.
It saves the information to a log file which it opens automatically once the scan finishes. The log file lists all folder and file paths that exceed the selected character limit. The limit is displayed in front of each folder, but the data is not sorted.
Tip: increase the character limit if you get too many results to narrow them down.
Too Long Paths Detector finds paths that are too long, but it is not designed to do anything about them. You need other tools, like the aforementioned Long Path Fixer for that.
Too Long Paths Detector is a handy administrative tool to quickly check locations or entire systems for long path violations. The program is as easy to use as it gets, but could use some nice to have features such as a sorted log file in the end or maybe an option to export the data to a csv file for further processing.
Now You: What do you do when you run into long path issues?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.