Error Code 36 Mac? Fix Finder Copy & Move Issues Now

You’re copying files on your Mac. Everything looks normal. Then the Finder stops cold and delivers this message:

“The Finder can’t complete the operation because some data in [filename] can’t be read or written. (Error code -36)”

Mac error code -36 is one of the most commonly encountered file system errors on macOS — and one of the most persistently misunderstood. It appears during file copying, moving, or transferring operations. It interrupts workflow without warning. And Apple’s own error message provides almost no actionable guidance.

The good news is that error code 36 on Mac has well-documented causes and a structured hierarchy of proven fixes. This guide covers every one of them — from the quick Terminal command that resolves the majority of cases in under two minutes, to advanced disk repair procedures for more serious underlying issues.

Whether you’re hitting Mac error code -36 while copying files to an external drive, transferring data across a network, moving files between different file system formats, or working with drives that contain legacy file structures, the solution is here.

What Is Mac Error Code -36?

Mac error code -36 is a file system I/O error — specifically identified in Apple’s legacy error code documentation as ioErr, which stands for Input/Output Error.

The full error message typically reads:

“The Finder can’t complete the operation because some data in [filename] can’t be read or written. (Error code -36)”

In plain terms, this means the macOS Finder attempted to read data from a source location or write data to a destination location — and that operation failed at the hardware or file system level.

The negative sign in -36 is significant. In macOS error code nomenclature, negative error codes originate from the core operating system layer — they’re not application-level errors. Error code -36 specifically indicates that the system encountered an I/O failure during a fundamental read or write operation.

This distinguishes it from errors like -43 (file not found) or -50 (parameter error), which indicate different categories of failure. Error -36 always points to a data transfer or storage access problem.

Understanding this distinction is important because it tells you exactly where to look: the problem lies somewhere between the source data and the destination storage — in the files themselves, the drive hardware, the file system format, or the connection pathway between them.

The Technical Definition — What ioErr Actually Means in macOS

For readers who want to understand the mechanics behind Mac error code -36, here’s the technical foundation.

macOS inherits its core error code structure from the original Mac OS and its Carbon framework. The ioErr (-36) code is defined in Apple’s OSStatus error table as a fundamental Input/Output error at the system call level.

When macOS attempts a file operation, it goes through several layers:

1. Application layer — Finder or a third-party application requests the operation
2. File system layer — macOS’s file system driver (APFS, HFS+, or a third-party format driver) handles the request
3. I/O Kit layer — Apple’s hardware abstraction layer manages the physical read/write operation
4. Hardware layer — The physical drive executes the read or write

Error -36 can originate at any of layers 2, 3, or 4. When it bubbles up to the application layer, Finder reports it as error code -36 regardless of which specific sublayer failed.

This is why the error is so versatile in its causes — it’s a high-level symptom that can have multiple specific origins. The diagnostic process essentially works backward through these layers to identify where the failure originated.

In modern macOS versions — including macOS Ventura and Sonoma — the underlying error code remains the same even though the file system has largely transitioned from HFS+ to APFS. Error -36 persists because it’s defined at a layer below the file system.

What Causes Mac Error Code 36?

Every case of Mac error code -36 traces back to one of the following root causes. Understanding them is essential for applying the right fix efficiently.

Dot Underscore Resource Fork Files

This is the most common cause — and the one most easily fixed.

macOS uses a dual-fork file structure that maintains both a data fork (the actual file content) and a resource fork (metadata, extended attributes). When files are stored on non-Mac file systems (FAT32, exFAT, NTFS, network shares), macOS creates hidden companion files with names starting with “._” (dot underscore) to store the resource fork data separately.

These dot underscore files are invisible on Mac but can become corrupted, mismatched, or incompatible with certain file systems. When Finder attempts to copy them alongside the parent file, the operation fails with error -36.

File System Format Incompatibility

Mac error code -36 frequently occurs when copying between drives formatted in incompatible file systems:

• Copying from APFS to FAT32
• Copying from HFS+ to exFAT
• Copying to or from NTFS drives (which macOS can read but not write natively)
• Copying from a Mac-formatted drive to a network drive with a different file system

Each file system handles metadata, extended attributes, and special characters in file names differently. These incompatibilities can trigger I/O errors during transfer. This type of cross-format transfer failure is not unique to macOS — similar issues appear in other platforms when file systems or network layers fail to properly interpret data during transfer.

