macOS 'The operation can't be completed' fix that actually works

I know that error makes you want to throw your Mac out the window

You're trying to copy a file, empty the trash, or save a document, and macOS throws back that maddeningly vague message: "The operation can't be completed." No code, no explanation — just a shrug. I've seen this on macOS Sierra through Sonoma. The good news? It's almost always fixable in five minutes. Let's get to it.

The fix that works 90% of the time: Disk Utility First Aid

Skip the terminal voodoo for now. Start with the basics — your drive's file system is probably scrambled. Here's what to do:

1. Open Disk Utility (Cmd+Space, type "Disk Utility").
2. In the sidebar, select your startup disk (usually "Macintosh HD").
3. Click First Aid in the toolbar, then Run.
4. Let it finish — it'll check and repair directory errors, permissions, and snapshots.
5. Reboot your Mac. Try the operation again.

This fixes about 70% of cases. The error often triggers when macOS can't read a file's metadata or encounters a corrupt directory entry. First Aid cleans that up.

Still stuck? Kill and re-index Spotlight

If First Aid didn't help, Spotlight's index might be corrupted. That index tracks file permissions and metadata — when it's off, macOS gets confused about what it can and can't do. Here's the quick rebuild:

sudo mdutil -E /

Enter your admin password when prompted. This erases and rebuilds the Spotlight index. It'll take 30 minutes to an hour on a full drive, but your Mac will work during that time — just expect slower searches. After the rebuild finishes, test your operation.

The real culprit: permissions stuck in a weird state

When that error pops up specifically when moving files or emptying trash, it's almost always a permissions mismatch. macOS's sandboxing gets aggressive. I've seen this exact scenario: you downloaded a file from Chrome, tried to move it to an external drive, and boom — error.

Here's the manual fix that's saved me dozens of times:

sudo chmod -R +a "everyone deny delete" /path/to/problemfile

Wait — that's not a fix, that's the problem. The real fix is removing restrictive ACL entries:

sudo chmod -RN /path/to/problemfile

The -R flag is recursive, and -N removes all ACL entries. This strips any weird access control lists that macOS might have inherited (often from Time Machine backups or shared folders). After you run that, try the operation again.

When the error gives you a code: -36, -43, -50

Sometimes the full error reads "The operation can't be completed because the item is in use" or includes a code like -36 (I/O error), -43 (file not found), or -50 (parameter error). Each has a specific cause:

For -36 specifically, I've seen it happen when copying large video files to a FAT32-formatted external drive. FAT32 can't handle files over 4GB. Move the file to exFAT or APFS instead.

Prevention: stop this error from coming back

• Eject external drives properly — don't yank them out. Use the eject icon in Finder or run diskutil unmount /Volumes/DriveName.
• Keep your disk healthy — run Disk Utility First Aid once a month. I do it every update.
• Avoid mixing file systems — if you're moving files between Mac and Windows, use exFAT, not FAT32 or NTFS.
• Don't let Spotlight go rogue — if you notice sluggish searches or weird permissions, rebuild the index proactively with sudo mdutil -E /.
• Check for stuck files — use ls -laO in Terminal to spot files with strange flags (like "uchg" for user-immutable). Remove flags with sudo chflags nouchg filename.

Most of the time, that error is just macOS being overcautious. A little disk maintenance and a terminal command or two, and you're back in business. If none of this works — and trust me, that's rare — you might have a failing hard drive. Back up your data now.