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).
HOw do you make teh 430 characters work? I have onedrive and still get creamed at abotu 240 characters?
I googled this because my folder names are getting cut off too!! I did not make them up, it was Itunes. I am hoping that the correct metadata is embedded into the MP3s themselves, but this is really stupid!
There are many many things about navigating thru my folders that is intensely irritating.
1. It does not find anywhere near close to all my files.
2. I have to scroll through thousands of folders (and I don't even know where iTunes put them...that is another whole stupid thing, like putting all greatest hits of an artist under compilations, which is only findable under "The Very Best of...." or something like that which means I can't find stuff at all. I don't know if it never got uploaded, or is simply lost forever. Again, an adequate search engine would have been nice.
3. Cannot open folders in a new window. This would mitigate much of the annoyance of this following scenario...ie. after examining contents of folder W (near the end of the lest), I must hit the back arrow and go back to A. Then scroll all the way down to get to Z.
When you have to do this 100 times because I am checking to make sure all my iTunes store purchases made it to OneDrive (some didn't and I don't know why), it is SUPER TEDIOUS!!
Is this what happens when you outsource all your IT and pay peanuts? I am just curious.
I have totally given up on OneDrive as a means of ever actually playing the cloud copy of my music [which is what I wanted more than anything]. I will start uploading it in small bits to Google Play since that at least works!!
C. R. Williams commented
Still not working after a number of years. I wish my company would just dump the MS products for something that really works, like Google for Business. Onedrive for Business is a kludge at best, it certainly isn't a polished product.
Same issue here after migrating from Dropbox. This sounds like a problem from last century. Why is it still here?
Brad Wilson commented
Whilst this seems to have given me some relief (not complete relief) when working in Windows Explorer, if I save a file via MS Word, I encounter all sorts of issues when the pathname is >256 chars. One of the issues is that word will just complain and not allow me to save a doc. Another issue I've seen is that it autosaves the doc with the old DOS truncation of folder/file names (eg DOCUME~2\CONSUL~1\...); this of course creates a whole new directory tree in my onedrive account whenever this occurs, requiring me to regularly clean up.
Little rant: I've had so many issues with Onedrive after migrating my terabyte or so of stuff from Dropbox. I'm too far in now to go back and I am saving money, but boy do I regret it. Microsoft, your customers should not be feeling such deep regret for switching to your products. As an engineer myself, I'm dumbfounded by some of the quality issues I've encountered. Not just annoyed, but really quite dumbstruck. You know when you see those viral photos online of shoddy building works that are so stupid you can only shake your head and wonder in complete bewilderment how anyone could have allowed them to be signed off - well that's the kind of bewilderment I feel when I encounter some of these issues and limitations with Onedrive (like this pathname character limit that "covers the vast majority of customers" but still clearly causes debilitating problems for the vast minority. Why not just bring it inline with Windows 10 character limits and fix it for everyone???). I truly don't get it.
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.
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