"Destination Path Too Long" after enabling long path names in registry?

Triad said:

I am migrating data from one PC (Windows 10) to a new PC (Windows 11).

My W10 PC had some nested folders, some of which contained longer than usual names. My W10 PC handles them fine, but when I copy them to my W11 PC, I get the "Destination Path Too Long" error message for certain subfolders.

I followed articles' instructions to change the registry setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem --> LongPathsEnabled from 0 to 1, and restarted the machine.

I still get the error message when trying to copy over the same subfolders.

Edit: It's Win11 Home, so I don't have the Group Policy Editor (gpedit.msc). I downloaded PolicyPlus and am looking for instructions on how to set the group policy there. It doesn't have the same folders / categories as what is expected based on the YouTube videos I'm watching, nor the regular Group Policy Editor categories so I'm going to have to do more digging.

Context: I am copying files for existing video editing projects. Media has been linked to various clips in large projects within software, hundreds of separate clips and elements. I could rename many folders and filenames in the copy, but that would require manually examining and potentially re-linking hundreds of files.

Edit: I see some saying that Windows Explorer does not support long paths, even with the above instructions. Which is odd.. the paths are the same length on my Win10 PC and it works..
I see multiple people recommending Directory Opus in other forums regarding this issue, as it supports long file paths, but it costs $.

Please advise?

Click to expand...

Steve C said:

I use the utility TLPD to find offending files and change their path / name to keep within the 255 character limit.
TLPD.

Click to expand...