In the world of technology, we often face unexpected interruptions that halt our productivity.
When studying human behavior, one reference differentiates between “error” and “mistake” as follows: An ‘error’ is a deviation from accuracy or a technical glitch, whereas a ‘mistake’ is a human misjudgment.
When you encounter Error Code 36 on your Mac, you are clearly dealing with the former—a technical system deviation rather than a mistake you made during file management.
Error Code 36 is one of the most common file transfer issues that Mac users encounter.
It typically manifests when you are trying to copy, move, or delete files between your Mac and an external drive, a network server, or even between folders on your local hard drive.
The system simply reports: “The Finder can’t complete the operation because some data in ‘filename’ can’t be read or written.
(Error code -36).” While the message is cryptic, the problem is solvable.
Understanding Error Code 36 on Mac
At its core, Error Code 36 is an I/O (Input/Output) error.
This means the macOS Finder is struggling to communicate with a specific file or the directory structure where the file resides.
Often, this is not a hardware failure, but rather a file system inconsistency caused by hidden metadata files that macOS creates to manage folders.
When you browse folders on a Mac, the system automatically creates invisible files named .DS_Store. These files store folder metadata, such as icon positioning and window size. If these files become corrupted or incompatible with the destination drive’s file system, the transfer process fails, resulting in the dreaded Error Code 36.
Common Causes of Error Code 36
Understanding why this happens can help you prevent it in the future.
The most common culprits include:
- Corrupted .DS_Store files: As mentioned, these hidden files are often the root cause. If they have incorrect permissions or structural corruption, the Finder stops the operation.
- Incompatible File Systems: Moving files from a Mac-formatted drive (APFS or HFS+) to a Windows-formatted drive (FAT32 or exFAT) can trigger metadata conflicts.
- Permission Issues: If your user account does not have read/write permissions for the specific file or folder, the system will block the transfer.
- Disk Integrity Errors: Sometimes, minor physical or logical sectors on your drive may be damaged, preventing successful read/write operations.
How to Fix Error Code 36 (Step-by-Step)
If you are currently stuck, don’t panic.
You can often resolve this issue using native macOS tools without needing third-party software.
Method 1: Use the ‘dot_clean’ Command
The most effective way to clear out problematic .DS_Store files is by using the Terminal. This command merges the attributes of the corrupted files into the main directory, effectively fixing the issue.
- Open Terminal (found in Applications > Utilities).
- Type
dot_cleanfollowed by a space. - Drag the folder containing the files causing the error into the Terminal window. The path will appear automatically.
- Press Enter.
- Once the process completes, try moving your files again.
Method 2: Run First Aid via Disk Utility
If dot_clean does not solve the problem, your disk might have logical errors. Use Disk Utility to repair them.
- Open Disk Utility.
- Select the drive causing the issue from the sidebar.
- Click the First Aid button at the top of the window.
- Click Run to scan and repair any file system discrepancies.
Preventing Future File Transfer Errors
To avoid seeing Error Code 36 again, try to maintain clean file systems. If you frequently transfer files between macOS and Windows, consider formatting your external drives as exFAT, as it is highly compatible with both operating systems and less prone to the metadata corruption that triggers this specific error. Additionally, keep your macOS updated to ensure you have the latest drivers and file system improvements provided by Apple.
Frequently Asked Questions (FAQ)
Is Error Code 36 dangerous for my Mac?
Generally, no.
It is a logical error related to file metadata, not physical hardware damage, so your Mac and data are likely safe.
Does this error mean my hard drive is failing?
Usually, it indicates file system corruption or metadata conflicts.
However, if the error persists after trying the fixes, you should run a hardware diagnostic to rule out drive failure.
Can I simply ignore Error Code 36?
You cannot ignore it because it prevents the specific file transfer from completing.
You must resolve the file system conflict to move or copy those files successfully.
Written by: Emma Johnson