High Sierra Destroys FAT32

download Forklift from the app store... I had the same issue using finder an was able to copy to FAT32 format using Forklift file manager. I spoke to Apple Support and the rep was not aware of the problem. I told here I saw the problem on the web a she checked with a supervisor and was told the developers are working on a fix

I have the same problem too.

BUT! If you don't use Finder, instead use Terminal for copying files it works! I realized it when I couldn't get my files copied, but when I did my backup it went through. (and I know that my backup software is using Terminal commands)

For copying in Terminal see: https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPag es/man1/cp.1.html

Or type in, in the Terminal "man cp".

Basically it is: "cp source_file target_file"

Somebody may already have replied: via Terminal you can copy up to 4 gbyte files in size. Via Finder, no. At least 'till now (10.13.3).

Tip: type in terminal:

- sudo cp + (drag origin file into Terminal) + (drag destination disk/folder) + ENTER

- if you want to copy a folder add "-R" after sudo cp

waste of time been complaining about this since the first Beta release of High Sierra and have been totally ignored since just install Commander one.

it caused me a lot of problems at first when i was moving some large files 2gb-2.5gb from some flash drives unfortunately exfat is not fully supported on some devices (but it works on files over 2GB) however Commander one works and its better than finder its now my default i am kinda glad Apple allowed this bug to drag on or i wouldn't have known about Commander one's software 😉

Apple haven't cut the file size because you can save files >2GB (and <4GB) to USB drives using the cp command in Terminal.

What is WRONG (when you try using Finder to copy files) is that:

1) the error message says that the EXTERNAL drive's format does not support files of this size, when it clearly DOES

2) The files will not copy via Finder.

This is sloppy coding by Apple (again). Something that is becoming ever increasingly common with MacOS updates.

The main problem is that not enough users can be bothered to file a FEEDBACK on these errors, and just put up with it.

*sigh*

Adam, I posted "This appears to be fixed now on 10.13.4."

Which part of "10.13.4" did you not understand?

The whole point of my previous post was to let people (who are a part if this thread) know that the latest update to High Sierra (13.10. FOUR) has actually fixed this ongoing error in Finder in High Sierra.

Turns out that Apple DO actually get round to fixing stuff IF they get enough FEEDBACK - https://www.apple.com/feedback/macos.html - (rather than people just b*tching in forums).

Sorry, I missed your reply before I posted. Just updated to 10.13.4 and indeed can confirm this issue has finally been fixed. Thanks all.

it's not a bug correct! it seems this is how it is now with the new APFS finder will not copy or move any file of 2GB and over (under 4GB) to a FAT32 formatted USB/HD/SD etc just refuses and has done this since the first beta of High Sierra i can only format the drives to exfat or use "commander one" they have never ever contacted me about this and i imagine others also! i reported it before i saw any others complain via the internet or google searches!

only now it's coming to light from other uses.

It's a bug. The file size limit for FAT32, as you are aware, is 4 GB. High Sierra is treating it as if it were FAT with a 2GB file size limit.

Apple is aware of the problem.

I am getting around this using an app called forklift but am also not happy that the Apple has gone mouldy

This is still broken... running 10.13.3. Had to fire up parallels to copy a 3GB file to a FAT32 formatted USB stick.

majortom, you don't need "sumo" in this case.

A simple "cp" then (drag origin file into Terminal) then (drag destination disk/folder) and press ENTER works just fine.

Makes no sense though why this Finder bug has still not been fixed though. I guess a visit to the feedback page is in order (... again ... *sigh*)

Ahah! Found the easiest of all workarounds! Use the terminal! Thank goodness for linux!

cp mybigfile.mov /Volumes/UNTITLED

This appears to be fixed now on 10.13.4.