Windows 10: Long directory / file name support PLEASE Ms in a Windows update

Hi there

Please Ms can you fix the restriction of file + directory (folder) name length so they can be LONGER than approx 200 Chars

For normal office type documents long file names won't be encountered very often but if you have large capacity HDD's with a lot of say Music files on them decently tagged with meaningful names it's easy to bump up against the restriction.

While some native programs might have no problem - anything that uses say file explorer to search / browse / manipulate the files will come up against the restriction and the name display will be truncated to 8 chars (from the old Dos 8.3 labelling scheme).

The files will still play in VLC or whatever but if you don't know what you are playing it renders the clients essentially USELESS. !!!!

Some of my Windows clients are unable to correctly see the proper names of my music files from my NAS and I don't want to have to go through WEEKS of re-naming, re-tagging etc etc.

This is what I mean

NAS files :






Comes out in File explorer as follows :






Cheers
jimbo

:)

 

Quick Access Crashes Explorer

Same here. Windows explorer crashes and restarts when it comes to very long file names. Even just accessing the directory path where the the file with the long name is can cause it to crash. Sorting by columns, enabling preview pane or details pane, using
'Details' folder view or changing folder view type also crashes Explorer with long file names. Sometimes, it crashes when copying, moving or renaming files with long file names.

I enabled Win32 long paths but didn't make a difference. Does even Windows explorer support this? On Windows 7 this used to happen but very rarely. With Windows 10 it is very frequent and even more so with the Anniversary Update. With Free Commander
can access files with long file names without problems.

 

Long File Paths When Is Real Support Comming

When will Windows really support long file paths? I have heard rumors of it since 1999. Currently, I have been working on a special project to add long file name support to .Net apps. They are currently limited to about 250 characters.

Today I was searching for something recursively, and noticed that the dir command can't handle a long file path that I created. I am running Windows 10 with the latest updates. Using dir command from in cmd.exe

'Dir /s' returns the following error on my system:

The directory name C:\mytemp\along\long\verylonglonglong\long1long2long3long4long5long6long7long8long9\long1long2long3long4long5long6long7long8long9\long1long2long3long4long5long6long7long8long9\long1long2long3long4long5long6long7long8long9\long1long2long3long4long5long6long7long8long9
is too long.

 

It seems as if MS may have introduced that change, then maybe withdrawn it, 'cos there are articles referring to a GPO option (which requires a matching entry in application manifests, apparently - Winaero).

I can't see the GPO, and there is the same comment at the end of Winaero's article. Hmm.
Is it in the latest Insiders' Build?

How to enable NTFS Long Paths in Windows 10 - Winaero
Microsoft removes 260 character limit for NTFS Path in new Windows 10 Insider Preview - MSPoweruser
How to enable paths longer than 260 characters in Windows 10

 

Hi there

Whatever the "technet" doc says - the wretched thing STILL doesn't work if say you use any sort of Media player where you use Browse File function on its menu -- as my first post shows.

(NAS server - Linux Centos 7,1 -- Windows clients Windows 10 Pro x-64).

Cheers
jimbo

 

f14tomcat has confirmed the GPO doesn't exist in the latest insider's build... so no long path support...*cry