# macOS -36: macOS Finder Error Code -36: File I/O & AppleDouble (`._*`) Copy Failure

> **Quick Answer:** macOS **Error Code -36** (`ioErr` — Input/Output error) pops up when Finder cannot read or write part of a file during copy, move, or delete operations—most frequently involving **exFAT / FAT32 USB drives**, **SD cards**, or **SMB network shares**. Before assuming drive failure, open **Terminal** and run **`dot_clean /path/to/folder`** (type `dot_clean `, drag the affected folder/volume into Terminal, and press Return) to merge conflicting hidden **`._*` AppleDouble** sidecar files back cleanly. If `-36` continues, run **Disk Utility > View > Show All Devices > First Aid**, check read/write permissions + SD lock tabs, or copy files cleanly using **`ditto -rsrc`** ($0 DIY; ~$120–$350 only if a failing drive needs data recovery or SSD replacement).

- **URL:** https://faultcodes.org/software/macos-error-36
- **Category:** Windows, Gaming & Tech
- **Brand / Standard:** macOS
- **System Area:** Finder File I/O & Disk Storage
- **Severity:** Moderate — Plan Repair
- **Safe to Operate?:** Yes (Short Term)
- **DIY Difficulty:** Easy (Basic Tools)
- **Updated:** 2026-11-22T00:00:00Z

## What This Fault Code Means
To preserve Finder metadata, tags, and resource forks on non-Apple filesystems like **exFAT / FAT32** or network **SMB** shares, macOS creates tiny paired **`._filename`** (AppleDouble) and `.DS_Store` helper files. When an AppleDouble header gets truncated during an interrupted eject, SMB permission quirk, or cross-platform Windows edit, Finder aborts the entire folder copy with `Error code -36` (`ioErr`)—even though the main data file is perfectly healthy.

## Technical Thresholds & Specifications
| Parameter / Condition | Factory Spec / Threshold | Note |
| --- | --- | --- |
| Apple Carbon / POSIX Error Meaning | ioErr (-36) Input/Output Read-Write Error | Triggered when Finder fails reading/writing file data or resource forks |
| Primary AppleDouble Sidecar Fix | dot_clean /path/to/folder | Merges conflicting hidden ._* files on exFAT, FAT32 & SMB shares |
| Terminal Robust Copy Fallback | ditto -rsrc <source> <destination> | Handles resource forks reliably and logs exact failing file path |
| Directory Verification Tool | Disk Utility (Show All Devices -> First Aid) | Repair both volume and parent physical container after dirty ejects |

## Commonly Affected Models & Service Bulletins
- MacBook Air & MacBook Pro (Apple Silicon M1/M2/M3/M4 & Intel) on macOS Ventura / Sonoma / Sequoia
- iMac, Mac mini & Mac Studio copying files to exFAT / FAT32 USB drives or SD cards
- macOS Workstations transferring files across Synology / QNAP / Windows SMB shares

## Common Symptoms
- Finder aborts file transfer mid-copy with *"The Finder can't complete the operation because some data in ... can't be read or written. (Error code -36)"*
- Transfers succeed to internal APFS drives yet fail consistently onto **exFAT / FAT32 external SSDs** or **NAS SMB folders**
- Folder deletion or renaming stalls on `.DS_Store` or `._*` sidecar entries

## Most Likely Root Causes
- Corrupted or mismatched hidden **`._*` (AppleDouble)** resource-fork files and `.DS_Store` sidecars on exFAT/FAT32 or SMB volumes
- Minor directory corruption from unplugging an external USB/SD drive without clicking Eject
- Mixed **Read-Only** POSIX/ACL permissions on an SMB network share or engaged SD card physical lock switch
- Failing NAND/bad hardware sectors on an aging USB stick, external HDD, or SD card (`genuine hardware I/O error`)

## Tools & Parts Reference
- macOS Terminal (`dot_clean` and `ditto -rsrc` built-in utilities)
- macOS Disk Utility (Show All Devices -> First Aid repair)
- Finder Get Info (`Sharing & Permissions`) / replacement USB-SSD if bad sectors appear

## Step-by-Step Troubleshooting & Fix
1. Open **Terminal** (`Applications > Utilities > Terminal`), type `dot_clean ` (note the trailing space), drag the source folder onto the Terminal window, press **Return**, and retry your Finder copy/move.
2. Verify **Read & Write** access on both source and destination under Finder **Get Info -> Sharing & Permissions**, confirm external SD cards aren't locked, and unmount/remount SMB shares cleanly.
3. Open **Disk Utility**, enable **View > Show All Devices**, select the affected external volume (and parent container), and click **First Aid > Run** to repair exFAT/APFS directory trees.
4. If Finder still trips on stubborn folders, transfer safely via Terminal with `ditto -rsrc <source> <destination>`, and back up immediately + retire the external drive/SD card if `ditto` reports genuine hardware read errors on specific files.

## Estimated Repair Cost Benchmark
| Currency | DIY Parts Only | Professional Repair (Parts + Labor) |
| --- | --- | --- |
| USD | $0–$80 | $120–$350 |
| GBP | £0–£65 | £95–£280 |
| CAD | CA$0–CA$105 | CA$155–CA$450 |
| EUR | €0–€75 | €110–€320 |
| CHF | CHF 0–CHF 85 | CHF 140–CHF 380 |

## Frequently Asked Questions
### Is the Terminal dot_clean command safe for my files?
Yes—`dot_clean` only merges macOS's hidden `._filename` metadata files with their matching native files (or tidies orphaned sidecar metadata) and does not erase user documents, photos, or videos.

### Why does Error -36 happen far more often on exFAT drives than Mac-formatted APFS drives?
APFS stores resource forks and extended attributes natively inside a single object, whereas exFAT and SMB shares require separate hidden `._*` AppleDouble files that easily lose sync when accessed by Windows PCs or unplugged unexpectedly.


## Verified Official & Engineering References
- [Apple Support: Finder Error Codes & Mac File Issues](https://support.apple.com/en-us/102611) (Official Support)
- [Apple Disk Utility User Guide: Repair a Storage Device](https://support.apple.com/guide/disk-utility/repair-a-storage-device-dskutl1040/mac) (Official Support)
