Fix 'The operation can't be completed' macOS error fast

Yeah, that 'The operation can't be completed because an unexpected error occurred' message is a classic macOS frustration. You're trying to move, copy, or delete a file and it just stops you cold. Let's fix it.

The Quick Fix: Kill the Finder's .DS_Store

Open Terminal — it's in Applications > Utilities. Copy and paste this, hit Enter:

cd ~/Desktop && rm -rf .DS_Store && sudo find / -name '.DS_Store' -depth -exec rm {} \; 2>/dev/null; killall Finder

This wipes the hidden .DS_Store files that macOS uses to remember folder view settings. When they get corrupted (which happens often), Finder locks up on file operations. After this, your Finder restarts, and the error should be gone.

If you don't want to use Terminal, you can manually delete .DS_Store files. Open Finder, press Cmd+Shift+. to show hidden files, navigate to the problematic folder, and delete any files named '.DS_Store'. Then restart Finder (Apple menu > Force Quit > Finder > Relaunch). But Terminal's faster — I use it every time.

Why This Works

.DS_Store files are Apple's way of storing icon positions, background colors, and sort orders per folder. When they get corrupted — often from copying files between macOS versions or from external drives — Finder gets confused. It tries to read the corrupted file before performing your operation, hits an error, and stops.

Deleting them forces macOS to rebuild fresh copies. That's why the error pops up most often on Desktops, Documents folders, or shared drives. I've seen this on every macOS version from High Sierra through Sonoma. The culprit is almost always a bad .DS_Store.

Real-World Trigger

This happens a lot after you restore files from Time Machine or migrate from an old Mac. The .DS_Store files get copied over from a previous macOS version, and they don't play nice with the new OS. You'll see it when trying to move files from the Desktop to a subfolder, or when deleting files right after a migration.

Less Common Variations

If the .DS_Store fix doesn't work, here are other culprits I've seen:

1. File Permissions Gone Wrong

Sometimes a file or folder has permissions that macOS can't read. Run this in Terminal:

diskutil resetUserPermissions / `id -u`

This resets permissions for your user on the boot drive. Takes a minute. Don't bother with Disk Utility's First Aid for this — it rarely helps with file operation errors.

2. Error Code -36 or -43

If you see 'error code -36' or '-43' along with the message, it's usually a file name issue. macOS can't handle certain characters — like colons (:) or very long file names. Rename the file to something short and simple (no special characters), then try again. I've fixed this for clients who had files named 'Project: Final (2024) v2.0' — that colon kills it.

3. Corrupted Spotlight Index

Spotlight indexes file metadata. If it's corrupt, Finder operations can freeze. Open System Settings > Siri & Spotlight > Spotlight Privacy. Drag your hard drive (usually Macintosh HD) into the list, wait 30 seconds, then remove it. This forces a reindex. Takes about an hour on a 500GB drive, but it's a solid fix for persistent errors.

4. External Drive Format Issues

If the error only happens on an external drive, check its format. macOS exFAT drives have issues with files over 4GB and can throw 'operation can't be completed' errors. If it's formatted as NTFS (Windows format), macOS can't write to it natively. You'll need a third-party tool like Paragon NTFS or format the drive as APFS or exFAT.

Prevention: Stop It From Coming Back

You can't completely avoid .DS_Store corruption, but you can minimize it:

Don't use Time Machine to migrate between major macOS versions. I know it's tempting, but it drags along old .DS_Store files. Do a clean install, then restore your data from a backup skip system settings.
Eject external drives properly. Always click the eject icon in Finder. Yanking a USB drive while it's writing .DS_Store files corrupts them. Seen it a hundred times.
Run the .DS_Store cleanup once a month. Add the Terminal command to a text file and run it every few weeks. Keeps Finder snappy and error-free.
Keep macOS updated. Apple has patched some .DS_Store bugs in recent updates. Ventura 13.4 and Sonoma 14.2 both fixed related issues.

That's it. Kill the .DS_Store, restart Finder, and you're back to work. If it still breaks after all this, you're looking at a deeper issue — try booting into Safe Mode (hold Shift at startup) and see if the error persists. But 9 times out of 10, it's just a corrupt .DS_Store file.