Could you check that the program is compatible with extra long file name lengths and file path lengths? (There is a registry setting in windows that allows to exceed the usual limitations for file/path name lengths.) Could you then please mention in the version history that this has been checked. Thank you. I am always scared some files might be missing in the list.
I can confirm that the Win32 API she used will not copy extremely long names as my machine is set up now. As it happens, I don't want to replicate those folders anyway because they are derived by running composer, or npm, to download other people's code into a project. So, I used global exclusions to exclude vendor/ and node_modules/ folders. The whole reason I noticed I was trying to replicate them was the warnings in the Replicator log files. Windows' own File History had the same issue.
Woops, you're talking Directory Printer and I'm thinking Replicator.
I can use my Replicator log to find the files that were named too long to replicate and then run Directory Printer to see if the problem is there, too, and then check to see if registry fix will fix it.
I do know that Directory Printer isn't able to navigate to the direct access UNC -- a system put into place by Microsoft to deal with super-long filenames. For instance \\?\C:\Users\Joe\Documents\....