Yes, these windows path length limitations are pretty much global. I believe @lassoan maybe said there’s a way to enable a longer path mode? I don’t use windows much.
That would be great - let us know if speaking to one of us could help answer any questions they have. I and others have worked with many institutions about their use of and contributions to Slicer.
Paths to DICOM files can easily get extremely long when they are named automatically based on long DICOM tags (UIDs, series description, etc.).
About 1-2 years ago we implemented automatic filename generation from cryptographic hash of UIDs for filenames that are copied into Slicer’s DICOM database. Therefore, copying DICOM files into the database is very unlikely to fail due to path length limitations.
However, if the input files already have longer paths than MAX_PATH_LIMIT (about 260 characters), created using UNC paths or application with long path support then Slicer most likely cannot read those files. I’ve added some details about how long file support could be added to this issue, but in the short term we need to keep avoiding paths longer than 260 characters on Windows.