Enable long file paths (aka "File Name Too Long" problem when syncing)
As a developer, I have deeply nested file structures with sometimes arduously long file names. I am unable to use OneDrive as it stands now because of this. I would like to suggest that this limitation be removed. I understand that it's probably a fundamental infrastructure issue but it's severely hampering Onedrive when compared to other competitors out there right now, despite all the other cool features.
We’ve enabled significantly longer paths for your personal OneDrive in our latest Windows and Mac releases (available from http://onedrive.com/download). You should be able to use paths up to 430 characters from the root of your local OneDrive sync folder. Our telemetry tells us this covers the vast majority of customers who have hit max path issues in the past. Note that if you have over 90 characters in your local OneDrive path (that is, from drive letter to OneDrive\) you will see characters over 90 cut into the budget of 430 characters (93 character local path will mean 427 characters available for path in the OneDrive folder).
Another problem with this is that if I simply want to sync a folder somewhere deep in the folder structure, OneDrive still syncs the entire directory tree and fails.
Even with longer paths in OneDrive, apps like Excel still can't handle the long path...
It's amazing that Google Drive and DropBox were able to get this right from the beginning, but Microsoft continues to struggle, and fails to work together with other Office apps.
Has somebody found a solution or a workaround for this issue?
And OneDrive for business...….
Visual Studio Cordova Apache generates files with names longer than 250 characters. They get copied to onedrive, but won't delete.
Joshua Richardson commented
"Wow! This program is amazing!
-did work fast
-deleted thousands of my long path files
-tested on different platforms, worked everywhere
Long Path Tool rocks! Recommended!
Still an issue - I can only have around 250 characters in the file path,
This is still an issue for me and hasn't been resolved. Using Win10 and OneDrive.
bob woodward commented
even if it just skipped the file, that would be better than aborting
Is the 430 character limit only available on Windows 10 machines? I am trying to synchronize machines that are running a variety of older Win OS and some are choking on the file length limitation.
Andres Vallistu commented
Is there already any solution? I have thousands of files which are longer that allowed. What should I do?
Apparently, I have many and I don't where they are among the terabytes of data. Please advise
Andrew Jobel commented
You Can use LONG PATH TOOL for solve this problem.It is great.
I am a University lecturer and have a diversity of file folders that leads to the same problem. How can I enable longer file names in 365?
Within seconds of me migrating my dropbox account to one drive for business I encountered these errors. It’s one drive running on DOS or something? It’s absolutely pathetic. I don’t want to use the long path migration tool to shorten all my file names I’m a developer and it’s absolutely essential that the files path structures be retained in tact as is. I’d love to switch over but for now it’s back to dropbox.
It's still happening
this is very simple, for onedrive to work as a usable capability, the filenames coped to it need to be allowed to be as long as the filenames in Windows. It's absolutely incredulous that you can't do this
try to use Long Path Tool
Doing a first migration to OneDrive just yesterday and encountered this issue with a client. SO frustrating... I'm force to create folders and drag over sub folders one by one to get them into OneDrive. Terrible user experience MS.
Please fix the pathname restriction on OneDrive. How long do we have to wait?!
Fred Smith commented
You can also use long path tool. Had same issues before.