How Do You Troubleshoot “The Finder Can’t Complete the Operation” Error -36?

When macOS shows “The Finder can’t complete the operation because some data in [file name] can’t be read or written. Error code -36”, it usually appears during a copy, move, delete, or transfer operation. The message is frustrating because it does not always identify the exact cause, and it can interrupt routine work with external drives, network shares, memory cards, or even local folders. In most cases, Error -36 is linked to unreadable metadata, file system inconsistencies, damaged files, permission issues, or problems with the destination storage device.

TLDR: Error -36 is commonly caused by hidden macOS metadata files, disk errors, file corruption, or trouble with external and network volumes. Start by retrying the operation with a smaller group of files, then use dot_clean in Terminal if the issue involves AppleDouble metadata files. If that does not work, check permissions, repair the disk with Disk Utility, test another destination, and inspect the storage device for failure. Avoid forcing repeated transfers if the source drive may be damaged, because that can worsen data loss.

What Error -36 Means in Finder

Error -36 is an I/O error, meaning macOS encountered a problem while reading from or writing to a file or storage location. Finder is only reporting that the operation failed; it is not necessarily the source of the problem. The underlying issue may come from the file itself, the source disk, the destination disk, a USB cable, incompatible formatting, network instability, or file metadata that Finder cannot process correctly.

This error is especially common when copying files between macOS and non Apple file systems, such as FAT32, exFAT, or certain network shares. It can also appear when transferring old folders that contain hidden files beginning with ._. These are AppleDouble files, used to store metadata such as resource forks and Finder information when the destination file system does not support native macOS metadata.

Start With Basic Isolation

Before changing settings or running commands, determine whether the problem is caused by one file, one folder, one disk, or the entire system. This step saves time and reduces the chance of accidentally damaging data.

• Try copying one file at a time. If one specific file fails, it may be corrupt or have problematic metadata.
• Copy the same file to a different location. Use your Desktop or Documents folder as a test destination.
• Try a different cable or port. For external drives, a failing cable or USB hub can cause read and write interruptions.
• Restart the Mac. This clears temporary Finder and mounting issues.
• Check available space. Make sure the destination has more free space than the total size of the data being copied.

If the same file fails everywhere, focus on the source file or source disk. If every file fails only when copied to one destination, the issue is more likely with the destination drive, file system, or permissions.

Use dot_clean to Fix AppleDouble Metadata Problems

One of the most reliable fixes for Error -36 is the Terminal command dot_clean. This command merges or removes problematic AppleDouble metadata files, particularly files that begin with ._. These hidden files are often harmless, but they can trigger Error -36 when Finder tries to copy folders to or from external drives or older storage formats.

To use it, follow these steps carefully:

1. Open Terminal from Applications > Utilities.
2. Type dot_clean followed by a space.
3. Drag the problem folder into the Terminal window. This automatically inserts the correct path.
4. Press Return.
5. Try the Finder copy or move operation again.

For example, the command may look like this:

dot_clean /Users/yourname/Desktop/ProblemFolder

If the error occurs when copying an entire external drive folder, run dot_clean on the folder that contains the failing files, not necessarily the whole disk. This keeps the operation targeted and easier to manage.

Check Disk Health With Disk Utility

If dot_clean does not solve the issue, the next step is to check the relevant drive with Disk Utility. File system corruption can prevent Finder from reading or writing data correctly. This applies to internal drives, USB drives, SD cards, and external SSDs or hard drives.

Use the following process:

1. Open Disk Utility from Applications > Utilities.
2. Click View and choose Show All Devices.
3. Select the affected volume in the sidebar.
4. Click First Aid.
5. Allow Disk Utility to check and repair the volume if possible.

If Disk Utility reports errors it cannot repair, do not keep attempting large transfers. Back up whatever data is still readable, then consider reformatting the drive after the backup is complete. If the disk contains important data and appears to be failing physically, consult a qualified data recovery provider before continuing.

Review File and Folder Permissions

Finder may also show Error -36 when your user account cannot properly access a file or write to a destination. This is more likely when files were copied from another Mac, restored from an old backup, downloaded from a network share, or stored on a drive used by multiple systems.

To check permissions:

1. Select the file or folder in Finder.
2. Press Command + I to open Get Info.
3. Expand Sharing & Permissions.
4. Confirm that your user account has Read & Write access.
5. If needed, click the lock icon, authenticate, and adjust permissions.

