macOS Error "The Operation Can’t Be Completed" – 6 Fixes That Work

Cause #1: File/Folder Permissions Are Out of Whack

You try to delete a file, drag something to Trash, or move a folder and boom—“The operation can’t be completed because you don’t have permission to access some of the items.” This is the most common flavor of this error. It’s not that you’re locked out by some sinister admin; it’s that the file’s permission bits got corrupted, often after copying from an external drive or a network share.

I’ve seen this happen with files copied from a Windows NTFS drive or an old Time Machine backup. The permissions get weird in transit. The fix is to reset those permissions.

Fix: Get Info to the Rescue

1. Right-click the stubborn file or folder and choose Get Info (or press Cmd+I).
2. At the bottom of the Get Info window, click the lock icon and enter your admin password.
3. Under Sharing & Permissions, set your user account to Read & Write.
4. Click the gear icon and choose Apply to enclosed items if it’s a folder.

That usually clears it. But if Get Info won’t even open or the permissions won’t stick, head to Terminal and force it:

sudo chmod -R 755 ~/Desktop/StubbornFolder

Replace the path with your file’s actual location. The -R flag applies it recursively. I always follow that with a quick sudo chown so ownership matches your username:

sudo chown -R $(whoami):staff ~/Desktop/StubbornFolder

That’s the surgical fix. If it still refuses, skip to Cause #2 because your file might be locked at the file system level.

Cause #2: The File Is Locked (Or a Disk Image Is Mounted)

Another sneaky trigger: the file or folder is marked as locked, or a .dmg (disk image) you downloaded is still mounted. I once spent an hour trying to delete a folder that contained a mounted DMG—macOS quietly refuses because the volume is in use.

You’ll often see this when you download an app and drag it to Applications, then try to eject the DMG. Or when you delete a file that has the “Locked” checkbox ticked in Get Info.

Fix: Unlock First, Then Unmount

1. In Get Info, uncheck Locked. That’s the obvious one.
2. For disk images, open Finder > Go > Utilities and launch Disk Utility.
3. In the sidebar, find the DMG volume—it’s the one with the little eject icon next to it. Click that icon to unmount it.

If Disk Utility is being flaky, don’t stress. Terminator—I mean Terminal—has your back:

hdiutil detach /Volumes/YourDiskName

If it says “Resource busy,” try adding -force at the end. That’s a last resort, but sometimes you need a virtual two-by-four.

Now delete the file. If it still won’t budge, it’s time to check the file system itself—that’s Cause #3.

Cause #3: External Drive Corruption

When the error appears with an external drive—like a WD My Passport or a SanDisk USB stick—and especially with code -36 or -50, you’re dealing with file system corruption. I know this error is infuriating because it’s so generic; it could mean anything. But after years of helping users, about 70% of external drive “can’t be completed” errors trace back to a dirty filesystem.

The trigger could be yanking the USB cable out without ejecting, a power surge, or a drive that’s formatted as FAT32 (which macOS doesn’t handle gracefully).

Fix: Run First Aid

1. Open Disk Utility (again, Finder > Go > Utilities).
2. Select your external drive in the sidebar—not the volume below it, the actual drive.
3. Click First Aid and let it run. It’s like a doctor for your disk.

If First Aid finds nothing, check the format. If it’s FAT32 or exFAT, and the drive is only for Mac use, reformat it to APFS. That alone fixes a huge chunk of file-operation errors. Back up your data first—reformatting wipes everything, and I don’t need to tell you what losing your photos feels like.

But wait—there’s another culprit that gets overlooked.

Bonus Cause: Cloud Storage and Metadata Weirdness

If your file sits in iCloud Drive, Dropbox, or OneDrive, the error often appears because the file is still syncing or has placeholder metadata that macOS can’t resolve. You’ll see this when you try to delete a file that’s only a stub on disk, not the full file.

The fix is to ensure the file is fully downloaded. In Finder, right-click the file and choose Download Now. Once it’s solid, delete it. If that fails, pause sync in the cloud app’s menu bar icon, delete, then resume.

Also, don’t forget to check if you’re running macOS Sonoma 14.x with an old version of the syncing app—I’ve seen weird conflicts there. Update the app first.

Quick-Reference Summary

That’s the short list. If you’ve tried all of this and the error still taunts you, drop a comment with your exact macOS version and the error code (like -36 or -8080). I’ll help you troubleshoot it manually—I’ve got a soft spot for stubborn files.