Windows 10: Long file path problem on non-C drives

I think I found a strange bug/limitation in Windows 10 related to long file paths (260+ characters). In short: dragging and dropping long path files from Explorer to a program's window fails, if the file is on a non-system (not C:\) drive. I attached an example file, so that you can easily try and reproduce this, for example: 1. Create a folder called test on C:\ and D:\ (so, C:\test\ and D:\test\). 2. Extract the attached .zip directly into these two folders. 3. Open a new blank instance of Notepad. 4. Drag and drop the .txt from either of the above folders into Notepad. The result is that the .txt from the C:\ drive loads fine, but the one from D:\ doesn't load at all. This is weird, because both have the exact same path length. Oh and the "Enable Win32 long paths" setting in GP makes no difference.

:)

 

Explorer support for zip files with long file paths

I suggest you try Long path tool is the very good program for easily delete, copy & rename long path files, error, unlock solution.
Try it and solve your problem.
I used long path tool and I solve my error, unlock problem solution.

 

Add a path to $PATH?

what exactly do you need to decipher about that path line? also, what are you installing? perhaps i can help.

 

Add a path to $PATH?

Yeah, I think you're right. I think the purpose of the echo command was to check if ~/bin was in the $PATH file. My problem is that I can't decipher the output and I don't know how to add ~/bin to the $PATH file.

Just for clarification, the snippet of instructions I gave is just a few steps in the installation process. Nothing is actually supposed to be installed with those steps.

Thanks for the reply.