TeraCopy truncates files at 4GB when copying from a Macrium tbFAT filesystem
This is a rare situation, but FYI teracopy has a bug where Windows Explorer copy and robocopy works fine. I have a file-and-folder backup created using Macrium Reflect 8.1.8017. If I mount the backup with a drive lever, windows 10 Win32_LogicalDisk reports the following about the drive letter:
DriveLetter : L
Provider : FileSystem
Root : L:\
DriveType : Network
FileSystem : Macrium tbFATThe Macrium tbFAT driver supports up to 3.9TB. However if I copy files from this source to an NTFS destination using TeraCopy 3.17.0.0 the transfer will complete and validate the checksums, but truncate files at 4GB as if the destination were FAT32. If I copy files using TeraCopy 4.0.0.37 it will copy the full size, but then either hangs during checksum validation or fails validation for file size mismatch reasons. And the copy operation is odd. It reports the files size to be copied as 4GB, but then for example if the file is actually 12GB, it continues copying until the file is 300% complete.
Log in to comment and vote
Comments2
Jul 11
PinnedThis happens because Macrium tbFAT reports file sizes as 4 GB through the
GetFileInformationByHandlefunction. Upon investigation, we found that the WindowsGetFileInformationByHandleExfunction reports the correct file size, so it was an easy fix.Please update to this version: teracopy4.0.2.exe
ryan-feeley
Jul 15
Thanks for the quick response and the fix. I can confirm this is now working as expected. Cheers!