Misc Is exFAT still problematic?

  • Thread starter Thread starter falcorr
  • Start date Start date
  • Views Views 14,469
  • Replies Replies 49
It is and always will be problematic as it's not a proper exfat driver from M$
 
Sadly as far as I know, it haven't been updated by Nintendo. So yes, the exfat driver is still bad.
 
But who has actually encountered a problem? I use exfat and have done always. My friends all use exfat. Not a single one of us has ever had any problems, whatsoever.
I won't cliam to know much about the topic, so my question is genuine. I always hear people say exfat is a really bad idea, but at the same time I don't think I've heard of anyone actually having problems with it.
 
But who has actually encountered a problem? I use exfat and have done always. My friends all use exfat. Not a single one of us has ever had any problems, whatsoever.
I won't cliam to know much about the topic, so my question is genuine. I always hear people say exfat is a really bad idea, but at the same time I don't think I've heard of anyone actually having problems with it.
For one atmosphere does not support it as it causes problems
 
For one atmosphere does not support it as it causes problems
This is the sort of thing I'd like to have explained a bit deeper. People always just type this sort of thing. I've used Atmosphere since RCM became a thing. What problems does it cause?
 
It is best to let the sysnand or emunand have exfat driver as usual. and don't affect you using a fat32 card.
 
For SD Cards I only use exfat card for game dump backups nuff said
HDD Exfat is fine so load installs from it

This won’t change

Nintendo just add ntfs support plz

Thanks
 
But who has actually encountered a problem? I use exfat and have done always. My friends all use exfat. Not a single one of us has ever had any problems, whatsoever.
I won't cliam to know much about the topic, so my question is genuine. I always hear people say exfat is a really bad idea, but at the same time I don't think I've heard of anyone actually having problems with it.
If a crash occurs on FAT32, it might corrupt whatever file it was writing to, if a crash occurs on ExFAT, it's likely to corrupt your entire card if it was writing to it at that moment. Maybe you've been lucky enough to not experience crashes so far, but they can happen even on OFW. When Pokemon Sword/Shield came out SciresM did a writeup about a bug in the game that caused full system crashes, and if you had autosaving enabled in the game, it was likely to crash during the autosaving, potentially corrupting your card, regardless of whether you played the game legit on OFW, or pirated it.
This actually happened to people, which is how the bug was discovered to begin with.
Crashes are rare on OFW, true, but they happen quite commonly on CFW, all it takes is a buggy or misconfigured piece of homebrew, leaving behind old files in the Atmosphere folder when updating, or inserting a game cart when you have a mismatched game cart FW. So it's especially important when using CFW to avoid ExFAT because the risk is 10x greater that your card will end up corrupted sooner or later.
This is the sort of thing I'd like to have explained a bit deeper. People always just type this sort of thing. I've used Atmosphere since RCM became a thing. What problems does it cause?
Read above.
For SD Cards I only use exfat card for game dump backups nuff said
HDD Exfat is fine so load installs from it

This won’t change

Nintendo just add ntfs support plz

Thanks
That would be even worse, because NTFS is proprietary and there are no official specifications released. Even Linux' NTFS drivers aren't perfect. NTFS also isn't optimized for flash storage.
 
For SD Cards I only use exfat card for game dump backups nuff said
HDD Exfat is fine so load installs from it

This won’t change

Nintendo just add ntfs support plz

Thanks
i still persist in using exfat not fat32, sometimes use another fat32 sdcard for cheat data searching. but i don't think nintendo will add ntfs support maybe they consider sdcard is flashdisk not HDD。
 
If a crash occurs on FAT32, it might corrupt whatever file it was writing to, if a crash occurs on ExFAT, it's likely to corrupt your entire card if it was writing to it at that moment. Maybe you've been lucky enough to not experience crashes so far, but they can happen even on OFW. When Pokemon Sword/Shield came out SciresM did a writeup about a bug in the game that caused full system crashes, and if you had autosaving enabled in the game, it was likely to crash during the autosaving, potentially corrupting your card, regardless of whether you played the game legit on OFW, or pirated it.
This actually happened to people, which is how the bug was discovered to begin with.
Crashes are rare on OFW, true, but they happen quite commonly on CFW, all it takes is a buggy or misconfigured piece of homebrew, leaving behind old files in the Atmosphere folder when updating, or inserting a game cart when you have a mismatched game cart FW. So it's especially important when using CFW to avoid ExFAT because the risk is 10x greater that your card will end up corrupted sooner or later.

Read above.

That would be even worse, because NTFS is proprietary and there are no official specifications released. Even Linux' NTFS drivers aren't perfect. NTFS also isn't optimized for flash storage.
First ever actual explanation I've seen. Thanks.
Not that it'll make me change to FAT32, but now I at least know what'll happen etc.
 
fat32 and exfat can both get corrupted, but it's unlikely running official software.

It is mostly a problem with retroarch.
 
Since my card is on exFAT atm can it be seamlessly converted into FAT32 without losing any data (like just convert and not format) or do I need to backup all the data somewhere else first, format the card to FAT32, and then move the backup data back to the card?

Also can installed games on a exFAT card be higher than the 4GB limit that FAT32 has in the sense that when a game is installed they can turn into a single file larger than 4GB or the installation process will always make sure to install in chunks smaller than 4GB regardless if the source file was bigger than 4GB?

Anyway, is there any homebrew that by nature will only work under FAT32 and not exFAT?
 

Site & Scene News

Popular threads in this forum