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.
Brian Hall
shared this idea
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).
1043 comments
-
kjasi
commented
I have to seriously consider Dropbox, which sinc perfectly without any problems, instead of using one drive after I switched from PC to Mac
-
Kristofer
commented
I agree. This is limiting my use of OneDrive, even tough I'm not a software developer, I have a bunch of files already that cannot be synced with OneDrive, unfortunately.
-
Anonymous
commented
Why has MSFT not fixed this as yet? I regret purchasing Office 365 now. 1 TB of storage, and I can't sync 20GB of data because of "long file names", apparently!
-
Mike Murphy
commented
Agreed - I have BackBlaze, which backs up long file names without issue. I'd like to move over to OneDrive as a primary file server source, and sync with another computer for backup instead of the other way around (using cloud as a backup). But I keep running into multiple folders and files that are too long
-
Glenn Barker commented
This is an important one. I tried transferring over a number of files and had to go through and rename a bunch as the error would appear. The file names weren't even really that long. This is not something you want users to have to deal with if you want them to use the service.
-
Jasper Tsai
commented
Buggy Onedrive and stinkin' incompetent Onedrive team, make me regret my subscription.
-
Jasper Tsai
commented
A year later this ridiculous problem still isn't fixed. How incompetent is the OneDrive team? Stinkin' much, that's what I think.
Dropbox and Google Drive do not have this ridiculous issue. All my files, they take it. Never any problems prompted. I have regretted paying for a subscription for Office 365 already. Problems problems problems, Windows always got problems. -
Anonymous
commented
Yes I second this. Had to transfer to dropbox because of this.
-
Stephen
commented
This is a dealbreaker issue for me - back to dropbox until support is added. As a developer, many of my folder structures are long enough to cause this error. Especially node.js modules. And when it happens, I have to completely restart OneDrive for Mac client as if it's a fresh install (repick OneDrive folder, choose settings, etc).
-
JR
commented
I agree with all the comments previously issued. file name too long is a step back to the dark ages.
Please fix the problem.
-
Nittin
commented
@Omar Shahine:
Seriously ???!!! That ("Revert the pivot menu UI for WP") is what you are working on??? You find that cosmetic ameliorations are more important than this ?
-
Nittin
commented
@Omar Shahine: How can it be a complicated one when your competitors are already doing it? Maybe you should consider getting google developers to help you out?
-
John
commented
Let me add my voice to the chorus that this is a deal-breaker for OneDrive. I am stunned it has been over a year and still not addressed, when every other cloud service has no such difficulties with long path names. Microsoft, i would LIKE to give you my money. Why are you making it so hard??
-
Anonymous
commented
This gravely, gravely reduces the usefulness of onedrive since a decent archiving structure is nearly impossible. I hope this will be addressed very soon...
-
Anonymous
commented
Any update to resolving this issue?
This problem i see was first reported on Aug 21 and acknowledged by Microsoft on Aug 23. It is now Nov 19!!! I've not been able to sync for months. I had thought when I subscribed to office 365 and migrated from dropbox that Onedrive would be a better product. A quicker resolution to this issue please!
T
-
Axel Buecker
commented
I absolutely second this request ... I am in the process of migrating lots of my files to OneDrive ... but not being able to have decent long file and folder structures is from the 90's.
Please fix this ASAP !!!!! -
Artur
commented
Please do not think about it! Please do the change asap.
This is critical bug as it prevents sync of files. Changing them manually is not acceptable.
Thank you -
Daniel Sokolowski
commented
unbelievable
-
Jeff Codling
commented
This has been a problem from the beginning and I have asked them to fix it for a couple years now. It is akin to using 8.3 file names verses plain text with spaces.
OneDrive is not developer friendly at all.
-
js
commented
Cubby.com, DropBox, iCloud disk, bitcasa and others all support long file names. This is truly disappointing for OneDrive.
