Destination path too long
Baptiste_PC Posted messages 2 Status Membre -
Hello,
Despite my extensive research to counter this issue, I still encounter the following error message:
Destination path too long
The file name(s) is/are too long for the destination folder. Reduce the length of the file name and try again, or specify a location where the path is shorter.
Initially, I changed the LongPathsEnabled value from 0 to 1 in the registry editor, restarted, but nothing, the problem persists.
Secondly, I followed the instructions in this video (https://www.youtube.com/watch?v=aNpy9r9wkE0) using Windows Powershell in administrator mode, but again, nothing has changed.
Finally, I went through the Local Group Policy Editor - which I accessed, being on Windows 11 Home, by this method (https://www.justgeek.fr/installer-editeur-de-strategie-de-groupe-locale-windows-11-home-88159/) - and enabled long Win32 path names and then restarted. Result: none.
Does anyone have a solution for me? Thank you in advance!
2 réponses
Hello,
The manipulation in the last link is known to provide only cosmetic effects; we can open gpedit.msc, but no modifications are validated: prefer Policy Plus from the same link.
That said, if nothing works, the most likely cause is the use of applications in 32-bit compatibility mode that do not support long paths, and the only solutions are to use other 64-bit applications or to shorten the target file name and/or the hierarchy to achieve this.
After opening Policy Plus, I see that the status of Enable Win32 long path names is Enabled. Clearly, going through the Editor has indeed modified it. But the problem persists.
I want to clarify that this is not about using an application but simply creating a folder within a folder, within a folder, and so on, which leads to a long path... until it's no longer possible to create a new one. I would prefer not to reach the point of having to modify the names of these folders, as that would be detrimental to their identification.
