Few things are as frustrating as being in the middle of a critical file transfer, only to be interrupted by a sudden popup notification. If you are a Mac user, you may have encountered the dreaded Error Code 36. This specific error often appears when moving, copying, or deleting files, effectively grinding your workflow to a halt. In human behavior, one reference differentiates between “error” and “mistake” as follows: An ‘error’ is a deviation from accuracy or a technical failure, whereas a ‘mistake’ is often a result of human misjudgment. When your Mac throws an Error Code 36, it is undeniably an ‘error’—a system-level deviation that prevents your computer from performing its expected tasks accurately.
Understanding Error Code 36 on Mac
At its core, Error Code 36 is an I/O (Input/Output) error.
It occurs when the macOS Finder is unable to read or write data to a file.
Most frequently, this happens during a move or copy operation from a network drive, an external hard drive, or a USB flash drive.
The system encounters an issue, usually involving hidden files that facilitate Finder’s performance, and simply gives up, presenting the user with the notification: “The Finder cannot complete the operation because some data in [filename] could not be read or written.
(Error code -36).”
While the error message seems vague, the cause is often specific: the presence of corrupt or problematic .DS_Store files. These files are hidden system files that macOS creates to store folder attributes, such as icon positioning or the view settings of a folder. Sometimes, these files become corrupted or incompatible with the destination drive, causing the entire transfer process to crash.
Why Does Error Code 36 Happen?
Understanding why this happens can help you prevent it in the future. Beyond corrupt .DS_Store files, other triggers include:
- Permission Issues: You might not have the correct read/write permissions for the source or destination drive.
- Incompatible File Systems: Transferring files between different formats (e.g., Mac OS Extended to exFAT) can sometimes cause conflicts if the system interprets file metadata differently.
- Disk Errors: Your source or destination drive might have underlying bad sectors or file system damage that hasn’t been repaired yet.
- Interrupted Connections: If the external drive is disconnected or experiences a power fluctuation during the transfer, the file operation will fail.
How to Fix Mac Error Code 36: Step-by-Step Solutions
Before assuming your drive is failing, try these proven troubleshooting methods to resolve the issue.
Most users find success within the first two approaches.
Method 1: Using Terminal to Remove .DS_Store Files
Since the issue is frequently caused by hidden .DS_Store files, the most effective fix is to force the system to clear them out. You can do this using the dot_clean command in the macOS Terminal.
- Open Terminal (found in Applications > Utilities).
- Type
dot_cleanfollowed by a single space. Do not press enter yet. - Drag the folder that contains the problematic files directly into the Terminal window. This will automatically populate the file path.
- Press Enter.
- Terminal will process the command, merging the
.DS_Storefiles. Once finished, try the file transfer again.
Method 2: Run First Aid via Disk Utility
If the Terminal command does not work, the issue might be broader than just one folder.
Your drive might have file system errors.
Disk Utility is the built-in tool designed to scan and repair these structural issues.
- Open Disk Utility (found in Applications > Utilities).
- Select the drive causing the issue from the left-hand sidebar.
- Click the First Aid button in the top toolbar.
- Click Run. The system will verify the file system structure and attempt to repair any inconsistencies it finds.
- Once the process is complete, attempt the file transfer operation again.
Method 3: Check Permissions
Sometimes, Error Code 36 is merely a permissions lockout.
If you do not have permission to read the source file or write to the destination, the transfer will fail.
- Right-click on the folder or drive you are trying to copy from.
- Select Get Info.
- Scroll down to Sharing & Permissions at the bottom of the window.
- Click the lock icon to unlock the settings (you may need to enter your admin password).
- Ensure your user account is listed under ‘Name’ and that the ‘Privilege’ is set to Read & Write.
- Click the gear icon (if available) and select ‘Apply to enclosed items’ if you are working with a folder.
When to Seek Professional Help
If you have attempted these solutions and continue to receive Error Code 36, you might be dealing with physical hardware failure.
If you hear clicking noises from your drive or if the disk fails to mount entirely, the issue has transcended software troubleshooting.
In such cases, discontinue use immediately to prevent further data loss and contact a data recovery professional or an authorized Apple service provider.
Conclusion
While Error Code 36 is undoubtedly an annoying hurdle, it is usually a software-based hiccup rather than a sign of a dying computer. By clearing out problematic .DS_Store files using Terminal or utilizing Disk Utility to repair file system issues, most users can resolve this problem in a matter of minutes. Remember that keeping your macOS updated and regularly checking the health of your external drives are the best ways to ensure your data transfers remain smooth and error-free.
Frequently Asked Questions (FAQ)
What does Error Code 36 mean on a Mac?
Error Code 36 is an I/O (Input/Output) error indicating that the macOS Finder cannot read or write data to a specific file, often due to corrupt hidden system files like .DS_Store.
Is it safe to delete .DS_Store files?
Yes, it is perfectly safe. .DS_Store files are generated by macOS to manage folder view settings.
If you delete them, the system will simply regenerate fresh, non-corrupted versions the next time you open the folder.
Can I fix Error 36 without using Terminal?
Yes.
While the Terminal method is often the fastest, you can also try running ‘First Aid’ in Disk Utility or checking folder permissions in the ‘Get Info’ menu to resolve the issue.
Does Error 36 mean my hard drive is failing?
Not necessarily.
It is most often a software or file system metadata issue.
However, if the error persists after troubleshooting and you hear unusual noises from your drive, it could indicate hardware failure.
Written by: Nathan Roberts