The 260 character limit in Windows

[a cooperator]

Hi,

I have read in this article Microsoft ends the 260 long path limit (sort of)


I have installed Windows 10 Home 64-bit. However, when following the steps below found in the article above,

Spoiler

How to enable support for long paths using the Group Policy Editor


Please note that the feature is currently only available as part of the latest Fast Ring Windows 10 Insider Build.

It seems likely that Microsoft will make it available with the Anniversary Update that it plans to release this Summer.
1.Tap on the Windows-key, type gpedit.msc, and hit enter.
2.Confirm the UAC prompt if it appears.
3.Use the hierarchy on the left to navigate to the following policy: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.
4.Locate the Enable NTFS long paths policy and double-click on it.
5.Switch its state to enabled.
6.Click ok.

Using the Registry instead

You can enable the policy in the Registry directly as well.
1.Tap on the Windows-key, type regedit.exe and hit enter.
2.Confirm the UAC prompt.
3.Navigate to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies
4.Check if the key LongPathsEnabled exists.
5.If it does not exist, right-click on Policies and select New > Dword (32-bit) Value from the menu.
6.Name it LongPathsEnabled.
7.Set its value to 1 to enable the feature.

I didn't find anything listed to me when typing 'gpedit.msc'. So, I think that this 'gpedit.msc' is not available in Windows 10 Home. Also, when I navigated to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\", I didn't find any entity like "Group Policy Objects". I only found 'Group Policy'. However, when expanded the 'Group Policy', there is no entity like '"{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies" inside 'Group Policy'.

How to use enable this feature???
I used programs such as Long Path Fixer to resolve issues that I am experiencing. However, none of them solved the issue

 

[Math Geek]

group policy is only available in win 10 pro. it's not in home so you can't use this trick on your pc.

 

[rtware923]

Did you try the regedit option in the guide you posted?

 

[a cooperator]

Did you try the regedit option in the guide you posted?

