Windows 10: Destination path too long after enable NTFS long path

Discus and support Destination path too long after enable NTFS long path in Windows 10 Customization to solve the problem; I have windows pro 10 education and 1903 version. I enable NFTS long path and update the group policy with this command: gpupdate /target:computer... Discussion in 'Windows 10 Customization' started by StavrosStavridis2, Nov 26, 2019.

  1. Destination path too long after enable NTFS long path


    I have windows pro 10 education and 1903 version. I enable NFTS long path and update the group policy with this command:

    gpupdate /target:computer /force


    But when I copy-paste folders to an external drive I still get the error Destination path too long The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.


    Thanks in advance.

    :)
     
    StavrosStavridis2, Nov 26, 2019
    #1

  2. Destination path too long

    Hi,

    Long paths works for NTFS file system only.

    https://docs.microsoft.com/en-us/windows/win32/...

    Enable Long Paths in Windows 10, Version 1607, and Later

    Starting in Windows 10, version 1607, MAX_PATH limitations have been removed from common Win32 file and directory functions. However, you must opt-in to the new behavior.

    To enable the new long path behavior, both of the following conditions must be met:

    The registry key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem LongPathsEnabled (Type: REG_DWORD) must exist and be set to 1. The key's value will be cached by the system (per process) after the first call to an affected Win32 file or directory function
    (see below for the list of functions). The registry key will not be reloaded during the lifetime of the process. In order for all apps on the system to recognize the value of the key, a reboot might be required because some processes may have started before
    the key was set.

    Note

    This registry key can also be controlled via Group Policy at Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long paths.

    https://mspoweruser.com/ntfs-260-character-wind...

    If you wish to utilize this feature, however, you will be required to make some edits to using Group Policy. Follow the steps below:

    Open Group Policy Editor (Press Windows Key and type gpedit.msc and hit Enter key.

    Navigate to the following directory: Local Computer Policy > Computer Configuration > Administrative Templates > System > Filesystem > NTFS.

    Click Enable NTFS long paths option and enable it.

    Regards,

    Lee

    ________________________________________________________

    Standard Disclaimer: There maybe links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly
    research any product advertised on the sites before you decide to download and install it.
     
    Lee Teck Koon, Nov 26, 2019
    #2
  3. Win User
    GPO: enable win32 long paths

    I saw that the Windows 10 Anniversary Update was supposed to address the limitation of long file paths and names. According to what I found, the new GPO entry of "enable NTFS long paths" was supposed to be added, but I didn't see it. Upon further research,
    I did find the "enable win32 long paths" option one level up in the GPO.

    Question: Was this supposed to address the problem? After I enabled it, rebooted the computer and confirmed that the setting was still enabled, I tried to copy a file (via File Explorer) from a local hard drive (G:\*.*) to a server share (\\SERVER\SHARE),
    but it failed for the same old reason that the pathname was too long. Does this only work locally, or does it only work with specific capabilities, like PowerShell?
     
  4. Destination path too long after enable NTFS long path

    Long Path Setting not working

    Seems Enabling Win32 long path to overcome the 260 character restriction has not yet resolved the issue. I have enabled Win32 long path under group policy editor--> Filesystem and also the reg key D word setting but continue to receive error " The file
    name would be too ling for the destination folder....."
     
    aaronvictor, Nov 26, 2019
    #4
Thema:

Destination path too long after enable NTFS long path

Loading...
  1. Destination path too long after enable NTFS long path - Similar Threads - Destination path too

  2. Destination Path to Long

    in Windows 10 Gaming
    Destination Path to Long: Hi. I'm a musician and I have to keep my files super organized. With lots of subfolders and long descriptive names. I have looked around for a good solution or an explanation on how it works for Windows 10 for this topic and have found no info that resolves my problem or that...
  3. Destination Path to Long

    in Windows 10 Software and Apps
    Destination Path to Long: Hi. I'm a musician and I have to keep my files super organized. With lots of subfolders and long descriptive names. I have looked around for a good solution or an explanation on how it works for Windows 10 for this topic and have found no info that resolves my problem or that...
  4. Destination Path to Long

    in Windows 10 Network and Sharing
    Destination Path to Long: Hi. I'm a musician and I have to keep my files super organized. With lots of subfolders and long descriptive names. I have looked around for a good solution or an explanation on how it works for Windows 10 for this topic and have found no info that resolves my problem or that...
  5. Path too long

    in Windows 10 Gaming
    Path too long: I downloaded a big file and I need to extract it, but some paths are too long.I worry that if I rename the file stuff won't work as intended, also there are a lot of long files so I don't really know what to do....
  6. Path too long

    in Windows 10 Software and Apps
    Path too long: I downloaded a big file and I need to extract it, but some paths are too long.I worry that if I rename the file stuff won't work as intended, also there are a lot of long files so I don't really know what to do....
  7. Destination Path Too Long

    in Windows 10 Network and Sharing
    Destination Path Too Long: Hello - Does anyone know which builds of Windows 10 Pro support file paths longer than 260 characters on NTFS volumes? Better yet, does anyone know how to remove that limitation? I am using Windows 10 Pro ver. 20H2 It seems that in this version the group policy "Enable...
  8. Long Path Enabled

    in Windows 10 Network and Sharing
    Long Path Enabled: Hi Team, We have been trying to increase the long path value as per the documents from Microsoft. We can create maximum of 20 sub folders beyond that we cannot go. So could you please help me in getting this sorted out. thanks. Sriram Krishnamoorthy...
  9. "Destination Path Too Long" -- despite LongPathsEnabled = 1 ??

    in Windows 10 Ask Insider
    "Destination Path Too Long" -- despite LongPathsEnabled = 1 ??: Trying to copy/dump a bunch of files & dirs from an external HDD (given by someone else), but getting the ol' "Destination Path Too Long" error ----- even tho i already have "LongPathsEnabled" set to 1 in registry (did this a long time ago). wtf? Why might this happen? HDD...
  10. Destination path too long after enable NTFS long path

    in Windows 10 Network and Sharing
    Destination path too long after enable NTFS long path: I have windows pro 10 education and 1903 version. I enable NFTS long path and update the group policy with this command: gpupdate /target:computer /force But when I copy-paste folders to an external drive I still get the error Destination path too long The file name(s)...