Yeah, that error box is annoying as hell. You try to delete a file, move something, or eject a drive, and macOS just says “The operation can’t be completed because you don’t have permission to access some of the items.” Or sometimes it just says “The operation can’t be completed. An unexpected error occurred (error code -43).” You’ve been there. Let’s fix it.
First, the direct fix: Repair permissions with Disk Utility
Don’t bother with terminal chown spree yet. The culprit here is almost always a corrupted permissions entry or a stray metadata file. Here’s what works 90% of the time:
- Open Disk Utility (from Applications/Utilities or Spotlight).
- In the sidebar, select the disk that has the problem — internal Macintosh HD or the external drive.
- Click First Aid at the top, then hit Run.
- Let it finish. It’ll take a few minutes on big drives. It reports any errors it found and fixes them.
After that, try the operation again. In most cases, it just works. If not, we move to the next step.
Why First Aid actually works
First Aid checks the filesystem structure, permissions bits, and metadata. When you see that “don’t have permission” error but you’re the admin and the file is yours, it’s not that you lack access — it’s that the ACLs or ownership flags got scrambled. A crash, a failed install, or a cable yank on an external drive can leave those in a bad state. First Aid rewrites the metadata index flags. It’s a bit like a filesystem chiropractor. It doesn’t touch your data, but it resets the structure to what the OS expects.
Less common variations and how to handle them
1. Error -43 on external drives or network shares
This one’s different. It usually means the file or folder has a hidden ._AppleDouble file that’s left over from a copy operation or a weird sync. First Aid won’t always catch it. The quick fix is to remove those hidden files:
find /Volumes/YourDrive -name '._*' -deleteRun that in Terminal, replacing /Volumes/YourDrive with the actual mount point. It deletes all those dot-underscore files. That usually clears the error. If the drive is still stubborn, try copying everything off, reformatting the drive, and copying back. Painful but bulletproof.
2. “You don’t have permission” on your own home folder
Sometimes you get this on files inside your own home folder. That’s not a disk issue — it’s a Spotlight or metadata index glitch. Here’s the fix: go to System Settings > Spotlight > Search Privacy, drag your entire home folder into the list. Wait ten seconds, then remove it. That forces Spotlight to rebuild its index. The error often disappears because the file’s metadata gets refreshed.
3. Trash won’t empty
Same error when you try to empty the Trash? That’s typically a locked file or a file with an odd name (like one with a forward slash). You can force it from Terminal:
sudo rm -rf ~/.Trash/*Be careful — that nukes everything in your Trash permanently. If you want to keep something, pull it out first. The sudo command bypasses the permission check.
Prevention: Stop it from happening again
There’s no magic bullet, but a few habits cut the frequency:
- Eject drives before unplugging. I know, it’s tempting to just yank the USB stick, but that’s how you get corrupt metadata. Right-click and Eject every time.
- Keep your disk from filling up. When macOS runs low on free space, it gets sloppy with metadata writes. Keep at least 10% free.
- Don’t interrupt system updates. They do a lot of permission churn in the background. Let them finish, even when it looks stuck.
- Run First Aid monthly. Make it a habit, like changing your oil. Most people only run it when something breaks.
Look, this error is a classic macOS quirk. It’s been around since Snow Leopard and it’s not going anywhere. But with these steps, you’ll spend less time staring at that grey box and more time actually getting stuff done. If you’re still stuck after all this, you’re probably dealing with a failing drive — back up now and check SMART status in Disk Utility.