A closely related real-world example is:
“Failed to Connect to Steam Error Code 211 — Complete Fix,” which breaks down how connection and data transfer mismatches between client and server can trigger similar interruption-style errors.

Corrupted Source Files

If the source file itself contains corrupted data — bad blocks on disk, incomplete writes from a previous operation, or damage from an improper ejection — macOS will fail to read that data and report error -36.

Bad Sectors on the Drive

Physical bad sectors on a hard drive or failing flash cells on an SSD can cause read failures that produce error -36. This is the most serious underlying cause — it indicates hardware deterioration rather than a software or configuration issue.

Faulty Cable or Connection

A damaged USB, Thunderbolt, or other interface cable can cause intermittent data transfer failures. Even a slightly loose connection can create the kind of read/write inconsistency that produces error -36 during file operations.

File Name Special Characters

File names containing certain special characters — colons, forward slashes, or characters from non-standard character sets — can cause failures when those files are copied to file systems that don’t support those characters.

Network Drive Issues

Copying files to or from network-attached storage (NAS) or SMB shares can produce error -36 when network interruptions, permission mismatches, or SMB protocol incompatibilities create I/O failures. Network-based file transfers are especially sensitive to protocol mismatches, authentication issues, and session instability — all of which can trigger I/O-style errors similar to macOS error -36.

A comparable troubleshooting breakdown can be found in:
“Steam Error Code 16 Quick Fixes — Login & Network Problem Solutions” shows how session failures and unstable network routing can break otherwise valid data connections.

macOS System File Corruption

In rare cases, macOS system file corruption affecting the file system drivers or I/O Kit can produce persistent error -36 across multiple operations. This typically requires a macOS reinstall to resolve.

Quick Diagnostic Checklist

Before working through the full fix list, run these quick diagnostics:

• Does the error appear in one specific file, or all files in a folder?
• Does the error appear when copying to all destinations, or just one specific drive?
• Are you copying between different file system formats?
• Does the error appear with both internal and external drives as the destination?
• Did the error start after an improper drive ejection or system crash?
• Does the error appear consistently or intermittently?
• Is the source drive or destination drive showing any warnings in Disk Utility?

The single most useful diagnostic: Try copying a single, simple file (a plain text document) to the same destination. If that succeeds but the original operation fails, the issue is with specific files — likely resource fork or dot underscore file related. If even a simple file copy fails, the issue is with the drive, the connection, or the file system.

Fix 1: The dot_clean Terminal Command — The Fastest and Most Effective Fix

This is the fix that resolves Mac error code -36 for the majority of users, and it takes less than two minutes.

The dot_clean command is a built-in macOS Terminal utility specifically designed to merge or remove the dot underscore resource fork files that cause error -36. Running it on the source folder before copying eliminates the incompatible hidden files that trigger the error.

Step-by-step process:

1. Open Terminal — press Cmd + Space, type “Terminal”, press Enter
   

Type the following command, but do NOT press Enter yet:

dot_clean

2.  (Include a space after dot_clean)
   
3. Open Finder and navigate to the source folder — the folder containing the files you’re trying to copy
   
4. Drag the source folder from Finder directly into the Terminal window. This automatically inserts the correct folder path
   

Your Terminal command should now look like:

dot_clean /path/to/your/folder

6. Press Enter and wait for the command to complete (no output means success)
   
7. Attempt your file copy operation again
   

What dot_clean actually does:

dot_clean scans the specified directory and merges dot underscore resource fork files with their parent files where possible, and removes orphaned dot underscore files that have no corresponding parent. This eliminates the corrupted or incompatible resource fork data that was causing Finder to throw error -36.

Variations for specific situations:

For recursive operation across all subfolders:

dot_clean -m /path/to/your/folder

The -m flag merges all dot underscore files rather than just removing them — useful when you need to preserve resource fork data.

For a specific drive volume:

dot_clean /Volumes/YourDriveName

This fix resolves the resource fork variant of Mac error code -36 in the vast majority of cases. If the error persists after running dot_clean, the cause is something other than resource fork files — continue to the next fixes.

Fix 2: Copy Files in Smaller Batches

If the error occurs when copying a large folder, try copying its contents in smaller batches — a few files at a time rather than all at once.

