Files on a FAT32 USB drive often fail to delete in macOS because the system caches directory entries or the volume is mounted read-only due to corruption. The most reliable fix involves using Terminal commands to force unmount, verify permissions, and eject the device properly, ensuring the file system metadata is updated before removal.
Why FAT32 Deletion Fails on Mac
FAT32 is an older file system that lacks modern access control lists (ACLs) and journaling features found in APFS or NTFS. When you attempt to delete a file on a Mac, the operating system must update the File Allocation Table to mark clusters as free. If this process is interrupted, or if the drive is not safely ejected, the table can become inconsistent. Unlike native Mac volumes, FAT32 does not have a standard.Trashes folder mechanism that blocks deletion; instead, failures usually stem from permission mismatches, cached locks, or physical write-protection switches.
Many users encounter this issue when transferring large files or when the drive is accessed by multiple devices. macOS may hold a lock on the volume if background processes like Spotlight indexing or Time Machine backups are attempting to scan it. This results in the "Item Can't Be Completed Because It Is Being Used" error, even though no visible application is open. Understanding these underlying mechanics helps in choosing the right troubleshooting step rather than simply retrying the drag-and-drop action repeatedly.
Step-by-Step Resolution Using Terminal
When Finder fails to delete files, the command line provides direct access to the file system driver. This method bypasses the graphical interface's caching layer and allows for precise diagnostic output. Follow these steps carefully to resolve persistent deletion errors. First, identify the mount point of your USB drive. Open Terminal and run the following command:df -h | grep disk/Volumes/YourDriveName. Note this path exactly. Next, check the current permissions of the volume by running:
ls -ld /Volumes/YourDriveNamedrwxr-xr-x and the owner is root, this is normal for FAT32. However, if you see unexpected restrictions, you may need to adjust ownership. For FAT32, you generally cannot change POSIX permissions directly on the drive itself, but you can ensure your user has write access by remounting with specific flags.
To force a clean unmount and remount, use the diskutil command. Replace diskN with your actual disk identifier (found via diskutil list):
diskutil unmountDisk /dev/diskN
diskutil mountDisk /dev/diskNrm -rf "/Volumes/YourDriveName/ProblematicFile"Preventing Future Issues
Consistent failure to delete files often indicates broader health issues with the USB stick or the host system. Regularly ejecting drives using the Finder sidebar icon prevents metadata corruption. If you frequently exchange drives between Windows and Mac machines, consider formatting them as exFAT instead of FAT32. exFAT supports larger files and has better cross-platform compatibility while maintaining simpler permission structures. For more detailed guidance on managing FAT32 volumes, refer to our guide on How to Delete Files on a FAT32 Formatted USB Flash Drive on MacOS?. Additionally, if renaming operations also fail, check How to Delete Files on a FAT32 Formatted USB Stick on MacOS and Renames Files for advanced permission fixes.Verifying Drive Health
If deletion issues persist after correcting permissions and unlocking the drive, the flash memory itself may be failing. Use the First Aid feature in Disk Utility to check for logical errors. Select the USB drive in Disk Utility, click "First Aid," and allow the process to complete. This tool scans the directory structure and repairs minor inconsistencies that prevent file operations. Corrupted sectors can also cause silent write failures. If First Aid reports errors that cannot be repaired, back up any accessible data immediately and format the drive. Formatting erases all data but restores the file system to a clean state. Choose FAT32 for maximum compatibility or exFAT for larger file support. Avoid keeping critical data on aging USB sticks, as they have limited write cycles and can fail unexpectedly.Frequently Asked Questions
Can I recover files deleted from a FAT32 drive on Mac?
Yes, but success depends on whether new data has overwritten the freed space. Stop using the drive immediately to prevent overwriting. Use recovery software like PhotoRec or TestDisk to scan the raw sectors of the USB stick. These tools ignore the file system structure and look for recognizable file signatures.
Why does my USB drive appear read-only in macOS?
This usually happens due to file system corruption or a physical write-protection switch. Check for a small slider on the drive casing that might be engaged. If the switch is off, run Disk Utility's First Aid to repair the volume. If corruption is severe, reformatting may be necessary.
Is it safe to force eject a USB drive if Finder hangs?
Force ejecting carries a risk of data loss or file system corruption. Always wait for the drive icon to disappear from the desktop first. If Finder freezes, restart your Mac or use Terminal to unmount the disk cleanly. Force ejecting should be a last resort when the system is completely unresponsive.
Does FAT32 support hidden files on Mac?
FAT32 does not natively support Unix-style hidden files (those starting with a dot). However, macOS can create them using extended attributes. These files may behave unpredictably when moved between different operating systems. To avoid confusion, ensure all files on FAT32 drives have standard names without leading dots.
What causes "The operation can't be completed because the item is in use"?
This error occurs when a background process holds a lock on the file or directory. Common culprits include Spotlight indexing, antivirus scanners, or media players accessing the drive. Quit all applications and wait a few minutes before trying again. Using Terminal to unmount and remount the drive can also release stubborn locks.