macOS Finder Error Code -36: File I/O & AppleDouble (._*) Copy Failure
Apple Carbon/POSIX ioErr (-36) occurs when Finder fails reading/writing hidden ._* AppleDouble resource forks or damaged sectors on exFAT/FAT32 drives and SMB shares—fix with Terminal dot_clean, Disk Utility First Aid, or ditto.
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).
- Safe to Operate?
- Yes (Short Term)
- DIY Difficulty
- Easy (Basic Tools)
- System
- Finder File I/O & Disk Storage
- Professional Repair
- $120 – $350
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.
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_Storeor._*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)
Technical Thresholds & Specifications
| Parameter / Condition | Factory Spec / Threshold |
|---|---|
| Apple Carbon / POSIX Error Meaning Triggered when Finder fails reading/writing file data or resource forks | ioErr (-36) Input/Output Read-Write Error |
| Primary AppleDouble Sidecar Fix Merges conflicting hidden ._* files on exFAT, FAT32 & SMB shares | dot_clean /path/to/folder |
| Terminal Robust Copy Fallback Handles resource forks reliably and logs exact failing file path | ditto -rsrc <source> <destination> |
| Directory Verification Tool Repair both volume and parent physical container after dirty ejects | Disk Utility (Show All Devices -> First Aid) |
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
Diagnostic Checks Before Replacing Parts
Verify the exact faulty component before ordering replacements.
- 1Check whether the destination or source volume uses exFAT / FAT32 or SMB (
Get Infoon drive in Finder), and verify read/write privileges under Sharing & Permissions plus any physical SD card write-protect tab. - 2Test running
dot_cleanin Terminal (dot_clean+ drag the source folder + Return): if the copy succeeds immediately afterward, hidden._*AppleDouble files caused the error rather than drive death. - 3If
dot_cleanstill triggers-36, open Disk Utility > View > Show All Devices, run First Aid on both the volume and its parent physical disk, or copy viadittoin Terminal to spot which specific file fails I/O.
Interactive Symptom Triage
Answer 3 quick checks to narrow down the faulty component before spending money on parts.
Are you copying to/from an exFAT, FAT32, or SMB share, and does running dot_clean <folder> fix the transfer right away?
Step-by-Step Troubleshooting & Fix
Tools & Parts Reference
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- 1Open Terminal (
Applications > Utilities > Terminal), typedot_clean(note the trailing space), drag the source folder onto the Terminal window, press Return, and retry your Finder copy/move. - 2Verify 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.
- 3Open 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.
- 4If 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 ifdittoreports genuine hardware read errors on specific files.
Estimated Repair Cost Benchmark
Typical DIY parts and certified technician labor ranges. Select a currency below.
| Repair Path | USD |
|---|---|
| DIY Parts Only | $0 – $80 |
| Professional Repair (Parts + Labor) | $120 – $350 |
Recommended Diagnostic Tools & Replacement Parts
Check OEM specifications and compatible tools for this repair.
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.
Related Searches & Questions
Verified Official & Engineering References
Related Fault Codes
Tech & OS →Windows Error Code 0x80070005 (E_ACCESSDENIED)
Windows Update, Microsoft Store, OneDrive folder backup, activation, or an installer hit `E_ACCESSDENIED`—blocking access to required system files, registry hives, or DCOM permissions (`SELF`).
Windows Blue Screen Stop Code IRQL_NOT_LESS_OR_EQUAL (0x0000000A)
Windows Blue Screen Stop Code MEMORY_MANAGEMENT (0x0000001A)
Windows Update Error 0x80070643 (ERROR_INSTALL_FAILURE / KB5034441)
PS5 Error CE-108262-9: System Software or Application Data Read Failure