This diagnostic approach serves two purposes simultaneously:

First, it may allow the overall copy operation to succeed by avoiding whatever specific file or combination of files is triggering the error.

Second, it helps identify which specific file is causing the failure. When error -36 appears during a batch copy, macOS doesn’t always identify the specific problematic file clearly. Copying in smaller groups narrows down the culprit.

Process:

1. Open the source folder
2. Select 20–30 files rather than the entire folder
3. Copy to the destination
4. If successful, continue with the next batch
5. When a batch fails, reduce that group further to identify the specific file causing the error

Once you identify the problematic file, you can either skip it, use Terminal to copy it directly (Fix 5), or investigate it specifically for corruption.

Fix 3: Run First Aid in Disk Utility

Mac’s built-in Disk Utility includes a First Aid function that scans drives for file system errors and repairs them where possible. This is the appropriate next step when dot_clean doesn’t resolve the issue, particularly when the error appears with multiple different files or across multiple operations.

How to run First Aid:

1. Open Disk Utility — press Cmd + Space, type “Disk Utility”, press Enter
   
2. In the left sidebar, locate the drive that’s involved in the failing copy operation — either the source or destination drive
   
3. Select the drive (not just a partition — the physical drive entry)
   
4. Click “First Aid” in the top toolbar
   
5. Click “Run” and allow the process to complete — this can take anywhere from 2 minutes to 30 minutes, depending on drive size and condition
   
6. Review the results:
   
   • “The operation was successful” — no significant errors found
   • Error messages indicating repaired issues — the repair may have fixed the problem
   • Error messages indicating irreparable errors — the drive has serious problems requiring professional attention or replacement
7. After First Aid completes successfully, retry your file copy operation
   

Running First Aid on the startup disk:

If the error involves your Mac’s internal startup drive, First Aid can still be run from the main Disk Utility interface in recent macOS versions. However, for a thorough repair of the startup disk, booting into macOS Recovery Mode provides a more complete First Aid environment:

1. Apple Silicon Mac: Hold the power button until “Loading startup options” appears
2. Intel Mac: Hold Cmd + R during startup
3. Select Disk Utility from the Recovery Mode options
4. Run First Aid on the internal drive

Fix 4: Check Drive Health with Terminal SMART Data

For external drives showing persistent error -36 across multiple files, checking the drive’s SMART (Self-Monitoring, Analysis and Reporting Technology) health data provides critical information about whether the hardware itself is failing.

Using Terminal to check drive health:

1. Open Terminal
   

Run:

diskutil list

2.  This shows all connected drives with their identifiers (disk0, disk1, disk2, etc.)
   

To check the SMART status of a specific drive:

diskutil info /dev/disk1 | grep SMART

3.  (Replace disk1 with your drive’s identifier)
   
4. Look for “SMART Status: Verified” (healthy) versus “SMART Status: Failing” (hardware failure imminent)
   

A drive reporting SMART failure status should be treated as an emergency. Back up all data immediately using whatever method works — even if that means the backup process encounters some errors. Do not continue regular use of a SMART-failing drive.

Using Disk Utility for SMART status:

1. Open Disk Utility
2. Select the physical drive in the left sidebar
3. The bottom information panel shows S.M.A.R.T. Status
4. “Verified” means healthy — “Failing” means the drive needs immediate replacement

Note that SMART data is only available for direct-attached drives (USB, Thunderbolt, internal). SMART data is typically not accessible for drives connected through certain USB enclosures or NAS devices.

Fix 5: Use Terminal to Copy Files Directly

When Finder throws error -36, bypassing Finder entirely and using Terminal’s cp command can often complete the same copy operation successfully. Terminal’s copy function handles file system operations differently from Finder — it can often work around the specific metadata handling issues that trigger error -36.

Basic Terminal copy command:

cp -R /path/to/source/folder /path/to/destination/folder

The -R flag enables recursive copying — it copies the folder and all its contents including subfolders.

More robust copy using rsync:

For large transfers or situations where you need to resume after interruption, rsync is more powerful:

rsync -avh /path/to/source/ /path/to/destination/

Breaking down the flags:

• -a — Archive mode (preserves permissions, timestamps, symbolic links)
• -v — Verbose output (shows each file being copied)
• -h — Human-readable file sizes

rsync with error handling:

rsync -avh –ignore-errors /path/to/source/ /path/to/destination/

