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).
I think "Boom! It's Done" has mis-understood the problem. Yes, OneDrive on the web can now hold paths of 400 characters. But the synchronisation to and from the C:\ drive is still limited to 260 chars. So if you have a folder on your C: drive that exceeds 260 chars, it DOES NOT synchronsie to the web. You can only access the 400 char limit if you never synchronise, and only access your data through a browser.
It kind of negates the benefits of the 400 character One-Drive limit, since many people prefer to synchronise and have the rich functionality of their File Explorer, rather than use the clumsy browser-only options.
To the people advocating "Long Path Tool" - yes, there are tools that allow you to access and delete longer paths on your C: drive - but why can't Microsoft just make OneDrive synchronisation work, without having to faff about with folder lengths? It is as though the people who have created the synchronsiation functionality have not spoken with the people who have implemented the OneDrive file length limit.
Come on Microsoft - why not get this sorted once and for all? Fix it so that you can synchronise paths on your C: drive up to the 400 character limit.
Been dealing with Onedrive issues the past 6 months. This is the biggest issue.
yes you have allowed longer path names in the WEBVERSION. howabout when it syncs to a local machine like WINDOWS 10 where there is a limit of 256 characters in the filepathname.
No longpathtool will not solve this issue as we don't need to rename copy or move files. The underlying issue it is the year 2020 this issue needs to be resolved to allow longer file paths with synced to a windows 10 local installation.
This is incredible frustrating to explain to a customer no sorry this is a limitation of Microsoft that hasn't allowed any more than 256 characters in a filepathname. At least I can say it's not you or me it's Microsoft. So thank you for being the one to be able to blame when this issue can't be fixed.
we migrated all our data to sharepoint and now we have issues opening files as path is too long.
Please fix this issue urgently
This is one of the worst thing of onedrive.
Why the path length is limiting to 256.
All my users are complaining. Thinking of moving from one drive to a onprem NAS device where we don't face such issues
This is still an issue here, especially with COVID and more and more people needing to work remotely, to have the first 50 or so characters being the "share name" (what used to be something like S:\) causing quite a few issues with clients syncing SharePoint. (when the sync client actually works haha)
Would be great to have this on the 400+ character limit and maybe, just maybe all will be right with the world...
This is literally an outrage. Halfway through migrating our entire company to OneDrive and O365 architecture, and this? File path name limits? In 2020? EVERY SINGLE NESTED FOLDER WE HAVE IS TOO LONG.
Use LongPathTool it will solve your problem of deleting and copying long path files
Caitlin Boake commented
SharePoint files synced with OneDrive still experience "path too long" issues. Please address this
Gerald Brickson commented
Exactly, I came to face this issue also. Then some recommended me Long Path Tool software and I am grateful to that person
the same issue, it is not solved with newer version of onedrive, the file show up on sync folder but just couldn't open it, i have to rename it online to open it in sync folder. this is not what we expected.
is there a way to shorten the file path and still refer to the correct URL?
This is one of the stupidest thing of onedrive.
Why the path length is limiting to 256.
It just means, we cannot keep internal structures with meaningful names.
I just did an automation project. And now when i try to copy the project folder for sharing, this error happens. How am i going to rename all those project folders? Amazing..
Now i need to use my local folder.
Fred Davis commented
Use Long Path Tool, Long Path Tool can simplify and
probably end your problems in unlocking, managing and
renaming files that appear to have a long filename
Jason Robertson commented
Its still a Problem AWS Cloudberry is much better at this please lift your game. This is extremely annoying.
I cannot copy or clone the Microsoft SPFx library due to this file limit restriction - https://github.com/SharePoint/sp-dev-docs
I had to download and shorten the zip path of the file repository. There was still one file that could not be copied.
I really believe that it is essential to solve this somehow.
In the years of my degree, I had a path pattern like
In the meanwhile, I have been working around various companies, including two startups of mine.
I tried to explain that path isn't not only a technical matter. If it was, we all would have chosen iPad. A IT because of the mindset maybe can think the better pattern of paths or use tweaks, scripts and tools. For an accountant or lawyer it is essentials to understand optical/visually where is a file and sometimes he needs filenames like Client-Second-Answers-to-The-Authority-Ver2.docx
So 420 characters maybe it's enough for a tweet, perhaps the 420 is the favourite number of Snoop Doog, but it is not enough of an organizing system.
Not done at all, still get this error in Onedrive for Business on Windows 10.
Have you tried 'long path tool'?
it's very helpful for me.
Long Path Tool will let you easily delete, copy or rename long path files.
I have just returned from a support task. The customer wanted to switch over to OneDrive from Google's cloud backup that I set up months ago to avoid paying for two online accounts. Google's backups had run perfectly. OneDrive failed like a beta program when confronted with long paths - and it was not a user-friendly job getting OneDrive to include folders outside the default settings.
Microsoft - If a file and its path fit on the NTFS system you chose for Windows you should have designed your backup facility to cope with it. Even my customer - a bookkeeper, not an IT professional commented that the backup should continue and then present a list of files that failed - it shouldn't just stop.
And people wonder why I always criticise Microsoft.
Blane Kemp commented
Hey "BOOM! IT'S DONE" Jason -- where are you? Can you enlighten us on what we need to do to make it work? Is is supposed to work in OneDrive for Business on Windows 10?
Please come back to us...as you can see from the 1000+ comments, nobody is seeing the boom.