Ad Space — Top Banner

-8076

Apple MacBook

Severity: Moderate

What it means

MacBook error -8076 is a macOS Finder permissions error.
The Finder's exact dialog reads: 'The operation can't be completed because you don't have permission to access some of the items. (Error code -8076)'
It appears when you try to move, copy, or rename a file or folder your user account doesn't have Read & Write permission for.
The fix is almost always to adjust the file's Sharing & Permissions in Get Info — or, if the file is system-owned, run the operation from an admin account in Terminal.

Affected Models

  • Every MacBook running macOS
  • Common on files copied from another Mac with a different user ID
  • Common on files restored from a Time Machine backup made by a different user account
  • Common in the Applications folder when modifying installed apps
  • Affects every recent macOS — Sequoia, Sonoma, Ventura, Monterey, and earlier

Common Causes

  • Your user account doesn't have Read & Write permission on the file or folder
  • File is owned by root or another user (very common on system or app files)
  • Folder being moved contains a sub-item with restrictive permissions
  • Drive's 'Ignore ownership on this volume' setting is off and ownership doesn't match
  • File has an Access Control List (ACL) that blocks your user explicitly

How to Fix It

  1. Open Get Info and check permissions.

    Right-click the file or folder, choose Get Info.
    Scroll to Sharing & Permissions at the bottom.
    Find your username in the list.
    If the privilege next to your name says Read Only, click it and change to Read & Write.
    Close Get Info and retry the operation.

  2. Apply permissions to enclosed items if it's a folder.

    Still in Get Info on the folder, click the lock icon at the bottom-right and enter your password.
    Click the action menu (the gear or '...' icon) and choose 'Apply to enclosed items.'
    This pushes the Read & Write permission down through every file inside the folder, not just the folder itself.

  3. Check 'Ignore ownership on this volume' for external drives.

    If the file is on an external drive, open Get Info on the drive itself (not the file).
    At the bottom under Sharing & Permissions, check the box 'Ignore ownership on this volume.'
    External drives often have permissions that don't match your current user account — ignoring ownership tells macOS to let your user act as the owner.

  4. Run the operation via Terminal sudo.

    If Get Info won't let you change permissions (greyed out, even after unlocking), the file is system-owned and needs admin rights.
    Open Terminal and run: sudo mv ~/source/path ~/destination/path
    Or for a copy: sudo cp -R ~/source/path ~/destination/
    Type your password when prompted.
    This runs the operation as administrator, bypassing the permission block.

  5. Use chown to take ownership of the file.

    If you want to permanently own a file that's currently owned by another user, run: sudo chown $(whoami) ~/path/to/file
    That changes the file's owner to your current user account.
    Now the regular Finder operations work without sudo — and -8076 stops appearing on that file.

When to Call a Professional

Error -8076 doesn't need a technician.
Setting your user account to Read & Write in Get Info fixes the vast majority of cases.
If the file is system-owned and refuses to budge from Get Info, run the operation as the admin user via Terminal sudo.

Frequently Asked Questions

Why does -8076 happen on files I copied from my own backup?

Time Machine and other backup tools preserve the user ID of the original owner — not your current user account.
If you restored files from a backup made on a different Mac (or made before you set up your current account), the files keep the old user ID and your current account sees them as owned by someone else.
Use the Get Info > Apply to enclosed items workflow described above, or run: sudo chown -R $(whoami) ~/restored-folder/ to take ownership of every restored file in one command.