Hi HomeBoy,
I recently improved support for very long paths in FileVoyager. There may still be cases that are not handled properly, but in most situations this is due to limitations of Windows itself. File Explorer exhibits the same issues for the same reasons.
Regarding the specific case in this Topic, I tested using extremely long paths created for stress testing, and everything worked correctly.
The key point is that FileVoyager does not rely on plain text paths. Instead, it uses Item ID Lists (aka PIDLs), which are binary structures used by the Windows Shell to identify objects.
A PIDL represents a path as a sequence of linked identifiers rather than a single string. Because of this, it avoids many of the traditional MAX_PATH limitations associated with text-based paths. In practice, PIDLs allow handling much longer paths than standard string-based approaches.