For folders, you can use the gear or more options menu in the permissions section to apply changes to enclosed items. Use this carefully, especially on system folders or shared project directories. Changing permissions broadly can create new access issues if applied to the wrong location.

Look for Problematic File Names

Some destination volumes and network systems do not handle certain characters or file name lengths well. While macOS is flexible, other file systems may reject names with unusual symbols, trailing spaces, invisible characters, or extremely long paths.

Check for names that contain characters such as :, /, \, *, ?, quotation marks, or control characters. Also look for very deep folder structures, where the full path becomes unusually long. Rename suspicious files and try the transfer again.

This is particularly important when copying from a Mac to Windows formatted disks, NAS devices, camera cards, or shared work folders managed by non macOS systems.

Test a Different Destination Format

The format of the destination drive matters. For example, FAT32 cannot store individual files larger than 4 GB. Although this often produces a clearer error, it can sometimes contribute to confusing transfer failures. exFAT is better for cross platform use, while APFS is preferred for modern Mac only SSDs. Mac OS Extended may be appropriate for older Macs or mechanical drives used with legacy systems.

If the issue occurs on a removable drive, copy the same files to your internal Mac storage first. If that works, the external drive or its file system is probably the cause. Back up the drive, then erase and reformat it in Disk Utility using the most appropriate format for your use case.

Handle Network Shares Differently

Error -36 can occur when copying files to or from SMB shares, NAS devices, office servers, or remote storage mounted in Finder. Network interruption, server side permissions, incompatible metadata handling, and file locking can all trigger the message.

• Reconnect to the share and try again after restarting Finder or the Mac.
• Use smaller batches rather than copying a large directory in one operation.
• Check server permissions and confirm your account can write to the target folder.
• Avoid Wi Fi for large transfers if possible; use Ethernet for stability.
• Compress folders first into a ZIP archive if metadata causes repeated failures.

Compressing a folder can be an effective workaround because Finder transfers one archive file instead of many individual files and hidden metadata entries.

Use Terminal to Copy Files When Finder Fails

If Finder continues to fail but the drive appears healthy, Terminal can sometimes provide more accurate behavior and clearer error messages. The cp command can copy files, while rsync is better for large folders because it can continue around certain errors and report what failed.

A basic rsync command looks like this:

rsync -avh /path/to/source/ /path/to/destination/

Be careful with paths and trailing slashes. If you are not comfortable using Terminal, test with a small folder first or ask an experienced administrator. Terminal commands are powerful and do not always provide the same confirmations as Finder.

When to Suspect File Corruption or Drive Failure

If Error -36 appears repeatedly on the same source drive, especially with slow performance, clicking sounds, disconnections, or files that cannot be previewed, treat the situation seriously. These symptoms can indicate failing storage. Stop unnecessary copying, avoid repair utilities that write aggressively to the disk, and prioritize recovering the most important files first.

For critical business documents, client files, photos, or research data, a professional recovery assessment may be safer than repeated do it yourself attempts. The more a failing drive is used, the greater the risk that recoverable data becomes unrecoverable.

Preventing Error -36 in the Future

Good storage habits reduce the likelihood of seeing this error again. Always eject external drives properly before unplugging them. Keep macOS updated, especially if you rely on network storage or external media. Use reliable cables and avoid unpowered USB hubs for drives that need stable power. Maintain regular backups with Time Machine or another trusted backup system.

For cross platform drives, choose the file system intentionally. Use APFS for modern Mac only SSDs, exFAT for Mac and Windows compatibility, and avoid FAT32 unless you specifically need it for older devices. For important transfers, verify that copied files open correctly before deleting the originals.

Final Practical Checklist

• Restart the Mac and retry the operation with a small group of files.
• Run dot_clean on the folder that triggers the error.
• Check file names, permissions, and available destination space.
• Run First Aid in Disk Utility on the affected drive.
• Test another cable, port, destination folder, or storage device.
• Use rsync or compress the folder if Finder remains unreliable.
• Stop and back up immediately if the drive shows signs of physical failure.

Finder Error -36 is not always a sign of a major problem, but it should not be ignored. A methodical approach usually identifies whether the cause is metadata, permissions, formatting, network instability, or storage damage. Start with the least invasive fixes, protect your data before attempting repairs, and escalate to professional help when the affected drive appears unreliable or contains irreplaceable information.