Thank you both of you very much,
Yes, I did. when I navigated to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\", I didn't find any entity like "Group Policy Objects". I only found 'Group Policy'. However, when I expanded the 'Group Policy', there is no entity like '"{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies" inside 'Group Policy'.

Also, I didn't find anything listed to me when typing 'gpedit.msc'. So, I think that this 'gpedit.msc' is not available in Windows 10 Home.

 

[Math Geek]

group policy is not available in win 10 home. it is only in pro version. so the registry edit won't work since the policy is not there to begin with.

perhaps you can find a way to shorten the file structure some. gonna need to bring the folders closer to the root one way or another. make some new categories and start moving folders about all you can do.

 

[a cooperator]

group policy is not available in win 10 home. it is only in pro version. so the registry edit won't work since the policy is not there to begin with.

perhaps you can find a way to shorten the file structure some. gonna need to bring the folders closer to the root one way or another. make some new categories and start moving folders about all you can do.

Thanks a lot,
Group Policy is available in Windows 10 Home. (screen shot below). However, as descried in the tutorial, I should navigate to 'Group Policy Objects', which is not available in my registry.
When I navigated to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\", I didn't find any entity like "Group Policy Objects". I only found 'Group Policy'. However, when I expanded the 'Group Policy', there is no entity like '"{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies" inside 'Group Policy'.

Also, why I didn't find anything listed to me when typing 'gpedit.msc'. So, I think that this 'gpedit.msc' is not available in Windows 10 Home as well.


I am sorry I don't get what you meant with this "gonna need to bring the folders closer to the root one way or another. make some new categories and start moving folders". I.e. How to do so?

P.S. I really have been faced with annoying issue with long paths in windows systems, I've tried many long path-solving programs. However, none of them worked well with me.
As a result, you think the tool built-in in Windows 10 pro is perfectly solving the issue with the long names of folders and files.

 

[Math Geek]

what i mean is that the 260 character limit is the full path of the file such as c:user/my documents/music/80's/rap/old school/run dmc/cd name/song name.mp3

all those folders under folders under folders hits the limit. to fix it create more folders closer to the c: such as c: user/my documents/music/run dmc/cd/song title.mp3 drops the characters a lot. whatever file organization you are using is just too deep with folders. make some more main categories to sort into and you'll shorten how many characters it takes to display the file name. that or your file names themselves are too long. if that's the case i'm sure you can shorten them some and not forget what the file is.

and again group policy is NOT in win 10 home. the registry folder is there but it does nothing at all since gpedit is not installed on the system. you can delete that folder and nothing will change for you at all. it's just a hold over from development.

see here from MS what is and is not in each windows version https://www.microsoft.com/en-us/WindowsForBusiness/Compare

 

[a cooperator]

what i mean is that the 260 character limit is the full path of the file such as c:user/my documents/music/80's/rap/old school/run dmc/cd name/song name.mp3

all those folders under folders under folders hits the limit. to fix it create more folders closer to the c: such as c: user/my documents/music/run dmc/cd/song title.mp3 drops the characters a lot. whatever file organization you are using is just too deep with folders. make some more main categories to sort into and you'll shorten how many characters it takes to display the file name. that or your file names themselves are too long. if that's the case i'm sure you can shorten them some and not forget what the file is.

and again group policy is NOT in win 10 home. the registry folder is there but it does nothing at all since gpedit is not installed on the system. you can delete that folder and nothing will change for you at all. it's just a hold over from development.

see here from MS what is and is not in each windows version https://www.microsoft.com/en-us/WindowsForBusiness/Compare

Thanks a lot,
Could you have seen my screen shot?

1- In the tutorial of MS ends the long path issue in Windows 10, there are two ways to solve the long path issue:

Firstly: 'Gpedit.msc', which is NOT available in my Windows 10 Home.
1.Tap on the Windows-key, type gpedit.msc, and hit enter.
2.Confirm the UAC prompt if it appears.
3.Use the hierarchy on the left to navigate to the following policy: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.
4.Locate the Enable NTFS long paths policy and double-click on it.
5.Switch its state to enabled.
6.Click ok.

Secondly "Using the Registry instead"

You can enable the policy in the Registry directly as well.
1.Tap on the Windows-key, type regedit.exe and hit enter.
2.Confirm the UAC prompt.
3.Navigate to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies
4.Check if the key LongPathsEnabled exists.
5.If it does not exist, right-click on Policies and select New > Dword (32-bit) Value from the menu.
6.Name it LongPathsEnabled.
7.Set its value to 1 to enable the feature.


2- In the tutorial of MS ends the long path issue in Windows 10, it is said 'Group Police objects' entity, and not 'Group Policy' entity?

3- In the tutorial of MS ends the long path issue in Windows 10, it is said 'Please note that the feature is currently only available as part of the latest Fast Ring Windows 10 Insider Build. It seems likely that Microsoft will make it available with the Anniversary Update that it plans to release this Summer.". What is meant with latest Fast Ring Windows 10 Insider Build' - Which edition is it?

 

[Math Geek]

right, in win 10 pro it would have the right folders. that folder is not meant for the same thing as group policy. similar name but different function.

that first link you gave had this as an option http://www.ghacks.net/2014/07/23/access-blocked-files-folders-long-path-fixer-windows/ it's a program that is supposed to help with this limits. never used it but it might be something that can help you out. have a look and see if it does what you are looking for.

 

[a cooperator]

right, in win 10 pro it would have the right folders. that folder is not meant for the same thing as group policy. similar name but different function.

that first link you gave had this as an option http://www.ghacks.net/2014/07/23/access-blocked-files-folders-long-path-fixer-windows/ it's a program that is supposed to help with this limits. never used it but it might be something that can help you out. have a look and see if it does what you are looking for.

Thanks a lot,
In windows 7 and earlier systems, MS didn't do any fix for long path. So, how did you manage with that while running Windows 7 or earlier

 

[Math Geek]

i did not have to manage it as it was never an issue for me. can honestly say i have never rn into the character limit in my daily pc usage. so never had to try and work around it.

 

[USAFRet]

In addition, this is not available yet unless you are running the most recent release of the Insider Preview.
It is not pushed out to retail installs yet. That will probably come with the Anniversary release next month.

 

[a cooperator]

i did not have to manage it as it was never an issue for me. can honestly say i have never rn into the character limit in my daily pc usage. so never had to try and work around it.

I have tried long path fixer, however, it didn't help me with long destination. I am still faced with the same 'too long destination' error. I am very surprised why those users commented 'an excellent solution' in their comments under that program website.
Here below is an example for a too long file name. When trying manually to move it to a destination, I found these 'too long destination' error below .

When trying to use the long path fixer to move it, I found this error below.

Yes, you might think that I must change permissions since the error say ''you don't have the correct permissions to move this file' as in screen shot above. However, when trying moving another file name which is NOT long, then the long path fixer moved it without changing any permissions. --- which means issue is not related to permissions. However,that long path fixer cannot move the too long file names as well. Or otherwise, I would be faced with the same error while moving the file name which is too short.

 

[a cooperator]

Some user told me that "You don't seem to get it - this feature "How to enable support for long paths using the Group Policy Editor" will help only with apps that specifically make use of it, and clearly File Explorer still doesn't and is stuck with the old 260 char limit.
Also yes, the Group Policy Editor isn't available in Win10 Home as you managed to figure out.
----------------------------------------------------------------------------------------------------------
I realized that Windows 10 Home doesn't have Group Policy Editor. However, Is that user kidding with me when saying this feature of enabling long path will not work on the File Explorer, and File Explorer will still use the old 260 char limit.
. Then what benefits are there from this article? This articles about how to enable the long path limit feature.
The issue I am faced with while moving a file from one location to another is "The destination Path Too long: The file would be too long for the destination folder". Will "enable support for long paths using the Group Policy Editor" not be useful?

 

[USAFRet]

Why not fix the actual problem? That being the actual path and filename is indeed too long.

What are you actually trying to move? What is the actual filename?

 

[a cooperator]

Why not fix the actual problem? That being the actual path and filename is indeed too long.

What are you actually trying to move? What is the actual filename?

Thanks a lot,
Could you please read my reply below again carefully? I have not said that I tried using the feature of enable long path limit' in Windows 10 since I couldn't find it enabled in Windows 10 Home.

However, another user told me this below
"You don't seem to get it - this feature "How to enable support for long paths using the Group Policy Editor" will help only with apps that specifically make use of it, and clearly File Explorer still doesn't and is stuck with the old 260 char limit.
Also yes, the Group Policy Editor isn't available in Win10 Home as you managed to figure out."
----------------------------------------------------------------------------------------------------------

I replied to him that I realized that Windows 10 Home doesn't have Group Policy Editor. However, Is that user kidding with me when saying this feature of enabling long path will not work on the File Explorer, and File Explorer will still use the old 260 char limit.
. Then what benefits are there from this article? This articles about how to enable the long path limit feature.
The issue I am faced with while moving a file from one location to another is "The destination Path Too long: The file would be too long for the destination folder". Will "enable support for long paths using the Group Policy Editor" not be useful?


Besides, about your Question "What are you actually trying to move? What is the actual filename"
Have you had a look at my last screen shots posted before in previous posts?

P.S. I am really stumbled with why some comments are not shown here, although they are received to my email in the reply notifications.

 

[USAFRet]

As noted above, the Group Policy editor is not available in Win 10 Home.

I'm not entirely sure of what the other person meant regarding it only works with specific apps.
No idea.

Yes, I looked at your previous pics.
The 'file' seems to be "The Synaptics Touchpad blah blah..."

THAT IS TOO LONG!
Change that file name.

 

[a cooperator]

As noted above, the Group Policy editor is not available in Win 10 Home.

I'm not entirely sure of what the other person meant regarding it only works with specific apps.
No idea.

Yes, I looked at your previous pics.
The 'file' seems to be "The Synaptics Touchpad blah blah..."

THAT IS TOO LONG!
Change that file name.

Thanks a lot,
If I will need to shorten the name file manually, then what benefits are there from this article "How to enable support for long paths using the Group Policy Editor?

I am willing to upgrage Windows 10 Pro, however, even this will not fix my issue according to the user reply below
"You don't seem to get it - this feature "How to enable support for long paths using the Group Policy Editor" will help only with apps that specifically make use of it, and clearly File Explorer still doesn't and is stuck with the old 260 char limit.
Also yes, the Group Policy Editor isn't available in Win10 Home as you managed to figure out."


The other person comments on this article : http://www.ghacks.net/2016/05/27/microsoft-260-long-path-limit/
"How to enable support for long paths using the Group Policy Editor
Please note that the feature is currently only available as part of the latest Fast Ring Windows 10 Insider Build.
It seems likely that Microsoft will make it available with the Anniversary Update that it plans to release this Summer.
Tap on the Windows-key, type gpedit.msc, and hit enter.
Confirm the UAC prompt if it appears.
Use the hierarchy on the left to navigate to the following policy: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.
Locate the Enable NTFS long paths policy and double-click on it.
Switch its state to enabled.
Click ok.
Using the Registry instead
You can enable the policy in the Registry directly as well.
Tap on the Windows-key, type regedit.exe and hit enter.
Confirm the UAC prompt.
Navigate to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies
Check if the key LongPathsEnabled exists.
If it does not exist, right-click on Policies and select New > Dword (32-bit) Value from the menu.
Name it LongPathsEnabled.
Set its value to 1 to enable the feature."

 

[USAFRet]

That file name by itself is 79 characters!
1/3 of the actual 260 char limit.

Stop beating yourself over the head with a tool that you do not have access to in your OS.
And don't change your OS for this single purpose.

 

[USAFRet]

You've been messing with this for 3 months. Just change the file name.
Or copy that jpg and put it somewhere else, not so deep in a folder tree.

 

[a cooperator]

That file name by itself is 79 characters!
1/3 of the actual 260 char limit.

Stop beating yourself over the head with a tool that you do not have access to in your OS.
And don't change your OS for this single purpose.

Thanks a lot,
Yes, the file itslef is named with about 79 characters. But, I need that name file since I classify my files in archive loaction path in my HDD
I am really always faced with this issue since I have many file names with such a long file name.

I am willing to upgrage Windows 10 Pro, however, even this will not fix my issue according to the user reply below
"You don't seem to get it - this feature "How to enable support for long paths using the Group Policy Editor" will help only with apps that specifically make use of it, and clearly File Explorer still doesn't and is stuck with the old 260 char limit.
Also yes, the Group Policy Editor isn't available in Win10 Home as you managed to figure out."


The other person comments on this]http://www.ghacks.net/2016/05/27/microsoft-260-long-pat...]this article[/url] :"How to enable support for long paths using the Group Policy Editor
Please note that the feature is currently only available as part of the latest Fast Ring Windows 10 Insider Build.
It seems likely that Microsoft will make it available with the Anniversary Update that it plans to release this Summer.
Tap on the Windows-key, type gpedit.msc, and hit enter.
Confirm the UAC prompt if it appears.
Use the hierarchy on the left to navigate to the following policy: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.
Locate the Enable NTFS long paths policy and double-click on it.
Switch its state to enabled.
Click ok.
Using the Registry instead
You can enable the policy in the Registry directly as well.
Tap on the Windows-key, type regedit.exe and hit enter.
Confirm the UAC prompt.
Navigate to the following key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy Objects\{48981759-12F2-42A6-A048-028B3973495F}Machine\System\CurrentControlSet\Policies
Check if the key LongPathsEnabled exists.
If it does not exist, right-click on Policies and select New > Dword (32-bit) Value from the menu.
Name it LongPathsEnabled.
Set its value to 1 to enable the feature."

 

[USAFRet]

Thanks a lot,
Yes, the file itslef is named with about 79 characters. But, I need that name file since I classify my files in archive loaction path in my HDD
I am really always faced with this issue since I have many file names with such a long file name.

You need a better file and folder naming scheme.

Is your Win 10 Home updated to the Anniversary release, 1607?
If so, is this function available?

 

[a cooperator]

Thanks a lot,
Yes, the file itslef is named with about 79 characters. But, I need that name file since I classify my files in archive loaction path in my HDD
I am really always faced with this issue since I have many file names with such a long file name.

You need a better file and folder naming scheme.

Is your Win 10 Home updated to the Anniversary release, 1607?
If so, is this function available?

Yes I have my Win 10 Home updated to the Anniversary release, 1607. But, I don't know what you mean with is this function available. You mean with "a better file and folder naming scheme" Or with the Group Policy Editor?

The Group Policy Editor is not available. However, if you meant "a better file and folder naming scheme", I don't know how to find it on Windows 10 the Anniversary release, 1607

 

[USAFRet]

By "a better file and folder naming scheme", I meant that having a file name that is 79 characters long (which could be maybe 15 characters and convey the same information), that is probably nested 5 deep in a folder tree...

That is the "better file and folder naming scheme" that you need.

 

[a cooperator]

By "a better file and folder naming scheme", I meant that having a file name that is 79 characters long (which could be maybe 15 characters and convey the same information), that is probably nested 5 deep in a folder tree...

That is the "better file and folder naming scheme" that you need.

Thanks a lot,
But why did you asked me if I have my Win 10 Home updated to the Anniversary release, 1607. And then you asked me is this function available.
What You mean with those questions?
In addition, you told me previously this is not available yet unless you are running the most recent release of the Insider Preview.
It is not pushed out to retail installs yet. That will probably come with the Anniversary release next month.

And while using the Long Path Fixer' tool, I found an error 'possible you don't have the correct permissions to move this file" while moving a long file name.(have you seen my screen shot posted before)