Fix 'The operation can't be completed' error on Mac

When does this error hit?

You're trying to eject an external drive after a backup, and instead of a smooth pop, you get: 'The operation can't be completed because an unexpected error occurred (error code -36).' Or you try to save a file from Pages and see the same message. Maybe you're opening a folder full of photos and it just refuses. This is a classic macOS Finder glitch that shows up most often on macOS Ventura and Sonoma, but it's been around since Mojave. The infamous 'error code -36' variant usually means a corrupted .DS_Store file or a spot of permission rot in the folder you're hitting.

What's causing it?

Your Mac uses .DS_Store files to remember folder settings — icon positions, view options, that sort of thing. When that file gets corrupted (common after a drive is yanked out without ejecting, or after a network hiccup), the Finder trips over itself. The error message is vague because macOS doesn't know how to tell you 'Hey, delete that hidden file.' The -36 code in particular means an I/O error on a file in that directory — usually the .DS_Store itself, but sometimes a trashed temp file. The good news: you don't need to reinstall anything. The fix takes two minutes and a single Terminal command.

Fix it: Delete the corrupted .DS_Store file

Open Terminal from Applications > Utilities.
Type this and press Return (replace 'FolderName' with the actual folder that's breaking):
```
cd ~/Desktop/FolderName
```
Now run this command to remove that hidden .DS_Store file:
```
rm .DS_Store
```
Restart the Finder so it rebuilds the file clean:
```
killall Finder
```

That's it. The next time you open that folder or eject the drive, it should work. If the error was on an external drive, run the same commands but with the drive's path — like cd /Volumes/MyDrive instead of the Desktop folder.

Still stuck? Try resetting Finder preferences

If Terminal didn't cut it (maybe the error is system-wide), reset the Finder's preference file. This clears out corrupted settings that cause the 'operation can't be completed' message across all folders. Steps:

Quit Finder by right-clicking its icon in the Dock and choosing Quit. If it won't quit, hold Option and right-click — you'll see Force Quit.
In the Go menu of Finder, choose Go to Folder and paste this path:
```
~/Library/Preferences/
```
Look for the file com.apple.finder.plist and move it to the Trash.
Restart Finder — either from the Apple menu (Force Quit > Finder > Relaunch) or by typing killall Finder in Terminal.

macOS will create a fresh preference file next time you open a folder. This fix has saved me dozens of times on customer Macs with that exact -36 error.

When it's a disk issue

If those two steps don't help, the problem might be deeper — a corrupted directory structure on the drive itself. Open Disk Utility (from Applications > Utilities), select the drive, and click First Aid. Let it run. I've seen this fix a 'can't complete operation' error on an iMac that had a failing SATA cable, but that's rare. Most of the time, it's just the .DS_Store file.

What if the error shows up when saving files?

That's usually a permissions issue on the destination folder. Right-click the folder, choose Get Info, and check the Sharing & Permissions section at the bottom. Make sure your user account has Read & Write access. If it says Read only, click the lock icon, enter your password, and change it. Then hit the gear icon and select Apply to enclosed items.

One last thing to check

If none of this works and the error keeps appearing — especially on a network drive or cloud folder — try rebooting your Mac in Safe Mode. That forces a directory check and clears system caches. On Apple Silicon Macs: shut down, hold the power button until you see Loading startup options, then hold Shift and click Continue in Safe Mode. On Intel Macs: restart and hold the Shift key immediately. Once in Safe Mode, try the operation again. If it works there, you've got a third-party Finder extension causing chaos — check your Finder sidebar for things like Dropbox or OneDrive extensions and disable them one by one.

Most people get fixed at step 1. If you're still seeing the error, drop me a comment below with the exact error code and what you were doing — I'll help you hunt it down.