Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Slartibart

macrumors 68040
Aug 19, 2020
3,145
2,819
You are copying files from the Apple OS to Windows and the Apple files are composed of what's called a ' resource fork'- that is in fact there are 2 files.
It isn’t a resource fork. These are DS_Store (Desktop Services Store) files, the macOS version of Windows's desktop.ini files, which are automatically created by Finder on local internal & external disks or remote filesystems mounted from servers to store a folder's custom view.

You don't see the ones with the '-' when you use the ipad or Mac but windows sees them. You can just delete those and there's a program I found somewhere that deletes them automatically.
indeed.
I think there might be a setting somewhere about using Windows friendly format or something but I don't know much about this and others can give you way more info or you can look up 'resource fork'.
On MacOS you can turn the creation of DS_Store files for external media off using e.g. Onyx or via terminal:

defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE
In my experience and corrupted transfer data, it always turns out to be the cable.
Sadly, this is probably not the main cause on iPadOS.
 
Last edited:

sparksd

macrumors G3
Original poster
Jun 7, 2015
9,996
34,294
Seattle WA
So does this mean that the corruption issue is with the Files app instead of the iPadOS?
So it would seem.
You are copying files from the Apple OS to Windows and the Apple files are composed of what's called a ' resource fork'- that is in fact there are 2 files.
You don't see the ones with the '-' when you use the ipad or Mac but windows sees them. You can just delete those and there's a program I found somewhere that deletes them automatically. I think there might be a setting somewhere about using Windows friendly format or something but I don't know much about this and others can give you way more info or you can look up 'resource fork'.

In my experience and corrupted transfer data, it always turns out to be the cable.
It is not the cable as I have tested with multiple drives and cables.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.