Hello all,

I've noticed that in Windows, when copying the Avid project folder to an exFAT drive (and it will not happen with an NTFS drive), a Windows prompt for an "Interrupted Action" appears for what seems like every Avid Bin file, asking:

"Are you sure you want to copy this file without its properties?

The file [file name] has properties that can't be copied to the new location."

When I click "Yes" and proceed to copy anyway, the entire project folder and the bins in question do copy over, and the sizes of the folder and each bin file are the same as they are on the source versions on the local NTFS drive, down to the byte.

Should I have any concern about data not making it over to the exFAT drive?  This would be for eventual copying onto a Mac formatted drive.

I searched the forums and only found a reference, in a post from 2011, to exFAT not writing "extended folder data", where a prompt appears similar to copying to old FAT formatted floppies.

If anyone has any thoughts, I would greatly appreciate it.

Thanks!

There are some major differences between exFAT and NTFS, most notably exFAT lacks things like file permissions, disk quotas, journaling, etc. These feature are supported with NTFS and Apples APFS. The exFAT file system is lightweight and has no file size limits. It's also the only compatible file system that can be used with both Windows and MacOS.

Also unlike NTFS and HFS+ if the drives directory becomes corrupt exFAT lacks the redundancy to scan and repair.

I never use ExFAT for content I don't have a copy of elsewhere.

Basicay it's a useful cross platform transfer format. Little else. 

Thank you both for those details on how exFAT operates.

Does anyone have any thoughts on the Windows prompt I mentioned, that has only appeared for me when copying bin files?  I wonder what it reflects, and if it should have any material effect on the bin file when it leaves the exFAT drive and lands on an HFS+ drive and is accessed in Avid.  This "Interrupted Action" prompt occurs in Windows when copying from a local NTFS drive to an exFAT drive:

"Are you sure you want to copy this file without its properties?

The file [file name] has properties that can't be copied to the new location."

When I tell Windows to proceed and copy it, it is copied to the exFAT drive and the size of the file is identical.

Thanks again.

I can't tell exactly what attributes are being lost in the copy but I can tell you it has no impact on the function of the bins. 

This was also an issue when copying Mac based files to Windows systems with their data and resource fork. 

Just ignore the message.