The –ignore-errors flag instructs rsync to continue copying even when individual files fail — allowing you to complete the bulk of the transfer and then investigate specific failed files afterward.

rsync with resource fork exclusion:

rsync -avh –exclude=’._*’ –exclude=’.DS_Store’ /path/to/source/ /path/to/destination/

This variant excludes dot underscore resource fork files and.DS_Store files entirely — preventing them from causing errors while preserving all actual file content.

Using rsync with error exclusion is one of the most practical approaches for completing large transfers where a small number of problematic files would otherwise block the entire operation.

Fix 6: Identify and Handle Problematic Dot Files

If dot_clean didn’t fully resolve the error, manually identifying and addressing problematic hidden files provides more precise control.

Reveal hidden files in Finder:

Press Cmd + Shift +. (period) In any Finder window, toggle hidden file visibility. This shows all dot files, including.DS_Store files and dot underscore resource fork files.

Find all dot underscore files on a specific volume via Terminal:

find /Volumes/YourDriveName -name “._*” -type f

This lists every dot underscore file on the specified drive.

Delete all dot underscore files on a volume:

find /Volumes/YourDriveName -name “._*” -type f -delete

Use this command carefully — it removes all resource fork sidecar files from the specified volume. This is appropriate when copying to a non-Mac file system where resource fork data is irrelevant (FAT32, exFAT drives used cross-platform).

Find and remove .DS_Store files:

find /Volumes/YourDriveName -name “.DS_Store” -type f -delete

.DS_Store files store folder view preferences and are generally safe to delete — they’ll be regenerated by macOS as needed.

Fix 7: Check and Repair File Permissions via Terminal

File permission issues can cause I/O errors that manifest as error code -36. This is particularly relevant for files that were created under different user accounts, transferred from other systems, or modified by applications with different permission sets.

Check permissions on a specific file:

ls -la /path/to/file

The output shows the permission string (e.g., -rw-r–r–), the owner, and the group.

Repair permissions on a folder and its contents:

sudo chmod -R 755 /path/to/folder

This sets read/write/execute permissions for the owner and read/execute for group and others — appropriate for most standard folders.

For files specifically (not folders):

sudo chmod -R 644 /path/to/folder

This sets read/write for the owner and read-only for the group and others.

Change ownership of files:

sudo chown -R $(whoami) /path/to/folder

This transfers ownership of the folder and all its contents to your current user account, resolving permission errors caused by ownership mismatches.

Note: sudo commands require your administrator password. Terminal will prompt for it when needed — the password won’t display as you type, which is normal macOS behavior.

Fix 8: Check Drive Connections and Cable Integrity

Physical connection issues are an underappreciated cause of Mac error code -36. A damaged cable, a worn USB port, or a loose connection can create exactly the kind of intermittent read/write failure that produces error -36.

Diagnostic steps:

1. Try a different cable — USB, Thunderbolt, or Lightning cables can develop internal wire breaks that cause intermittent failures without any visible external damage. Swap the cable and test.
   
2. Try a different port — Connect the drive to a different USB or Thunderbolt port on your Mac. Port damage is more common than it appears.
   
3. Connect directly to Mac — If the drive is connected through a hub, dock, or adaptor chain, connect it directly to your Mac’s port. Hubs and docks introduce additional connection points and can cause power delivery issues.
   
4. Test on a different Mac — If available, connect the drive to a different Mac and test the same copy operation. If the error disappears, the issue is with your Mac’s port or its interaction with the drive.
   
5. Check the drive enclosure — For external drives in third-party enclosures, the enclosure’s USB bridge controller can fail. Testing the bare drive (if possible) or a different enclosure eliminates this variable.
   

Physical connection diagnostics are especially important when error -36 appears alongside other symptoms like slow transfer speeds, drives not mounting reliably, or drives dropping offline during transfers. When physical or driver-level instability affects data transfer, the result is often broader system-side I/O failures — not limited to storage devices alone.

A similar system-level failure pattern is explained here:
“How to Fix Audio Renderer Error in Windows 11 Guide” covers how hardware communication breakdowns and driver-level interruptions can disrupt real-time data processing in Windows systems.

Fix 9: Reformat the Destination Drive

If error -36 consistently occurs when copying to a specific external drive — and the source files copy successfully to other destinations — reformatting the destination drive may be necessary.

