Feedback by UserVoice

I suggest you ...

Allow files that have special characters in the name to be uploaded

This makes it hard to convert users in our company.

1,314 votes
Sign in
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Password icon
Signed in as (Sign out)
  • Ken commented  ·   ·  Flag as inappropriate

    My company just have moved email server from local to MS could (Office365 & Onedrive business), but I am very unhappy with Onedrive business which can not sync my file with special characters. Onedrive stop immediately sync if found any file name with special characters. So fix this please. One more thing, I can sync all my files with special characters on Dropbox without any issues.

  • Jared Pickerell - Troy USD 429 commented  ·   ·  Flag as inappropriate

    @Jason Moore, any updates on the status of this? It is still causing problems when using the latest Next Gen Sync Client on Windows and OneDrive for Business (first release tenant).

  • LarryMcJ commented  ·   ·  Flag as inappropriate

    That's nice for business users, but what about OneDrive Personal. I think the limitation on allowing "all" other special characters and symbols that other cloud services allow, hurts your business. For example, I am seriously considering to not renew our Office 365 subscription. Having the larger OneDrive available with it is a selling point, but I've had to revert back to Dropbox, which sync all these special characters. Justification for many, like "|" is because they're invariably part of URL names when you copy them to save as .webloc files.

  • Anon commented  ·   ·  Flag as inappropriate

    Really need to be able to sync files including # symbol... come on this is basic! I have 1600 database files to backup that comprise 1.2GB of data. Because there are 10 files that include a # symbol (that total in space to less than 2MB) I am unable to use the OneDrive I pay for as a solution for my needs. That is ridiculous.

  • George commented  ·   ·  Flag as inappropriate

    1. You cannot limit the size of the copy.
    2. You cannot limit the amount of files for the copy.

    Attempted to copy indicated to large, selected less than 100 megabytes of data with 8 files indicated dont select so many files.

    Are you kiidding me! You guys need to stop being a joke. Get true and real. file management capabilities active, full trees full commands between OD, ODfB and Sharepoint in a fashion that EVERYONE expects and yes this includes folders, subfolders and files regardless of quantity or size.

    So ridiculous

  • Anmar Mansur commented  ·   ·  Flag as inappropriate

    I have a bunch of Visual C# projects that won't sync because they all contain folders named Visual C#. It's funny how the two are Microsoft products! No, it's not funny, but it's a joke nonetheless.

  • Eric Garza commented  ·   ·  Flag as inappropriate

    This is getting old. Any progress? I am getting tired of discovering the sync is broken due to this problem.

  • Derek commented  ·   ·  Flag as inappropriate

    Yep, I just hit this today too and I'm shocked. Worse still, because of they way the error message is worded, I raised a stink through my company's IT department thinking that this was due to my "organizaiton's policies".

    Somebody grab the OneDrive product owner and tell them to move this to the top of the backlog!!

  • Anyn commented  ·   ·  Flag as inappropriate

    At the very least, continue to upload files that don't have invalid characters. Why does the whole program shut down for only 1 file?

  • Anonymous commented  ·   ·  Flag as inappropriate

    Still working on it? An update would be great after almost 6 months. Your own software uses # and % for naming files in visual studio and yet you see it to be an issue for onedrive? Excuses are getting old, actions speak louder than words.

  • Gerry commented  ·   ·  Flag as inappropriate

    It looks like this was a problem in Aug.2014 and still in Sep. 2016. It is now Feb. 2017 and they still don't upload. How long do we have to wait, another three years? We have a business to run not a hobby. This is very much of a problem when you have hundreds of files with % and # that no other program has a problem with. It should be a very simple coding fix to allow a few symbols.

  • pkirill commented  ·   ·  Flag as inappropriate

    We should get a partial refund on our O365 E3 licensing. Between the extremely long "OneDrive - <your super long tenant name here>" folder, the confusing OneDrive / OneDrive for Business installation and setup, and the invalid characters issue, OneDrive for Business is essentially useless. Since Microsoft has integrated is so tightly with the other O365 products, they are all to some extent crippled as well.

OneDrive Archive: OneDrive for Business

Feedback and Knowledge Base