TS1402: Unable to move, unlock, modify, or copy an item in Mac OS X

Learn about Unable to move, unlock, modify, or copy an item in Mac OS X
jacolonia

Q: error code -8072

i want to delete 3 files i says i cant. a window pops out saying this massages "error code -8072"

 

what should i do??

MacBook Air (13-inch Late 2010), OS X Mountain Lion (10.8.2)

Posted on Sep 25, 2012 11:17 AM

Close

Q: error code -8072

  • All replies
  • Helpful answers

  • by BDAqua,

    BDAqua BDAqua Sep 25, 2012 11:45 AM in response to jacolonia
    Level 10 (123,765 points)
    Sep 25, 2012 11:45 AM in response to jacolonia

    That is a Permissions problem, did you maybe trash some Time Machine files in the Finder?

     

    If not then, Solving Trash Problems...

     

    http://thexlab.com/faqs/trash.html

  • by JenniferEdwardxs,

    JenniferEdwardxs JenniferEdwardxs Mar 11, 2013 7:20 AM in response to jacolonia
    Level 1 (0 points)
    Mar 11, 2013 7:20 AM in response to jacolonia

    Hi, i also got the error, but i already fixed it, suggest you try the way from: How To Fix Error Code -8072

    Hope this information is helpful for you, too.

  • by David J. E. Marsh,

    David J. E. Marsh David J. E. Marsh Feb 24, 2014 5:51 AM in response to jacolonia
    Level 1 (0 points)
    Feb 24, 2014 5:51 AM in response to jacolonia

    I had this error when trying to delete or move a file after an application crash (Microsoft Powerpoint). I had already recovered the file and saved it in another location, but couldn't delete the old corrupted version.

     

    There is a very simple fix to this. Use the Terminal! The terminal can override all this silly error code business.

     

    Open the terminal, go to the folder with the file you want to remove and do the following.

     

    First, make a copy, just to double check you don't lose anything you want to keep.

     

    cp Oldfile.extension Newfile.extension

     

    Now delete the old file giving the error code

     

    rm -Rf Oldfile.extension

     

    Done! Newfile.extension was in my case uncorrupted and could be manipulated with no errors inside Finder.