DiskImageMounter can't be opened (-36)

[GerritV]

Double-clicking on my old TimeMachine backup results in an error message "DiskImageMounter can't be opened (-36)". It used to work before, so it might be caused by my recent update to 10.12.2 ??

The file info says it should be opened by DiskImageMounter per default. Also, I can perfectly open other dmg's.

All suggestions on how to access my old TimeMachine data are very welcome.

 

[MTShipp]

Same issue here. Following this thread in case someone has an answer.

 

[dianeoforegon]

Most likely the file itself is corrupted. The error -36 often indicates a hardware issue. If the file is on a bad disk and you try to copy the file, you get the -36 error. If the following does not help, the file is too damaged to recover.

Try running Disk Utility > Repair Disk. Disk Utility can be found in Applications/Utilities.

See other options here:
https://in.answers.yahoo.com/question/index?qid=20100402121353AATVlMt

 

[GerritV]

Most likely the file itself is corrupted. The error -36 often indicates a hardware issue. If the file is on a bad disk and you try to copy the file, you get the -36 error. If the following does not help, the file is too damaged to recover.

Try running Disk Utility > Repair Disk. Disk Utility can be found in Applications/Utilities.

See other options here:
https://in.answers.yahoo.com/question/index?qid=20100402121353AATVlMt

Thanks for the tip. Unfortunately, my TimeMachine backup file is on a TimeCapsule.
This device doesn't show up in Disk Utility's sidebar.
I now wonder if the Terminal command from your yahoo link will work ?

Next, my wife's TimeMachine backup file is on the same TimeCapsule, and producing the same error. So file damage on both, at the same time, looks a bit too coincidental to me.

[EDIT]
I've looked closer into it, and in fact I can't open ANY file on my TimeCapsule drive.

 

[bcave098]

I think it's a 10.12.2 bug. Try to open a file from an app (i.e. open the app, or Disk Utility, first then open the file), I'd bet it will work normally.

 

[GerritV]

I think it's a 10.12.2 bug. Try to open a file from an app (i.e. open the app, or Disk Utility, first then open the file), I'd bet it will work normally.

Thanks, your tip works !! Why didn't I think of that ?