Time Machine error code -36

Hello

I am no expert.

I have this problem too; I think it's a simple "catch 22" situation caused by having files that have been on a mac, copied to a Microsoft machine and back again. (It may not be all files but one in a batch that has had "background" files altered by this process is enough to halt a copy, move or recover command.) I suspect we will come to call this a "Catch 36" problem!

The "catch 22" is; There is a mildly corrupted file on your Mac, your Time Machine backs up (Time Machine files can't be altered by default so can't be cleaned by dot_clean in Terminal) Then the Mac refuses to restore/copy/move back from Time Machine as it reads the files as corrupted (they aren't corrupted they have just managed to acquire some residual information ("dot_") in some previous copying files process). This prevents restoring these files back to your Mac.

I suppose we should have both formatted our backup destination storage (Time Machine) to a Mac format at inception. Then kept away from Microsoft (as Apple seam to want us to do)

I have a MacBook Pro (running 10.9.5, 16GB RAM 1600mhz DDR3, Graphics
Intel Iris Pro 1536 MB.) but I partitioned and did a co-instal of High Sierra to see if this would be sophisticated enough to allow me to get around this but it isn't. I used to back up to a Lacie Thunderbolt 3TB, that is where all my back-up files reside.

Some files are able to copy back either individually or in small batches but if I inadvertently try with a file that is affected them my Mac just seizes!

I hope Apple can chip in here as it is a profound problem caused by us trusting our precious information to the Time Machine concept. If we had manually backed up to an external disk without Time Machine we could have run a simple command from "Terminal" to rectify this, Time Machine won't allow this.

Good luck

NH

I think that Error Code 36 normally is a response by OSX when it tries to read files (or metadata accompanying a file) with ._ (or DOT_ which may be a normal code but only generated when copying/reading/editing ms-windows files) which it refuses to read - I make it sound like I know what I'm talking about but this is just what I've gleaned scouring this forum.

It doesn't seem to happen to everyone so it must be something related to particular circumstances.

Thanks

Yes, I understand the difference and maybe they are unrelated problems. Disk permissions and Time Machine's own encryption seem to be at the route of this for both of us. I haven't had time to contact Apple Support yet but I will and post their response too.

I did have a "mac formatted disk" not as I said earlier "microsoft formatted" so that rules out another possible cause.

Thanks

Hello

I am going to contact Apple support with this problem. I doubt very much that they will offer a solution or any constructive input but I will post their response soon.

NH