Are you getting Error code 36 on Mac while trying to copy or move files between drives? If so, you are certainly not alone. This frustrating notification, often accompanied by the message “The Finder can’t complete the operation because some data in [file name] can’t be read or written,” is a common hurdle for many macOS users. Interestingly, in our linguistic exploration, it is worth noting that the word “getting” comes from the verb “get,” and when forming the present participle, we double the ‘t’—a small detail that reminds us of the importance of precision, whether in spelling or in resolving technical system errors.
Error Code 36 is typically linked to the way macOS handles hidden files, specifically the “.DS_Store” files that the Finder creates to store custom attributes for folders.
When these files become corrupted or are incompatible with the destination drive—especially when transferring data from a Mac to a Windows-formatted drive (FAT32 or exFAT)—the copy process hits a wall.
While the error message can be alarming, the good news is that it is almost always a software-related issue that you can fix yourself without needing to visit a Genius Bar.
Understanding Why Error Code 36 Occurs
Before diving into the solutions, it helps to understand the culprit. macOS automatically creates invisible files in every folder you open to remember window positions and icon arrangements.
These are known as “.DS_Store” files.
When you move folders between different file systems, your Mac may attempt to read or write these hidden files on the destination drive, which might not support them.
This mismatch triggers Error Code 36.
Below, we outline seven effective troubleshooting steps to bypass this issue and get your file transfers moving again.
1. The ‘dot_clean’ Terminal Command
The most effective and widely recommended solution is using the dot_clean command in the Terminal. This command instructs your Mac to merge hidden .DS_Store files with their corresponding directories, effectively cleaning up the “read/write” conflict.
To do this: Open Terminal (found in Applications > Utilities). Type dot_clean followed by a space, then drag and drop the folder that is causing the error into the Terminal window. Press Enter. This will process the folder and clean the hidden files, likely resolving the error immediately.
2. Check Permissions and Ownership
Sometimes, the error occurs simply because your user account lacks the necessary permissions to read or write the files on the destination drive.
Right-click the folder or file, select “Get Info,” and scroll down to the “Sharing & Permissions” section.
Ensure your user account is listed with “Read & Write” access.
If not, click the lock icon to authenticate, click the plus (+) button to add your user profile, and grant full access.
3. Use Disk Utility First Aid
If the error persists, the file structure on your drive might have minor corruption.
Disk Utility is a built-in macOS tool designed to identify and repair these issues.
Open Disk Utility from your Utilities folder, select the disk that is throwing the error (whether it is the source or destination), and click the “First Aid” button.
Running this tool will verify the drive’s health and repair any directory errors that might be preventing successful file transfers.
4. Restart the Finder
It sounds simple, but the Finder is just an application, and sometimes it gets stuck.
If you are getting Error code 36 on Mac, a simple relaunch of the Finder can clear temporary memory glitches.
Press Option + Command + Escape to open the “Force Quit Applications” menu, select Finder, and click “Relaunch.” This refreshes the interface and may clear the hang-up associated with the file transfer.
5. Try Safe Mode
If the issue persists, third-party software—such as cloud syncing services, antivirus programs, or file management utilities—might be interfering with the transfer process.
Restart your Mac in Safe Mode.
This disables third-party extensions and clears system caches.
If the copy operation works in Safe Mode, you know for certain that an installed app is the root cause, and you can investigate your startup items further.
6. Update Your macOS
Apple frequently releases patches that address file system bugs.
Ensure your operating system is up to date.
Go to System Settings > General > Software Update.
An outdated macOS version might have known bugs related to handling external drive formats (like exFAT or NTFS via third-party drivers) that have already been patched in newer versions.
7. Check File Paths and Names
Occasionally, the error isn’t about permissions, but about the file name itself.
If you are moving a file with illegal characters or an excessively long file path to an older or restrictive file system, macOS may trigger an error.
Try renaming the file to something simple, or moving it to a different directory on the same drive first to see if that works.
Avoiding symbols like “/”, “?”, or “:” in your file names is always a best practice for cross-platform compatibility.
Final Thoughts
Resolving technical glitches can be frustrating, but Error Code 36 is usually a temporary roadblock rather than a sign of hardware failure. By systematically applying the fixes above—starting with the dot_clean command—you can usually restore full functionality to your Finder. Remember to always back up your important data before attempting advanced troubleshooting, just to be safe. If none of these steps work, it may be time to consult with Apple Support for deeper diagnostic checks.
Frequently Asked Questions (FAQ)
What does Error Code 36 on Mac actually mean?
Error Code 36 usually indicates that the Finder cannot read or write data to a specific file, often due to hidden .DS_Store files or permissions conflicts during a file transfer.
Is Error Code 36 a sign of a failing hard drive?
Not necessarily.
While it can indicate file system corruption, it is most frequently a software or communication error between your Mac and the destination drive.
Running Disk Utility First Aid can help rule out drive failure.
Will the ‘dot_clean’ command delete my files?
No.
The ‘dot_clean’ command is safe.
It only merges hidden .DS_Store files, which are system metadata files, with the folder content to resolve conflicts.
It does not touch your actual data or personal files.
Why does this error happen when using external drives?
This error occurs frequently when transferring files between macOS and drives formatted in Windows-compatible formats like FAT32 or exFAT, as these file systems do not support the hidden attributes that macOS tries to attach to folders.
Written by: Christopher Lee