File name restrictions
The file name restrictions are still in place. There shouldn't be any special character, symbol, space before or after file. It is very disappointing especially when you are uploading hundreds of GBs and with 460 file name errors. That makes you stop the whole process. Please allow any type of file names like dropbox/google drive etc.
I have the same very disappointing issue -- file name restrictions are one thing, but it is totally unacceptable that other files are not synced, i.e., the process stops until you fix the conflicts. Even if you fixed the file name restrictions, you have to restart OneDrive.
Please see how Dropbox works...
I use "#" and "&" in my file names and OneDrive is always changing my filesnames. I wish it would stop and Microsoft would simply use the filenames that I give my files.... That would be so wonderful.
Please can this be changed for Mac. It makes One-Drive very un-user friendly if you have to constantly change file names in order to store your files on the system. It's almost unworkable. I've just uploaded a number of files holding receipts and I have 75 file names I need to amend. It is very frustrating!
These restrictions come straight out of a substandard command line parsing algorithm in DOS from 40 years ago. Because of this, special characters and device names cannot be used in file names. Please note that UNIX, which is >10 years older than DOS, and the Mac, have never had any problem with special characters. Microsoft needs to fix this 40 year old abomination and not carry over silly limitations to 21st century products.
Yes yes yes.
It seems to go without saying that a backup service for Mac should accept Mac file names. The OneDrive naming requirements go back to the 1980's MS DOS. It's time to enter the 21st Century. We're already 19 years into it.
Not accepting Mac file names makes OneDrive incompatible with Mac. People are not going to take the time to change perhaps hundreds of file and folder names. OneDrive never should have been offered to Mac users until it was made compatible with Mac.
The fact that MS requires user comments to change a mistake that never should have happened in the first place is making a second major mistake. MS should not require users to do their work for them. Accepting Mac file names on a mac backup service is an obvious requirement.
Same issue here.
Thought I was being smart signing up for Office365, thinking I could cancel google drive and transfer all my files to OneDrive.
Now with hundreds of filename errors that is forcing me to go back to google and cancel my Office subscription.
Looking at a google search of this problem, it seems it has been known for years - little hope of it getting fixed anytime soon.
Why Microsoft. why? Every time I give you a chance, you break my heart
Really disappointed and frustrated when syncing files from Mac, always prompt the file name errors.. Hope Microsoft can do something on this, otherwise we have to change the cloud storage solution to other provider.
Roy Leban commented
DropBox never complains that the name of a file contains a special character — it just makes it work. I'm trying to move from DropBox to OneDrive and I'm told I have to rename 165 files?!
Matthew Slyman commented
I would "second" the request by "Anonymous": filename restrictions in 2018? Seriously? All I did was copy some emails to my filesystem from Outlook, attempt to synchronise them, and I get this road-block! Also disappointed that Windows File Explorer can't search paths/filenames containing Unicode chars.
[Deleted User] commented
Do yourself a favor and switch to real and secure cloud service, like ********.