Important: Reformatting erases all data on the drive. Back up anything on the drive first.

Choosing the right file system format:

APFS — Best choice for drives used exclusively with modern Macs (macOS 10.13 High Sierra and later). Optimal performance, best support for macOS features, including Time Machine.

Mac OS Extended (HFS+) Journaled — Better choice for drives that need compatibility with older Macs or Time Machine on older macOS versions.

exFAT — Best choice for drives shared between Mac and Windows. Supports large files, has no macOS volume size limitations, and is natively supported by both operating systems without third-party drivers.

FAT32 — Maximum compatibility across all systems, but limited to a 4GB maximum file size. Appropriate only for small drives used with legacy systems or devices like cameras and gaming consoles.

How to reformat in Disk Utility:

1. Open Disk Utility
2. Select the drive in the left sidebar (the physical drive, not a partition)
3. Click “Erase” in the top toolbar
4. Choose your desired format from the dropdown
5. Name the drive
6. Click “Erase” to confirm
7. Wait for the format process to complete
8. Test the copy operation to the newly formatted drive

If error -36 persists even after reformatting, the drive itself has hardware problems. Proceed to checking SMART status and considering drive replacement.

Fix 10: Update macOS

macOS updates regularly include file system driver improvements, bug fixes for known I/O errors, and APFS enhancements. If you’re running an older macOS version, a pending update may contain a fix for the specific error -36 scenario you’re encountering.

Check for updates:

1. Open System Settings (macOS Ventura/Sonoma) or System Preferences (older macOS)
2. Click “General” → “Software Update.”
3. Install any available updates
4. Restart your Mac
5. Test the copy operation

This is particularly relevant for:

• Error -36 appears after a new external drive or storage device purchase
• Error -36 on specific file types that weren’t problematic in a previous macOS version
• Error -36 that started after a partial macOS update

Fix 11: Use Third-Party File Transfer Tools

When macOS’s native Finder cannot complete a copy operation due to error -36, several third-party applications provide alternative transfer methods with better error handling and recovery capabilities.

Recommended tools:

Carbon Copy Cloner — Professional disk cloning and file transfer utility with detailed error reporting, the ability to skip problematic files and continue, and comprehensive logging of exactly which files caused errors and why.

SuperDuper! — Similar functionality to Carbon Copy Cloner, focused on reliable backup and disk cloning with robust error handling.

PathFinder — A comprehensive Finder replacement with better file operation feedback and alternative copy engine options.

Transmit (for network drives) — Panic’s file transfer client handles FTP, SFTP, S3, and WebDAV transfers with significantly better error recovery than Finder’s native network file handling.

For users who regularly encounter error -36 on network drives or NAS devices, Transmit’s dedicated network transfer protocol support is particularly valuable.

Mac Error Code -36 on Specific Scenarios

Mac Error Code -36 on External Hard Drive

This is the most common scenario. When error -36 appears specifically on external drives, work through this specific sequence:

1. Run dot_clean on the source folder first
2. Check the destination drive’s file system format — APFS or HFS+ avoids resource fork compatibility issues
3. Try rsync instead of Finder drag-and-drop
4. Run First Aid on both the source and destination drives
5. Check SMART status
6. Inspect the cable and connection

For new external drives showing error -36 immediately, the drive may have shipped with a file system format incompatible with your use case — reformat to APFS or exFAT, depending on your needs.

Mac Error Code -36 on Network Drive / NAS

Network-related error -36 has specific additional causes:

SMB protocol issues: macOS’s SMB implementation has historically had compatibility issues with certain NAS devices and Windows file servers. Update your NAS firmware, ensure SMB 2.0 or 3.0 is enabled rather than SMB 1.0.

Permissions on network share: Verify that your user account has full read/write permissions on the network share, not just the top-level folder.

Network stability: Error -36 on network drives can indicate network interruptions rather than file system problems. Run the copy during off-peak network hours and use rsync with the –partial flag to enable resume capability.

Connect using AFP instead of SMB (older NAS devices): Some legacy NAS devices work better with macOS using AFP (Apple Filing Protocol) rather than SMB. Check your NAS settings for AFP support.

Mac Error Code -36 When Copying to USB Drive

USB drives formatted as FAT32 are particularly prone to error -36 because FAT32 doesn’t support macOS resource forks, extended attributes, or file names with certain characters.

