You're dragging a folder from your SD card to your desktop, and then it happens. That gray box pops up. "The Finder can’t complete the operation because some data in 'File Name' can’t be read or written. (Error code -36)". It's annoying. Actually, it's worse than annoying because it feels like your files are held hostage by a ghost in the machine.
Most people think their drive is dying when they see finder error code 36. I've seen users panic and assume they need a $2,000 data recovery service. Usually, you don't. This specific error is almost always a communication breakdown between the macOS file system (APFS or HFS+) and an older Windows-centric format like FAT32 or exFAT.
It’s a "dot file" problem.
Why your Mac is tripping over invisible files
MacOS creates hidden files that start with a "._" prefix. These tiny companions store metadata, like custom icons or window positions. They are basically the Mac's way of remembering how you like your folders to look. But when you move these files to a drive formatted for Windows, the destination doesn't know what to do with them.
The finder error code 36 occurs when the Mac tries to read these hidden metadata files and hits a snag. It's essentially a "lost in translation" moment. Imagine trying to explain the concept of "schadenfreude" to someone who doesn't speak a word of German; eventually, someone just gives up and stops talking. That’s your Finder. It just stops.
The Dot_Clean fix is your best friend
There is a specific command built into your Mac designed for this exact headache. It’s called dot_clean. I'm surprised how many "Genius Bar" techs don't lead with this. You don't need to download anything. You just need the Terminal.
Open your Terminal (Command + Space, type Terminal). Now, type dot_clean followed by a single space. Don't hit enter yet. Grab the folder or the entire external drive icon that’s giving you grief and drag it right into the Terminal window. This will automatically paste the file path. It'll look something like dot_clean /Volumes/USB_DRIVE. Hit Enter.
The Terminal won't give you a "Success!" message. It'll just jump to a new line. That’s good. It means it merged those pesky hidden files with the actual data files. Try copying again. It usually works instantly.
When the hardware is actually the problem
Sometimes it isn't just metadata. I've had cases where a cheap USB-C hub was the culprit. If the connection flickers for even a millisecond during a write operation, macOS throws a -36 error because the "handshake" between the drive and the OS was broken.
- Try a different port. Seriously.
- If you're using a dongle, plug the drive directly into the Mac if possible.
- Check the cable. If it's a fraying lightning cable or a $2 gas station USB-C wire, throw it away.
Low voltage can also cause this. If you have a massive 12TB external hard drive that doesn't have its own power power supply, your MacBook's port might not be pushing enough juice to keep the platter spinning at a consistent rate during heavy transfers. This leads to read/write failures.
Formatting: The Nuclear Option
If dot_clean failed and your cables are fine, the drive's directory structure might be corrupted. This happens a lot if you pull a USB stick out without "ejecting" it properly. We’ve all done it. We all regret it when the finder error code 36 shows up.
First, try First Aid. Open Disk Utility. Select your drive. Click "First Aid" at the top. MacOS will try to stitch the file system back together.
If First Aid says it can't repair the drive, you're looking at a reformat. You’ll lose everything on that specific drive, so copy what you can save to your cloud storage or internal SSD first. When you reformat, choose APFS if you only use Macs. If you need to jump between Windows and Mac, use exFAT, but make sure the "Scheme" is set to GUID Partition Map. Using the older MBR (Master Boot Record) scheme on modern high-capacity drives is a recipe for error codes.
Misconceptions about "Corrupt" Data
A common myth is that error -36 means your photos or videos are gone forever. That’s rarely the case. The "data" isn't usually corrupt; the "map" to the data is just smudged. If you're desperate and the Finder keeps failing, try using the Terminal to move files instead of the GUI.
Type cp -R (that's cp, space, -R, space), then drag the source folder, then drag the destination folder. The Terminal is much more resilient than the Finder's visual interface. It will often push through minor metadata errors that would cause the Finder to commit digital hara-kiri.
Specific software conflicts to watch for
I once spent three hours troubleshooting a -36 error only to realize an antivirus program was "locking" files as the Mac tried to move them. The Finder tried to read, the Antivirus said "Wait, I'm scanning!", and the Finder timed out.
- Turn off real-time scanning temporarily.
- Close Dropbox or Google Drive sync.
- Make sure no other app (like Final Cut Pro or Photoshop) is trying to access the files at the same time.
It's all about file locking. If two processes are fighting over the same bit of data, the operating system eventually throws its hands up and displays that error code.
Deep Dive: The role of the DS_Store
You might see people talking about .DS_Store files. These are related but slightly different. While dot_clean handles the ._ files, sometimes a corrupt .DS_Store file prevents a folder from being opened or moved. These files store your folder view settings (like whether you use icons or a list).
If a specific folder is the only one acting up, you can try deleting the hidden DS_Store file inside it. In Terminal, type cd followed by the folder path. Then type rm .DS_Store. Your folder will reset to the default view, but the transfer block might vanish.
Summary of Actionable Steps
First, try the dot_clean command in Terminal as it's the most effective non-destructive fix. If the error persists, swap your hardware—cables, hubs, and ports—to rule out a physical power or data drop. Run Disk Utility First Aid to check for logical errors in the drive's volume header. For users moving data to non-Apple drives, ensure the drive is formatted as exFAT with a GUID Partition Map to minimize metadata friction. If all else fails, bypass the Finder entirely and use the cp or rsync commands in the Terminal to force the data transfer. Most of the time, the data is perfectly safe; the system just needs a clearer path to move it.
💡 You might also like: The iPhone 16 Ultramarine Color: Is It Actually Blue or Purple?
---