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).
Andrew Klimek commented
Deal-breaker for me as well. I have classical albums in my music library and they often have insanely long title.
The same problem exits on MAC and there is no fix. This is a real deal breaker moving back to DropBox unless fixed in a few days. No support for Mac and the problem is the same so its not a OS issue but how OneDrive looks at files.
Ok, so I figured it out. This has nothing to do with OneDrive, it's a limitation imposed by Win API functions in Windows. These Win API functions can't accept paths longer than MAX_PATH which is 260 characters. These functions are used by a lot of programs, including Windows Explorer, so it can't create a file with an absolute path longer than 260 characters
In my case, the path in the comment bellow, is just under 260 characters, so the PC had no problem uploading it. But the laptop had a different path for the OneDrive folder (C:\Users\Dell\OneDrive) and it exceeded 260 chars. To solve this I moved OneDrive folder to C:\OneDrive and the absolute path dropped just under 260 chars. I was incredibly lucky the the path was just bellow the limit.
Bottom line, you can never have an absolute path longer than 260 characters in Windows, not just in OneDrive. It's an OS limitation. You would have the same problem in Dropbox.
This is Interesting.
Windows 7 with OneDrive had no problem uploading "D:\Data\SkyDrive\Soft\Programming\EclipsePortable\App\Eclipse\features\org.eclipse.jst.jsf.apache.trinidad.tagsupport.feature_2.5.0.v201405061851\META-INF\maven\org.eclipse.webtools.jsf\org.eclipse.jst.jsf.apache.trinidad.tagsupport.feature\pom.properties".
It's there on OneDrive.
But another laptop with Windows 8.1 with the app version of OneDrive can't download it. Great.
On August 22 Microsoft said they would look into this. People here (including myself 2/3 months ago) have been stressing that this is a deal breaker and simply bad service for months now. Could we have an update on what Microsoft is doing to fix this problem?
This is clearly because of the fake unlimited space...
YEP - PATHETIC. Clearly this is something Microsoft chooses to do. Long nae issues have been fixed for years. Dropbox works seamlessly and I have 1Tb on each. Now looking to shift the OneDrive to Dropbox as well. Not worth the hassle for the couple of bucks difference in cost per month.
Another Microsoft misstep.
Pls fix it in mac too!!!! Incredible...
You can try long path tool that are very good for easily fix. thanks
easy way try to use long path tools :). trust me it work :)
I suggest to try "Long Path Tool" program .
before I have problem cannot copy file because file name too long on Windows 7. and after I found long path tool and now my problem solved
The limitation of long file names severely limits the use of OneDrive. Compound that with the various bugs I've encountered over the past couple of months, my greatest mistake was assuming that OneDrive would function seamlessly like DropBox or Google Drive.
R. David Parker commented
I must say this is a huge issue. Working at a university as we moved to 365, One Drive limiting the characters for file names is a problem for anyone who archives pdfs.
It is ridiculous that this limitation exists, considering Onedrive is meant to seamlessly integrate with Windows 8. Windows 8 does not have a 256 character length limit, and neither should Onedrive. It is shocking that this is even an issue, it is problematic for too many people.
Robert Samuel White commented
This is a deal breaker for me. I signed up for Office 365 because of the 1TB of space it included for OneDrive, but I didn't need to. I'm a developer also so I have long paths and I cannot live without them. Dropbox and ownCloud do not have these issues. With OneDrive, the second it encounters the issue, it force closes the application making it useless to me. Please fix this!
Mikey Soft commented
OD is awful. Found this site trying to clear up sync problems around multiple devices. I am giving up and going to use another solution.
Dan Myers commented
Hi, would like to see this feature also. I deleted a long file name and its still trying to sync is and giving me errors saying that file is the culprit. How do I fix this? Thank you!
Running into this right now trying to save a Windows project on OneDrive for a class: So frustrated.
Glauco Basilio commented
In my opinion the unique reason that this bug is not fixed yet is that Microsoft does not want that users store any sort of files in his cloud that is not MS Office crafted. I think that they keep OneDrive in an buggy state to avoid people like me and you that like to keep our massive long project folders structure sync with the Cloud. This way they can advertise 1Tb fishing 365 users that will cannot use their resources by rights. Shame on you, MS
Justin Adie commented
it's a quite appalling limitation. what idiot thought that imposing an arbitrary limit (possibly related to a field length limitation in sql server) was a good idea?
tech should match our way of doing things; not force us to do things differently.
this is a deal killer for any migration to OneDrive. likewise the lack of data-sync.
MS should buy dropbox and do it properly.