Microsoft suddenly disabled OneDrive support for non-NTFS disks this week, wreaking havoc for users with FAT32-based removable drives. But here’s the kicker: This should have never worked.
“Microsoft OneDrive wants to ensure users have the best possible sync experience on Windows, which is why OneDrive maintains the industry standard of support for NTFS,” a Microsoft statement explains. “Microsoft discovered a warning message that should have existed was missing when a user attempted to store their OneDrive folder on a non-NTFS filesystem—which was immediately remedied. Nothing has changed in terms of official support and all OneDrive folders will continue to need to be located on a drive with the NTFS filesystem.”
What’s not clear, of course, is when this support was supposed to have ended. And that users have been utilizing FAT32-based microSD cards and other removable storage with OneDrive for years. The problem impacts drives formatted with exFAT and ReFS as well, Neowin reports.
The issue is that Microsoft just suddenly pulled the switch without warning anyone. And for those who had been using this functionality, its sudden disappearance—the error message above is seen after a reboot—is most unwelcome.
Pbike908
<p>I see this as a potential issue for Mac folks more than Windows folks…</p>
fishnet37222
Premium Member<blockquote><a href="#136372"><em>In reply to Pbike908:</em></a></blockquote><p>The macOS version of OneDrive supports HFS+.</p>
rameshthanikodi
<blockquote><a href="#136374"><em>In reply to fishnet37222:</em></a></blockquote><p>yeah but the macOS version of OneDrive doesn't support placeholders. It's pretty much the existing OneDrive client that we have for Windows 10.</p>
SvenJ
Premium Member<blockquote><a href="#136400"><em>In reply to FalseAgent:</em></a> To be clear, the Windows version doesn't support files-on-demand, aka placeholders, either. The latest insider builds support placeholders. It isn't fully baked yet, and I expect that that functionality should make it to the MAC client in some way. The functionality is in Windows File Manager in preview. This 'change' to not supporting anything but NTFS is not an insider or placeholder thing. Production builds are subject to it.</blockquote><p><br></p>
suavegav
<p>"users have been utilizing FAT32-based microSD cards"</p><p><br></p><p>Seriously?</p><p><br></p><p>That's just nuts</p>
wunderbar
Premium Member<blockquote><a href="#136373"><em>In reply to suavegav:</em></a></blockquote><p><br></p><p>every MicroSDHC card that's 32GB or lower is formatted fat32 out of the box. You have to actively change it to something else. anything 64 and up is formatted exFAT out of the box, same thing, have to actively change it.</p>
hrlngrv
Premium Member<p><a href="#136378"><em>In reply to wunderbar:</em></a></p><blockquote>. . . have to actively change it.</blockquote><p>Granted, but how difficult and time consuming is it to fire up File Explorer, right click on the drive icon for a new and just inserted MicroSD or USB drive, choose format, and choose QuickFormat as NTFS? Took me longer to write this.</p><p>As long as MicroSD cards could be used in cameras or camcorders the firmware for which only understands FAT, seems reasonable to me that they always come preformatted as FAT32 or exFAT.</p>
wunderbar
Premium Member<blockquote><a href="#136424"><em>In reply to hrlngrv:</em></a></blockquote><p>I think the average person doesn't do that though. Your reply is firmly in the "all you have to do is…." camp. And if you have to tell someone "all you have to do is" it's probably not something they can do. I know If I tried to tell say, my mother, to do that she'd look at me like I have 2 heads.</p><p>For the average person reading this website, sure it's trivial. But for the average person, it isn't. Can't forget the wider audience.</p>
hrlngrv
Premium Member<p><a href="#136425"><em>In reply to wunderbar:</em></a></p><p>The question is how many camera/camcorder users use MicroSD cards? If substantial numbers, say, within an order of magnitude of PC users using those cards, <strong><em>and</em></strong> if camera/camcorder users couldn't reformat MicroSD cards and those devices' firmware could only handle FAT32 or exFAT, then from my perspective it's obvious and simple common sense that MicroSD cards would come formatted as FAT32 or exFAT. MicroSD card manufacturers would be accommodating their customers who just couldn't use their products if initially formatted as NTFS.</p><p>Perhaps it'd be good for all camera and camcorder manufacturers to support NTFS <strong><em>if</em></strong> MSFT didn't charge any royalties for doing so, and <strong><em>over time</em></strong> those devices would mostly be able to handle NTFS. But today, I figure the vast majority of cameras and camcorders can't handle NTFS, so MicroSD card makers would be insane to preformat them as NTFS.</p><p>I believe it's you who's failing to understand just how wide the customer base for MicroSD cards may be.</p>
SvenJ
Premium Member<blockquote><a href="#136424"><em>In reply to hrlngrv:</em></a> Not a problem to change it at the beginning, if you know you should and ignore the SD Card Consortium recommendation to format your 128G card exFat (a MS format). Actually that is for anything over 32GB. Go buy a 256GB SD and try to format it NTFS. Windows won't do it. So, you have folks that have had OneDrive syncing on a 128G/256G SD cards forever that wake up and find, nope we aren't doing that anymore, deal with it. You don't have an option other than to re-setup your OneDrive. If it's 256 BTW, you are screwed, they don't support it.</blockquote><p><br></p>
SDreamer
<p>This is annoying for me because I had it all synced up on an exfat drive on bootcamp so I wouldn't have to duplicate my OneDrive…. if I didn't have subscription, I would just go somewhere else.</p>
wunderbar
Premium Member<p>this is irresponsible, shortsighted, etc.</p><p><br></p><p>If it was never supposed to work, I get why they'd want to fix that, but to just pull the pin with zero warning to users is unacceptable.</p><p><br></p><p>This company……</p>
Skolvikings
<blockquote><a href="#136377"><em>In reply to wunderbar:</em></a></blockquote><p>^ this</p>
JacobTheDev
Premium Member<blockquote><a href="#136377"><em>In reply to wunderbar:</em></a></blockquote><p>I agree. For users who already have this set up, at the very least, there should be a workaround. Something like a registry key entry so that if you really know what you're doing and are aware of the risks you can get still do it.</p>
GarethB
Premium Member<blockquote><a href="#136377"><em>In reply to wunderbar:</em></a></blockquote><p>Just another reason to not go back to OneDrive….</p>
jimchamplin
Premium Member<blockquote><em><a href="#136377">In reply to wunderbar:</a></em></blockquote><p>The insanely stupid part is that if it was "never supposed to work," why did it work flawlessly the whole time?</p>
hrlngrv
Premium Member<p><a href="#136492"><em>In reply to jimchamplin:</em></a></p><p>Probably because it saved no NTFS-specific metadata for files on *FAT* drives, so wouldn't need to sync any.</p>
lwetzel
Premium Member<blockquote><a href="#136492"><em>In reply to jimchamplin:</em></a></blockquote><p>It may be that something is in the works that will upset this apple cart and then people would complain that MS broke the system. Maybe?</p>
dstrauss
<blockquote><a href="#136377"><em>In reply to wunderbar:</em></a> Microsoft is getting to be like the old joke of pulling the pin and handing the guy the grenade, then tossing the pin. THAT'S what you get with Windows anymore…</blockquote><p><br></p>
Narg
<blockquote><a href="#136377"><em>In reply to wunderbar:</em></a></blockquote><p>Can you explain why? Other than to just b*tch? Reformat, redownload. Fixed. You are making a mountain out of… NOTHING. Your data is safe. No big deal.</p>
Skolvikings
<blockquote><a href="#138649"><em>In reply to Narg:</em></a></blockquote><p>It's not always that trivial to reformat and redownload. For example, what if the drive in question was also the OS drive? Or had data besides the OneDrive data?</p>
hrlngrv
Premium Member<p><a href="#142000"><em>In reply to Skolvikings:</em></a></p><p>Anyone using FAT32 or exFAT for Windows 7 and more recent deserves the headaches that brings. There is no account-level security with FAT file systems. The entire %SYSTEMDRIVE% would be open to any & every exploit imaginable.</p><p>As for data in addition to OneDrive data, someone above mentioned <strong>convert.exe</strong>.</p>
BigM72
<p>In the consumer space, Microsoft just can't be trusted. It seems to be in their DNA to burn users in so many ways, Windows Phone, placeholders, My People, the list goes on. </p>
Waethorn
<p>I bet this has something to do with Windows Azure. Are they moving OneDrive to Azure? Azure Backup only supports backing up files that are stored on an NTFS volume, and that really sucks if you're trying to use Azure Backup to back up a Storage Space formatted with ReFS, which is what Microsoft's recommendation is to use when setting up a file server.</p>
LocalPCGuy
<blockquote><a href="#136387"><em>In reply to Waethorn:</em></a></blockquote><p>I believe you are correct. Too bad Microsoft forgot to tell everyone a long time ago.</p>
Waethorn
<blockquote><a href="#136406"><em>In reply to LocalPCGuy:</em></a></blockquote><p>They only thing they told people is that ReFS wasn't meant to be a replacement for NTFS. The writing was on the wall though: they never had any intention of following through on ReFS. It's very likely we'll be using a license-free FS built for Linux in a few years time anyway.</p>
Waethorn
<p>Let's see:</p><p><br></p><p>ReFS is dead.</p><p><br></p><p>NT is dead.</p><p><br></p><p>This week is a good one for Microsoft predictions. Can we make it a hat trick?</p>
navarac
<p>How about Microsoft is dying?</p>
Waethorn
<blockquote><a href="#136501"><em>In reply to navarac:</em></a></blockquote><p>Cutting thousands of jobs means that Office and Azure money gets split among fewer employees, meaning the executive board will get nice fat bonuses.</p>
skane2600
<p>I stopped most of my use of OneDrive because of it's inability to properly handle Office files. It constantly believes there's a syncing issue between local and server when the document hasn't be changed anywhere. Now I only use OneDrive to view photos automatically uploaded from my Windows Phone.</p>
Darmok N Jalad
<blockquote><a href="#136389"><em>In reply to skane2600:</em></a></blockquote><p>Would this also be true of OneDrive for Business? Cause, oh my, I have persistent crashing of Office applications and nothing fixes it. What is worse is when the application recovers my file, it can't save as the original file name because it is still in use. IT has gone round and round and says OneDrive isn't the problem, but I get crashes almost everyday, several times a day, often when I'm not even interacting with the file. Could Autosave and OneDrive be doing it?</p>
robinwilson16
<blockquote><a href="#136416"><em>In reply to Darmok N Jalad:</em></a></blockquote><p>Around the time placeholder support was removed I found OneDrive basically became incompatible with Office 2013 whether it was the standard or business one and you could save a new file to OneDrive then when you pressed save a second time it would tell you the file was in use by someone else, that it was modified on the server and pc and I was asked which version I wanted to keep or it was read only and Office would freeze and crash (I think disabling the Office Document Cache helped as it was like both OneDrive and this were competing for the file to upload it). It was so bad and Microsoft couldn't help so I switched to DropBox after losing work on multiple occasions and everything has worked very reliably since then and syncing is faster.</p><p>I have just switched back to OneDrive again (as would rather not have to pay for both!) and the new sync client with files on demand and Office 2016 seems better although I have already had it create duplicate files (where one has the computer name on the end) so time will tell!</p><p><br></p><p>Robin</p>
navarac
<p>I stayed with Dropbox. Microsoft "retires" too much without warning.</p>
TrevorL
Premium Member<p>I always believed it was NTFS only. Never even thought of putting it on anything else.</p>
ndwilder
<p>Cloud First, Users Last. </p>
waverunning.geek
<p>First there was the Unlimited Storage fiasco which was basically a bait-n-switch scam to sell more Office 365 subscriptions. </p><p><br></p><p> Then when my PC started up today, I was greeted with this BS.</p><p><br></p><p>Like others here, I utilize Storage Spaces and REFS because I care about my data integrity. Why the hell would Microsoft stop supporting their next generation file system, which has much better data integrity than the ancient NTFS, for a product whose main function is data backup?</p><p><br></p><p> And why would they do this without warning anyone?</p><p><br></p><p>I called Microsoft today to cancel all of my subscriptions. Google Drive will be offering a similar sync service soon. $10/mo for unlimited storage if you have your own domain. Say what you want about Google, but at least they do not pull this BS on paying customers.</p>
Darmok N Jalad
<blockquote><a href="#136401"><em>In reply to waverunning.geek:</em></a></blockquote><p>Yeah, the OneDrive tier changes prompted my change. I don't even find OneDrive to be that reliable with syncing, so once MS dropped the tiers to where I had to pay, I took my money elsewhere for better results. In other words, free is a good price for OneDrive. </p>
Lauren Glenn
<blockquote><a href="#136401"><em>In reply to waverunning.geek:</em></a></blockquote><p>Right. I stopped using Google Drive after it couldn't reliably sync files between my desktop PC and my other PCs. Google's solution was to uninstall and reinstall Google Drive to get it to sync. Meanwhile, I lost many files in the process and never used it again. OneDrive isn't much better as I remember the old placeholders with Windows 8 caused many files to just randomly reappear after being deleted and it created a HUGE sync disaster with things being duplicated with different versions. That's why I'll only use Dropbox but keep OneDrive to keep my video files on there since they brought placeholders back with Windows 10 but seemed to have done it right this time.</p>
Winner
<p>Oh Microsoft, you try so hard to be progressive and customer-centric but your actual DNA keeps you acting like this.</p><p><br></p><p>From a Slashdot commenter "<span style="color: rgb(0, 0, 0);">Usually they declare a bug to be a feature so they don't have to fix it. This time they called a feature a bug & fixed it right away. Round and round we go!"</span></p>
Darmok N Jalad
<p>I ran into this problem on Windows 8.1 RT on my Surface 2, where I used my SD card for document storage and OneDrive (with placeholders!). NTFS was required then, so who knows when that switch accidentally got flipped. Problem then though was Windows failing to mount the card on resume, resulting in a file system mess until I rebooted. </p>
hrlngrv
Premium Member<p>Picky: it's possible to format removable drives as NTFS. One of the first things I do with new MicroSDs and USB drives. Heck, possible to put multiple partitions on them, say 1GB FAT32 and the rest NTFS.</p>
wunderbar
Premium Member<blockquote><a href="#136419"><em>In reply to hrlngrv:</em></a></blockquote><p>Sure it's possible, but not for the average user, and the point remains you shouldn't have to.</p>
hrlngrv
Premium Member<p><a href="#136426"><em>In reply to wunderbar:</em></a></p><p>Debatable for MicroSD cards, though perhaps not for USB drives.</p><p>If a substantial number of MicroSD cards are used in cameras and camcorders, those devices have no means of formatting those cards, and those machine's firmware only handled FAT32 and exFAT, then FAT32 and exFAT are most usable formats since it's relatively easy for PC users to reformat those cards as NTFS.</p>
unfalln
<blockquote><a href="#136435"><em>In reply to hrlngrv:</em></a></blockquote><p>While I can see some perverse benefit to hotswapping a MicroSD card from a camera and having it upload to OneDrive when returned to the PC, I doubt that's really a good way of doing it.</p>
hrlngrv
Premium Member<p><a href="#136519"><em>In reply to unfalln:</em></a></p><p>Geez this is apparently a difficult concept!</p><p>Not hot swapping. The point is PREFORMATTING, that is, how the MicroSD card's MANUFACTURER formats these cards in their own factories. If these cards could be used in devices other than PCs, and most of those other devices only support FAT32 and exFAT, and PCs also support those file systems along with others, then wouldn't FAT32 or exFAT be the most usable format OUT OF THE BOX?</p>
Narg
<blockquote><a href="#136426"><em>In reply to wunderbar:</em></a></blockquote><p>So…. You're average? Sorry.</p>
hrlngrv
Premium Member<p>Lemme guess: OneDrive also stores NTFS file metadata, permissions, maybe ACLs. If so, fine. That'd mean files uploaded from local NTFS drives to OneDrive couldn't subsequently be synced with drives which couldn't accommodate the metadata. However, files uploaded from local FAT32 or exFAT drives would have only FAT file attribute bits as metadata. It should be possible to sync them with any drive using a file system Windows understands.</p><p>Looks like there were 2 ways MSFT could go when they discovered this, and true to form MSFT opted for the more user-hostile route.</p><p>Has MSFT ever been a customer-focused company? Or is the extent of their customer focus summarized by BOHICA?</p>
SvenJ
Premium Member<p>Fat32 my ass. This affects exFat, the MS proprietary, and SD card committee recommended format for SD cards over 32GB. If you stick an SD card in a Surface/Windows Phone and say format, it defaults to exFat, a format now all of a sudden not supported by OneDrive. I have a couple of devices that I've jumped through hoops to move the files, redirect OneDrive, reformat and move back and redirect. These were 128G SDs. I haven't found a Windows device that will format a 256G SD in anything other than exFAT yet.</p><p>We have a thread going on Answers, MSs preferred support format (user supported) on this. It is freakin'' ridiculous that exFat isn't supported. It's their format, specifically indicated for high capacity SD cards, which are likely to be installed in the anemically provisioned Windows mobile/portable devices. Guess OneDrive is only intended for desktop machines with Terabyte drives formatted NTFS, a file system that dates back to NT.</p><p>I'd post a link to the Answers thread, but it seems to be <span style="color: rgb(0, 0, 0); background-color: transparent;">inaccessible at the moment, or maybe forever, if you are a conspiracy theorist.</span></p>
hrlngrv
Premium Member<p><a href="#136445"><em>In reply to SvenJ:</em></a></p><blockquote>. . . Guess OneDrive is only intended for desktop machines with Terabyte drives formatted NTFS . . .</blockquote><p>Not cynical enough. OneDrive could be intended to get mobile device users to buy higher capacity SSDs formatted NTFS.</p><p>Thing is NTFS stores more file-level metadata than any FAT-based file system. NTFS has ownership, create/access/modify times, file permissions beyond FAT file attributes, ACLs, and more. If files with such metadata were stored on OneDrive, could they and their metadata be synced to non-NTFS drives?</p><p>From this perspective, it doesn't matter than exFAT is a MSFT proprietary file system. After all, MSFT is also throwing ReFS users under the bus too.</p><p>This is MSFT being MSFT: Our customers are our OEMs; their customers are irrelevant to MSFT.</p>
Lauren Glenn
<blockquote><a href="#136445"><em>In reply to SvenJ:</em></a></blockquote><p>Doesn't this have to do with the tagging that NTFS does to files? I know that if you kept getting a message regarding ownership or something like that on files (and this affected iTunes when syncing music manually to an iPad/iPod), the only way to get rid of that error was to move the files to exFAT or FAT32 drive to remove those tags and then back again. Those tags always were on the files that were placed in a OneDrive or Dropbox folder on my computer.</p><p><br></p><p>Also keep in mind that NTFS has had some revisions over the years. Didn't it also take Apple a long time to get rid of HPFS?</p>
quick_razor360
<blockquote><a href="#136445"><em>In reply to SvenJ:</em></a></blockquote><blockquote><em>So using DISKPART in an elevated command prompt wont let you format a 256GB SD card to NTFS?</em></blockquote><p><br></p>
SvenJ
Premium Member<blockquote><a href="#136946"><em>In reply to quick_razor360:</em></a> Didn't for me. I imagine there may be SD with different controllers in them that might, but they are still expensive enough I haven't bought a dozen to experiment 😉 I even tried to create a 128G partition on the 256 card and format it to NTFS, just for fun, and that wouldn't work. Just failed. Trying to format the card NTFS using various methods even got the card to the point Windows wouldn't recognize the card anymore. The formatting process just quit, and you couldn't cancel, just pull the card. The system then said there was nothing in the drive, disk manager saw no available space. At that point I stuck the 256G card in a $39 Windows GoPhone (Lumia 635). It said, I see an SD but don't understand the file system, would you like to format it. I said yes and in seconds had a working SD, formatted exFat. You don't get a choice in the phone. Surface and Dell desktop were happy with the card again, but of course, OneDrive wasn't. </blockquote><p><br></p>
Spineless
<p>Anyone who is using a removable device for their OneDrive sync location, and not using NTFS and BitLocker is making a huge mistake. I am personally glad that MS made this change, because it is a pragmatic change. Yes, they could have provided better messaging, but if nothing else, it will get people to think more about their data security.</p>
SvenJ
Premium Member<blockquote><a href="#136450"><em>In reply to Spineless:</em></a> You may believe that, but I have a personal device with 64G of internal RAM. Some have devices with 32GB internal. I have a 128G SD card that stays in it permanently and it is by default, and recommendation, formatted exFAT. I could give a crap about BitLocker. I have OneDrive redirected to that 128G drive because that makes sense in this situation, and it has been fine for some time. A long time. All of a sudden, with no warning whatsoever, and no grace period, that is no longer OK. exFat is a MS format. MS will not format a 256G drive in anything other than exFAT. MS has just told us, if you have a mobile device with limited internal RAM, you need to be very careful about OneDrive syncing on your internal drive, or limit yourself to 128G on external storage. </blockquote><blockquote>MS needs to allow OneDrive on exFAT, and support BitLocker on exFAT, for thse that need it. or just surrender mobile, including Surface.</blockquote><p><br></p>
jpaterson84
<blockquote><a href="#136453"><em>In reply to SvenJ:</em></a><em>You mean internal STORAGE not RAM right?</em></blockquote><p><br></p>
SvenJ
Premium Member<blockquote><a href="#139115"><em>In reply to jpaterson84:</em></a> Yea, storage. Storage is largely random access memory in mobile devices these days, so I think of it that way. </blockquote><p><br></p>
matsan
Premium Member<p>Ahhh – the joy of having updates rammed down your throat when you at least expect them. </p>
jimchamplin
Premium Member<p>Wait wait… If it was "never supposed to work" but had worked perfectly the whole time…</p><p><br></p><p>… WHY DIDN'T THEY JUST REMOVE THE ARBITRARY REQUIREMENT INSTEAD OF SCREWING USERS!?</p>
hrlngrv
Premium Member<p><a href="#136491"><em>In reply to jimchamplin:</em></a></p><p>Because MSFT.</p>
matsan
Premium Member<blockquote><a href="#136491"><em>In reply to jimchamplin:</em></a></blockquote><p>"Yes, we can"</p>
Narg
<blockquote><a href="#136495"><em>In reply to matsan:</em></a></blockquote><p>Yes you can reformat and redownload. Grow a pair and get over it.</p>
hrlngrv
Premium Member<p><a href="#138652"><em>In reply to Narg:</em></a></p><p>Struck out at the singles' bar tonight?</p><p>Wee overreaction to obvious sarcastic flippancy.</p>
navarac
<p>I went to Dropbox 2 years ago and cannot say I'm interested in OneDrive anymore. I'm getting to have no confidence in Microsoft supporting anything that is not "of the moment".</p>
ErichK
Premium Member<p>I don't think this is going to affect me personally, but if it did I think I'd be pretty PO'ed.</p>
rh24
<p>Obligatory Office Space reference…. They just *fixed the glitch*…</p>
Delmont
<p>Oh please… enough with the drama. Who is using SD Cards and USB thumb drives as critical mission anything? Even for a camera use… it's July 2017. You want FAT, go back to WinXP.</p>
DWAnderson
<blockquote><a href="#136543"><em>In reply to Delmont:</em></a></blockquote><p>That argument doesn't work for the dropped support for ReFS.</p>
JudaZuk
<blockquote><a href="#136899"><em>In reply to DWAnderson:</em></a></blockquote><p><br></p><p>Well when it comes to ReFS, the argument should be..don't use ReFS if you don't know what it is and what it is for .</p><p>If you know the purpose of ReFS and where to use it, you soon realise OneDrive not supporting it, is a non issue</p>
jwpear
Premium Member<blockquote><a href="#136543"><em>In reply to Delmont:</em></a></blockquote><p>Remember those cheap Windows tablets with 16 or 32 GB internal storage? I've used an SD card to expand storage on one I have (the poor Acer Iconia W3 MS distributed at Build in 2012). I put my OneDrive on it to save space on the internal drive. I did reformat mine with NTFS, but I'm sure lots of folks don't.</p>
CompUser
<p>I've always said, anyone who stores their data on someone else's server, and gives control of that data to the company running those servers, is an idiot. Thanks, Microsoft for proving me right.</p>
SvenJ
Premium Member<p><a href="#136544"><em>In reply to CompUser:</em></a> Nothing happened to my data. MS doesn't control it. The way I interact with it has changed. Nothing lost, nothing in danger of being lost. I still have a number of ways to interact with it. The issue is only that they made a significant change in where/how my local sync'd copy is handled. They did it with no warning, and it has some ramifications for those of us who have a need for larger external storage.</p><p>I have a largish SD card in a couple of devices, not for OneDrive specifically, but for other off-line file requirements. That makes it a logical place to put my OneDrive sync folder. I am now limited by NTFS for the size of that external drive. With the Files-on-Demand that is coming (and I have on a couple of insider devices) it does allow me to re-evaluate my sync requirements, and potentially just 'sync' less and keep OneDrive on the OS/internal storage. That lets me use exFAT on the SD as recommended/required.</p><p>So, this is exceptionally annoying, in the short <span style="color: rgb(0, 0, 0); background-color: transparent;">term, but not a showstopper, for me anyway. </span></p>
TechnologyTemperance
<blockquote><a href="#136544"><em>In reply to CompUser:</em></a></blockquote><p>You forgot to add a disclaimer in your post that you are a large shareholder in Reynolds group holdings</p>
Bill Russell
<blockquote><a href="#136544"><em>In reply to CompUser:</em></a></blockquote><p>As with the futile argument of what type of device is 'best', it sort of depends on the type of data and how it is used. Business? Personal? For my irreplaceable data – family photos/videos and other data of my creation, I would have lost all of this years ago if I didn't keep stuff backed up on – in my case Google drive/photos. I tried my own NAS at home for a while, but unless you are willing to devote a significant amount of time, expense and effort – and even then for most people inevitablly lose control of such a server over the course of a few years as I did. A top reputable company's cloud storage service has a far, far better chance of keeping this stuff safe for decades than I will. It may be more arguable for a business to have on premises storage for business data or not, with paid IT personnel in charge of it.</p>
creugea7
<p>It also currently does not support APFS. The new file system in MacOS High Sierra. It would be nice if they could just make it file system independent. </p>
SvenJ
Premium Member<p>I really hate the inability to comment on "Premium Comments." when the segregation started, I could at least click reply on a Premium Comment and it would throw me over to 'coach' to post.</p><p>In any case, </p><p>@Delmont, This affects more than FAT, it affects exFAT and apparently Apple's new file system as well. NTFS isn't actually a modern file system either, and isn't supported on some modern storage media. MS doesn't support NTFS on some modern storage media.</p><p> @cruegea7, If in fact this affects APFS, that is significant. My understanding is that file system will be transitioned to all MACs. This would mean OneDrive is not supported on Apple without a secondary drive, formatted NTFS. Thanks MS for helping out DropBox and iDrive.</p>
djncanada
Premium Member<p>Quick question, can OneDrive files provided external drive is formatted to NTFS, work?</p><p><br></p><p>As vendors sell more devices like Yoga Book that has 64GB (24 GB usable), some may need ability to have OneDrive files local</p>
Narg
<blockquote><a href="#136961"><em>In reply to djncanada:</em></a></blockquote><p>Yes. Non-issue. Move along…</p>
Mark from CO
Premium Member<p>Paul:</p><p>This is how to make satisfied customers and create positive word of mouth. Microsoft is so good at it.</p><p>Mark from CO</p>
LeFrenchFab
<p>Next stop, Mac file systems (HFS & APFS)?</p>
edboyhan
<p>This one caught me. After a reboot — took me a few retries before I realized they were serious 🙁 . Anyhow, I was using an external USB SSD drive for OneDrive. I reformatted it, and reinitialized OneDrive, and all is well. Most annoying thing (beyond the out of the blue nature of this) was the repeated requirement to relogin to my MSA account with the whole two factor authorization messages to my phone.</p><p><br></p><p>I wish MS had more of Amazon's customer focused ethos ( also wish these two Seattle area behemoths would cooperate more).</p>
Narg
<p>Why does this matter??? The data is safe in the cloud, just reformat and download again. NO PROBLEM!!! Gees.</p>
ErichK
Premium Member<blockquote><a href="#138648"><em>In reply to Narg:</em></a></blockquote><p>Good point I suppose. I knee-jerk reacted to this story, but now it looks like this is more of an inconvenience rather than an all-out tragedy. Like you said, it's not like the data is permanently deleted.</p>
hrlngrv
Premium Member<p><a href="#138648"><em>In reply to Narg:</em></a></p><p>Not high cost, but not cost-free. You're dismissing the time spent/inconvenience of needing to reformat and download sync.</p>
JudaZuk
<blockquote><a href="#138648"><em>In reply to Narg:</em></a></blockquote><p><br></p><p>You don't even need to reformat, just convert the FAT32 volume to NTFS</p>
jlmerrill
<p>Does this mean I cannot install onedrive on a mac?</p>
SvenJ
Premium Member<blockquote><a href="#138667"><em>In reply to jlmerrill:</em></a><em> </em>Right now you can. Haven't heard that any current Mac users have an issue. Not sure how this will work with future OneDrive client releases for the MAC, or the impending switch to AFS with the next major MACOS release. </blockquote><p><br></p>
SvenJ
Premium Member<p>@narg, not necessarily that simple. OneDrive isn't the only thing on the SD. Can't just reformat and redownload, have to move those other files. Can't put them on the boot drive, too small. That's why there's is an SD. Need to come up with a large thumb drive and an OTG dongle, or spend hours and capped data a$$et$ to upload to a cloud $ervice. Now I can reformat. Oops, no. It's a 256G SD and Windows won't reformat that as NTFS, only exFat. Need to find a 128G card. Do I have one laying around, or do I needed to buy one? Amazon and two days, or Best Buy today at twice the price (for something I shouldn't need to buy.) OK. 128G card is in and formatted. Copy files back from thumb drive or cloud $ervice (eating more data allotment) taking more time. Oh wait, not enough room. Card is half as big now. Not really enough room to put OneDrive back.</p><p>So you spend a day, spend money, and don't even wind up with a capability that worked fine the last time you booted up. No warning, no other choice, no problem? No concept of any other situation but your own. </p>
jwpear
Premium Member<p>I don't understand the non-support for ReFS. Makes me question using ReFS at all.</p>
JudaZuk
<blockquote><a href="#139565"><em>In reply to jwpear:</em></a></blockquote><p>You shouldn't be using ReFS unless on a server, and if it is on a server you should not use OneDrive as a backup solution </p><p><br></p><p><span style="background-color: rgb(255, 255, 255);">ReFS is intended for Storage Spaces , and even if it has some advantages it also have several limitations, for instance you can not boot Windows of a ReFS formatted drive, and you can not install Windows Store apps to it either, it is not intended to be used on a standard Desktop computer</span></p><p><br></p><p><span style="background-color: rgb(255, 255, 255);">ReFS is not a replacement for NTFS and it was never intended to be either.</span></p>
jwpear
Premium Member<blockquote><a href="#140886"><em>In reply to JudaZuk:</em></a></blockquote><p>Using it exactly as you describe–on servers. Although, I could see using it on desktop to create a JBOD storage. Agree that it probably shouldn't be used with OneDrive. Without MS elaborating, it isn't clear if the non-support is due to limitations of ReFS or if this is a sign ReFS will be sunset. I half expected ReFS to eventually replace NTFS.</p>
gdt841
<p>I have an HP two-in-one with just 32GB of storage (plus a 1TB drive in the keyboard).</p><p>I added a 64GB SD card and have always had problems with it; it was formatted as Ex-FAT and used exclusively for OneDrive.</p><p>As it was consistently unreliable, I contacted HP and they <strong>replaced the motherboard</strong> under warranty. The SD card was subsequently no better, but by then the warranty had run out.</p><p>I have reformatted it as NTFS and re-synced the OneDrive contents. It is a bit early to be sure, but it appears to be reliable now, and hasn't given any errors at all.</p><p>If even HP didn't know about this farce, what hope have the rest of us got?</p>
JeremyJukes
<p>This file support change also makes system image backup fail in preview releases since the EFI partition is a FAT32 partition. Manufacturers created this partition when manufacturing the PC and it is used to boot the OS. When you convert this partition to NTFS, the backup works but boot fails. Many millions of PCs will not be able to be booted when this release of the OS goes into production in the fall.</p>
SvenJ
Premium Member<p><a href="#140617"><em>In reply to JeremyJukes:</em></a> Not sure what that has to do with the OneDrive situation. Maybe I'm missing something. The drive you use to sync OneDrive must be NTFS. Unless you are wanting to put OneDrive on that OEM partition, which you shouldn't, leave it alone. Your whole internal drive doesn't need to be NTFS, so the various other partitions can just stay as they are. I don't have issues with large internal drives, SSD, or traditional, making them NTFS. It's just SD cards that are an issue, and only big ones, >128G. For small portable tablets and 2-1s, that SD card winds up being your secondary drive, and this limits the size you can use, if you are going to put OneDrive on it.</p>
JudaZuk
<p>I don't get the problem.. it is not like Windows 10 stopped supporting NTFS, it is just OneDrive.. </p><p><br></p><p>So you have a folder that no longer can sync , because the folder it is on a volume formatted in FAT32 …</p><p><br></p><p>1) move the folders to another drive formatted in NTFS, change so OneDrive syncs from the new location .</p><p>or</p><p>2) Considering converting the FAT32 volume to NTFS</p><p><br></p><p>( In an elevated command-prompt type convert <drive letter>: /fs:ntfs )</p><p><br></p><p>Have a cup of coffee, done.. </p><p><br></p>