DiskImageMounter can't be opened (-36)

Discussion in 'macOS Sierra (10.12)' started by GerritV, Dec 23, 2016.

  1. GerritV macrumors 65816

    Joined:
    May 11, 2012
    #1
    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.
     
  2. MTShipp macrumors 6502a

    Joined:
    Mar 25, 2009
    Location:
    Raleigh, North Carolina
    #2
    Same issue here. Following this thread in case someone has an answer.
     
  3. dianeoforegon macrumors 6502a

    dianeoforegon

    Joined:
    Apr 26, 2011
    Location:
    Oregon
    #3
    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
     
  4. GerritV, Dec 24, 2016
    Last edited: Dec 25, 2016

    GerritV thread starter macrumors 65816

    Joined:
    May 11, 2012
    #4
    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.
     
  5. bcave098 macrumors 6502a

    bcave098

    Joined:
    Sep 6, 2015
    Location:
    Northern British Columbia
    #5
    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.
     
  6. GerritV thread starter macrumors 65816

    Joined:
    May 11, 2012
    #6
    Thanks, your tip works !! Why didn't I think of that ?
     

Share This Page