Solved Enable long file path names in Windows 11

LesFerch said:

A year ago, when I tested a bunch of third party file managers for long path support, I found that One Commander supports long paths, but Xplorer2 does not (not that you said it did - just clarifying).

Click to expand...

Yeah, it's one of many reasons that I've moved to OC, though Nikos, developer of Xplorer², says it has supported them for 10 years - but it is still entwined with Windows Explorer settings, so runs into the issue above.

He discussed this in a blog 8 years ago lol.

@johnlgalt @zelarra821

I just tested Xplorer² 6.0.0.3 64 bit and it worked fine for me with long paths (e.g. I was able to create new folders that extended the path length).

I also tested the 32 bit version and encountered errors in long paths. For example, I got an error when attempting to rename a folder deep in a long path. It's possible when I tested a year ago I was using the 32 bit version.

Don’t the long file path names include all parent paths, ie:

Abcdefgh.mp4 Located in Music folder would be (long name)

C:\Users\username\music\Abcdefgh.mp4

So depending on how deep OP file is located, it will reach the max length sooner, correct?

dacrone said:

Don’t the long file path names include all parent paths, ie:

Abcdefgh.mp4 Located in Music folder would be (long name)

C:\Users\username\music\Abcdefgh.mp4

So depending on how deep OP file is located, it will reach the max length sooner, correct?

Click to expand...

That is my understanding. It can cause untold problems when there is an array of subfolders.

dacrone said:

Don’t the long file path names include all parent paths, ie:

Abcdefgh.mp4 Located in Music folder would be (long name)

C:\Users\username\music\Abcdefgh.mp4

So depending on how deep OP file is located, it will reach the max length sooner, correct?

Click to expand...

Correct.

You can get around long path names a few ways discussed there. Mklink and Subst are two of them.

Ok, thanks for the information.

@dacrone
@zelarra821

As I've said "As Nauseam" -- it doesn't matter what you change in the registry or tweaks to Windows itself if the application you are using still uses the old API which doesn't support long file / path names. I'm amazed that there's still misunderstanding on this here. File explorer still uses the old API so do a lot of those windows programs that throw up a small pane when you need to select a file to use with an application.

It doesn't matter for example if you have a drain capable of emptying say 5000 litres of liquid a minute if the connector to the drain only allows a throughput of 100 litres a minute.

That's the same with Windows -- the Windows system is like the drain and the application is like the connector.

Too many people seem to just go for the complex stuff - and if you have to write your own scripts - well that's just another App accessing the appropriate API, which assuming it's enabled in Windows then it will work properly.

Most want just a decent file manager that works properly and these days with large storage NAS's it's quite easy to get files / path names that exceed the 266 byte limit.

Even macrium has a problem -- copy an image to a shared folder on a NAS and make the path longer than 266 chars. Now see if Macrium can locate the image.

Cheers
jimbo

That has nothing to do with what I posted.

LesFerch said:

@johnlgalt @zelarra821

I just tested Xplorer² 6.0.0.3 64 bit and it worked fine for me with long paths (e.g. I was able to create new folders that extended the path length).

I also tested the 32 bit version and encountered errors in long paths. For example, I got an error when attempting to rename a folder deep in a long path. It's possible when I tested a year ago I was using the 32 bit version.

Click to expand...

I contacted the Xplorer² developer on his forums, and he had this to say about the 32-bit version:

when creating long paths, there could be trouble at the crossover point where the path length exceeds 255 characters

at that point you can use CTRL+F2 to rename the semi-deep folder name (instead of F2 or when F8 creation fails)

from then on, you should be ok digging deeper

Click to expand...

So, there is a workaround for the 32-bit version to allow for longer paths that doesn't run into the Windows API brick wall.