Solutions specific to USB drives:

• Run dot_clean on the source before copying
• Use rsync with –exclude=’._*’ to exclude resource fork files
• Reformat the USB drive as exFAT for better Mac compatibility with large file support
• Check that file names don’t contain characters illegal in FAT32 (colons, question marks, asterisks, backslashes)

Mac Error Code -36 on Internal Drive

Error -36 on the internal startup drive is the most serious scenario — it suggests file system corruption or storage hardware issues.

Immediate steps:

1. Back up your Mac using Time Machine or another backup method immediately
2. Boot into macOS Recovery Mode and run First Aid on the internal drive
3. If First Aid reports irreparable errors, reinstall macOS over the existing installation (this preserves data while refreshing system files)
4. If the error persists after a macOS reinstall, the storage hardware (SSD or hard drive) is failing and requires professional service or replacement

Mac Error Code -36 vs Similar macOS Error Codes

Understanding how error -36 relates to other common macOS errors prevents misdiagnosis.

Error -36 (ioErr) — Input/Output error during file read or write; file system, hardware, or resource fork related

Error -43 (fnfErr) — File not found; the source file doesn’t exist at the expected path

Error -50 (paramErr) — Parameter error; incorrect parameters passed to a system call, often related to file name characters or path length

Error -54 (permErr) — Permission error; the operation was denied due to insufficient file permissions

Error -69842 — Media is write-protected; destination drive or file is read-only

Error -8062 — Bad name error; file name contains illegal characters for the destination file system

Error 100093 — Network-related error; typically SMB protocol failure

The presence of error -36, specifically, combined with its occurrence during file copy operations, points clearly to I/O layer failures rather than these other categories. The fixes in this guide target that specific layer systematically.

How to Prevent Mac Error Code -36 From Returning

Resolving the immediate error is only part of the solution. Here’s how to minimize future occurrences.

Eject drives properly every time

Improper drive ejection — pulling a USB drive without ejecting in Finder — is a primary cause of file system corruption that leads to future error -36 appearances. Always eject drives through Finder’s eject button, the desktop eject option, or the Disk Utility eject function before physically disconnecting.

Choose compatible file system formats

Match your drive’s format to its primary use case:

• Mac-only use: APFS
• Mac and Windows cross-platform: exFAT
• Legacy device compatibility: FAT32 (with awareness of the 4GB file size limit)

Using the appropriate format eliminates the resource fork compatibility issues that cause the majority of error -36 cases.

Run Disk Utility First Aid periodically

For external drives used regularly, running First Aid monthly catches developing file system issues before they cause data loss or operation failures. Five minutes of maintenance prevents hours of troubleshooting.

Keep macOS updated

Apple regularly releases file system improvements and I/O bug fixes in macOS updates. Keeping your system current ensures you benefit from these improvements.

Use quality cables

Invest in quality cables for external drive connections. Generic or worn cables introduce connection instability that causes I/O errors. Thunderbolt cables in particular should be from reputable manufacturers — the protocol’s complexity makes it more sensitive to cable quality.

Monitor drive health proactively

Check SMART status on external drives periodically using Disk Utility or a dedicated tool like DriveDX or SMARTReporter. Catching the drive health deterioration early allows data recovery before failure becomes catastrophic.

Final Word

Mac error code -36 is a well-defined, systematically solvable problem. It looks alarming when it first appears — particularly when it interrupts an important file transfer — but in the overwhelming majority of cases, it’s resolved quickly once you understand what’s causing it.

Start with dot_clean in Terminal. It resolves the resource fork file conflicts that drive the majority of error -36 cases and takes under two minutes. If that doesn’t resolve the issue, work through First Aid in Disk Utility, then the rsync Terminal approach, then the connection and hardware diagnostics.

The hierarchical approach matters here. Each fix targets a specific layer of the potential failure — from the file metadata level, through the file system level, to the hardware level. Working through them systematically ensures you find the actual cause rather than applying random fixes and hoping something sticks.

For persistent error -36 that doesn’t respond to software fixes — particularly when accompanied by slow drive performance, unusual sounds from a hard drive, or SMART warnings — treat it as a hardware alert and prioritize data backup immediately.

Mac error code -36 is solvable. This guide gives you everything you need to solve it.

FAQ