macOS 'The operation can’t be completed' Error Fixes

1. Permissions — the most common culprit

I've seen this error a thousand times, and nine times out of ten, it's file permissions. You try to drag a folder from external drive to Desktop, and boom—The operation can’t be completed because you don’t have permission to access some of the items. Infuriating, right? The fix is simple: reset permissions using Disk Utility.

Open Disk Utility (from /Applications/Utilities/). Select the drive containing the files. Click First Aid then Run. It'll check and repair permissions and disk structure. On APFS volumes (macOS 10.13+), this fixes most permission errors. I've had it work on macOS Ventura and Sonoma with external SSDs and HDDs.

If that fails, open Terminal and run:

chmod -R 755 /path/to/folder

Replace /path/to/folder with the actual path. This gives read/write/execute to the owner, read/execute to everyone else. Works like a charm when the drive is formatted as APFS or Mac OS Extended.

Real-world trigger: You just copied files from a colleague's drive and they were owned by a different user ID. The error pops up during the copy because macOS checks ownership.

2. Disk errors — when permissions aren't the problem

Sometimes permissions are fine, but the disk itself has a hiccup. This happens a lot with external drives that were improperly ejected. The error message stays the same, but you'll notice it happens with multiple files, not just one.

Run First Aid on the specific volume from Disk Utility (not just the container). For external drives, connect via a different cable or port—I've seen bad USB-C cables cause this. Also check if the drive is formatted in a way macOS reads properly. ExFAT drives (common for cross-platform use) can develop errors that look like permission issues.

If First Aid finds nothing, try copying the files via Terminal:

cp -R /source/folder /destination/folder

This bypasses Finder's error handling. If it copies fine, the problem is Finder-specific—try restarting Finder (Option + Right-click Finder icon, select Relaunch). If Terminal also fails, the drive has real corruption. Back up immediately and reformat.

Real-world trigger: You yanked out a USB drive without ejecting. Next time you plug it in, every copy operation fails with this error.

3. Hidden files or character conflicts — the sneaky cause

This one tripped me up the first time. The error shows up when copying a folder that contains hidden files (like .DS_Store or ._ AppleDouble files) or filenames with illegal characters (colons or slashes on old HFS+ drives). macOS Finder hates these.

Check if the folder has hidden files by running in Terminal:

ls -la /path/to/folder

Look for files starting with a dot or with weird symbols. Delete them or move them out. Alternatively, zip the folder first (right-click > Compress), then copy the zip file. I've used this trick dozens of times on network drives that were shared with Windows machines.

For character conflicts, rename the file to something simple (like file.txt) and try again. If that fixes it, rename back carefully—avoid colons, slashes, and leading dots.

Real-world trigger: You downloaded a batch of photos from a Windows PC that used colons in filenames. macOS refuses to write them to your local drive.

Quick reference summary

If none of these work, check if the source drive is nearly full—less than 10% free space causes random failures. And if you're copying to a cloud-synced folder (iCloud Drive, Dropbox), pause sync first. That's another common gotcha I've seen in support tickets. Hope this saves you the hour I wasted the first time.