I got that "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" error when I was moving documents across folders. I know there are ways to disable that file path length restriction, but those ways just did not work on my laptop.
https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/ offers two solutions to get rid of the restriction, the second of which resorts to the use of Group Policy (dpedit.msc). As I am using a Windows 10 Home Edition, the second solution does not work. I tried to install dpedit.msc as instructed here (Windows Starter Edition, Home and Home Premium do not include gpedit, how do I install it?), but for some reason it did not work as demonstrated -- I downloaded that zipped folder and ran the extracted setup.exe file. Following the execution, however, I tried to access gpedit.msc command via RUN as well as START Menu search box, but my laptop failed to locate gpedit.msc.
So I tried the first solution. I looked up regedit and followed everything and changed the value date from 0 to 1. It still did not work, even after I logged off, restarted the computer, and logged back in.
This is giving me so much headache, so I appreciate it if someone can shed some light as to what led to the foregoing issues and how to get rid of the file path restriction.
P.S. I am a tech amateur, so any walk-through or explanation in layman terms would best help, thanks!
Answer
thanks for all the inputs and my apology if this is a duplicate. I downloaded OneCommander as instructed here and it worked. OneCommander certainly cannot override/get ride of the file path restriction but it certainly (at least in my case) bypassed it. For your reference, mine is a version 1607, home edition of Windows 10.
No comments:
Post a Comment