'The Operation Can't Be Completed' Error on Mac? Here's the Fix

You drag a folder to an external drive and Finder stops cold: “The operation can’t be completed because an unexpected error occurred (error code -36).” Or you try to delete an item from the Trash: “The operation can’t be completed because the item is in use.” Same opening line, very different problems hiding behind it.

This is one of macOS’s vaguest errors, but the number after the parenthesis tells you exactly what went wrong if you know how to read it.

Decoding the error codes

Finder reports the underlying POSIX or BSD error number. The common ones:

• -36 — I/O error reading or writing a file. Usually a corrupt source, bad sector, or filesystem mismatch.
• -43 — File or folder not found. The path resolved to nothing.
• -50 — Parameter error. Filename invalid for the destination filesystem (illegal characters, name too long).
• -41 — Resource not found.
• -120 — Folder not found.
• -1407 — Item busy or in use.
• -1309 — File too large for the destination filesystem (FAT32 caps at 4 GB per file).
• -8003 — Trash item with locked permissions.
• 8076 — Permission denied on the destination.

Knowing the number changes which fix to try first.

Quick fixes that work for most cases

Run these in order. Most “operation can’t be completed” errors stop here.

1. Restart Finder. Hold Option, right-click the Finder icon in the Dock, choose Relaunch. Clears stuck file handles.
2. Restart the Mac. Releases any kernel-level locks on stuck files.
3. Try a different path. Move the file to your Desktop first, then to the destination. If the two-hop works, the issue was a path-resolution glitch.
4. Check the destination’s filesystem. Get Info on the destination drive. APFS and HFS+ accept anything. ExFAT mostly works. FAT32 rejects files larger than 4 GB and choke on filenames with : or trailing dots.
5. Use Terminal to copy. cp -p ~/source.dmg /Volumes/External/dest.dmg bypasses Finder’s metadata staging that triggers many -36 errors.

Free up disk in one clickMany errors stem from a full startup disk. Sweep finds gigs of cruft fast. Get Sweep free →

Fixing error -36 specifically

Code -36 is the most common. It means Finder hit a read or write error somewhere mid-copy. Causes ranked by frequency:

1. Corrupt source file. Try copying just that file alone. If it fails, the original is bad.
2. Bad sector on either drive. Run Disk Utility → First Aid on the source and destination. If First Aid reports errors, the drive is failing.
3. Hidden .DS_Store files mismatched between filesystems. Use Terminal: dot_clean -m /Volumes/SourceDrive then retry.
4. macOS metadata that the destination can’t store. ExFAT and FAT32 don’t support extended attributes. Try cp -X source dest to skip extended attributes.
5. Network drive timing out. SMB shares mid-copy occasionally drop. Increase timeout via defaults write com.apple.NetworkBrowser BrowseAllInterfaces 1 or copy in smaller batches.

If dot_clean fixes it, you have a metadata mismatch from a previous incomplete copy. Run it preemptively next time.

Fixing error -50 (parameter error)

This almost always means the filename has characters that don’t survive the destination filesystem.

• Forbidden on FAT32/ExFAT: : \ / ? * " < > |
• Filenames longer than 255 bytes (UTF-8) fail on most filesystems.
• A trailing space or period in the name fails on ExFAT.
• Files with no extension can fail on some Windows-formatted drives.

Fix: rename the file to ASCII-only characters and try again. If you can’t pinpoint the problem file in a folder copy, copy in batches to bisect.

Fixing error -1407 (item in use)

Finder thinks something is still holding the file open. Even after you “quit” the app.

1. Open Activity Monitor → search the filename. Quit any process that has it open.
2. In Terminal: lsof | grep "filename" lists every process touching the file. Kill them: kill -9 <PID>.
3. Spotlight indexing is a frequent culprit — pause it with sudo mdutil -i off / , do your operation, then re-enable with sudo mdutil -i on /.
4. Restart and try again. The handle dies with the process.

Trash that won’t empty

You drag an item to Trash and it refuses to empty: “The operation can’t be completed because the item is in use” or “…because the item is locked.”

Try in order:

1. Restart, then empty Trash. Releases file handles.
2. Hold Option while choosing Empty Trash. Skips the “are you sure” and force-deletes.
3. Get Info → uncheck Locked on the offending item.
4. Terminal nuke: sudo rm -rf ~/.Trash/* — only do this if you’re certain about what’s in there. There is no recovery.

If a file from an external drive is stuck in Trash, eject the drive properly first; the Trash references can hold even after the drive disconnects.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

When the destination filesystem is the problem

If you need to copy a 10 GB file to a thumb drive that says “MS-DOS (FAT32)” in Disk Utility, it will never work. Reformat the drive (back up its contents first):

1. Disk Utility → select the drive (the gray external partition, not the volume).
2. Erase → Format: ExFAT for cross-platform, APFS for Mac-only.
3. Scheme: GUID Partition Map.
4. Erase.

ExFAT works on Windows and Mac but doesn’t support journaling or permissions in a useful way. APFS is faster and more reliable but Mac-only.

Permissions errors

Code -8003 or “you don’t have permission” with the operation-can’t-be-completed wrapper means the destination’s permissions don’t allow your user to write.

1. Get Info on the destination folder → Sharing & Permissions → unlock with admin password → set your user to Read & Write.
2. For external drives: Get Info → check “Ignore ownership on this volume.” This is the right answer for backup drives that move between computers.
3. For system folders, you generally can’t and shouldn’t fix them — write somewhere else.

When it’s the hardware

If First Aid in Disk Utility reports issues twice on the same drive, that drive is dying. Other signs:

• The error appears randomly with files that previously copied fine.
• You hear clicking from a spinning drive (that’s mechanical failure).
• SMART status in Disk Utility (View → Show All Devices → click the physical device) reads “Failing” or “Verified” with errors.

Back up immediately and replace the drive. No software fix will keep ahead of failing storage. For SSDs that come up “Verified” but show repeated errors, the SSD’s controller may be remapping bad blocks faster than it can keep up — same outcome, different mechanism.

Prevent the error from coming back

• Eject external drives properly with the eject button or diskutil eject. Yanking a USB drive corrupts metadata.
• Run Disk Utility First Aid on external drives monthly.
• Don’t let your startup disk fall below 15% free — APFS needs scratch space and starts throwing errors when it can’t get it.
• Format new drives ExFAT or APFS instead of FAT32.

The “operation can’t be completed” error is a generic Finder wrapper — the real story is in the parenthesized number. Translate it, and the fix is usually obvious.