You’re staring at a progress bar that refuses to move, and then the dreaded dialog box appears: “The Finder can’t complete the operation because some data in “filename” can’t be read or written (Error code -36).” It’s a frustratingly common blocker that halts your workflow, whether you’re archiving a project, moving media assets, or simply cleaning up your desktop. While it looks like a generic failure, fixing error code -36 requires understanding why the file system is rejecting the command. Is it a localized permission glitch, a corrupted metadata file, or a deeper network driver issue? In my experience supporting Mac-based creative teams, the key is distinguishing between these causes immediately. By isolating the root cause—be it a failed device driver installation or a standard read/write permission conflict—you can apply the correct fix rather than blindly cycling through generic restarts. This guide breaks down the error into manageable segments, offering safe, step-by-step solutions that don’t require you to become a terminal expert overnight.

What Is Mac Error Code -36 and Why It Happens

To troubleshoot effectively, we need to look under the hood. What is error code -36 at its core? It is a POSIX error EIO (Input/Output error) or a permissions error (EPERM) that macOS wraps into a user-friendly message. Essentially, the kernel requested data from a block device or a network share, and the driver responded with a "no go."

Decoding the 'Can't Be Read or Written' Message

When you see this message, macOS is telling you it cannot access the specific data blocks on the volume. Think of it like a library system where the card catalog says a book is on shelf 4, but when you walk to shelf 4, the slot is physically blocked by a loose shelf or the book is missing entirely. The system (Finder) asked for the book (data), and the storage layer (disk driver) failed to deliver it.

This often ties into system compatibility issues. For instance, if you are moving files from a drive formatted in NTFS or exFAT to an APFS container, the metadata structures differ. If the hidden system files (.DS_Store) contain attributes that the source file system doesn't support, or if the target file system rejects the specific permission flags macOS tries to write, you get this error. It’s less about the file content being "corrupt" in the human sense (like a broken PDF) and more about the file metadata being incompatible or unreadable by the current file system driver.

Common Triggers: Drivers, Updates, and Corruption

In most cases I’ve diagnosed, the trigger is one of three things: corrupted dot files, a faulty external connection, or a recent device driver installation that left the system in an inconsistent state.

1. Corrupted .DS_Store Files: These hidden files store view options. If a drive is shared between macOS and Windows, the Windows side may write data to these files in a way macOS cannot read back, causing a "can't be written" loop.
2. Post-Update Glitches: Many users report error code -36 appearing specifically after upgrading to macOS Ventura or Sonoma. This often happens because the update invalidates cached metadata, forcing the system to rebuild indexes. If that rebuild process hits a permission wall on a user folder, the error surfaces.
3. Hardware Faults: Loose USB-C connections or failing SSD controllers can cause intermittent I/O errors that manifest as -36.

Step-by-Step: 5 Methods to Fix Error Code -36

Now that we’ve identified the likely culprits, let’s move to remediation. We’ll go from the safest GUI-based fixes to more advanced terminal commands.

Method 1: Run First Aid on the Storage Device

Before touching Terminal commands, we must rule out file system integrity issues. This is the safest first step. Disk Utility’s First Aid checks the volume's catalog and repair structures. If the error is caused by a bad sector or a broken pointer in the HFS+ or APFS structure, this tool will often fix it automatically.

• Open Disk Utility from Applications > Utilities (or Spotlight search).
• Select the drive where the error occurred (internal Macintosh HD or external USB/SSD) in the sidebar.
• Click the First Aid button in the toolbar.
• Click Run and enter your admin password.
• Wait for the scan to complete. If it reports errors, click Repair. If it says "The volume appears to be OK," you can likely rule out deep file system corruption and move to the next method.

Method 2: Clean Corrupted Dot Files with dot_clean

If First Aid came back clean, the issue is likely isolated to corrupted metadata files, specifically .DS_Store files. These files are notorious for breaking when drives are handed off between different operating systems. The dot_clean utility is designed to merge these dot files with their parent directory structures, effectively "cleaning" the view settings without deleting user data.

Safety Warning: Always create a Time Machine backup or manual copy of critical data before running system-level commands. While dot_clean is generally safe, unexpected disk errors during execution can lead to data loss if the drive is already failing.

To execute this, open Terminal. You have two options:

Option A: Targeted Fix (Recommended) Identify the specific volume or folder causing the issue. Let’s say the problem is on an external drive named "BackupDrive."

ls /Volumes/

sudo dot_clean /Volumes/BackupDrive

Option B: Drag-and-Drop Fix If you don't know the exact path, you can use a slick Finder trick:

1. In Terminal, type dot_clean (with a space at the end).
2. Drag the folder or drive icon from Finder into the Terminal window.
3. Press Enter.
4. Enter your password when prompted.

This command recursively repairs the dot files in that specific container. Try your file move operation again after it completes.

Method 3: Verify Read/Write Permissions via Finder

Sometimes, the file system is fine, but your user account simply lacks the privilege to modify the specific directory. This is common when moving files out of protected system directories or when a folder has been copied from a secure network share that stripped permissions.

1. Locate the folder containing the problematic file in Finder.
2. Right-click it and select Get Info (or press Cmd + I).
3. Expand the Sharing & Permissions section at the bottom.
4. Check the privilege for your username. It must be set to Read & Write.
5. If you see "Read only" or "No access," click the Lock icon at the bottom right, enter your password, and change the privilege to "Read & Write."
6. Crucial Step: If the folder is inherited from a parent, you may need to click the gear icon in that section and select Apply to enclosed items to force the permission change down the directory tree.

Method 4: Reinstall or Update Specific Device Drivers

If this error is occurring on Bluetooth peripherals, Logitech devices, or specific USB audio interfaces, it’s often a driver conflict. In my experience, a half-installed reinstall software suite or a driver that hasn't updated for the latest macOS version can cause the kernel extension to hang, resulting in I/O timeouts that look like -36 errors.

For example, if you are using a Logitech Hub or a specific graphics card, go to the manufacturer’s website. Do not just install the latest version; uninstall the current version first using their dedicated uninstaller (or CleanMyMac Uninstaller if you have it). Then, reboot the Mac and install the fresh driver package. This resets the kernel extension cache and often resolves the "peripheral disconnect" symptoms that manifest as file errors.

Method 5: Bypass Finder Using Terminal Commands

If Finder is completely locked on a specific operation, you can bypass its user interface entirely and use core Unix commands. This is for advanced users only. If you type a command incorrectly, you could delete the wrong file. Use with caution.

If you cannot delete a file causing the error:

cd /path/to/problem/folder

rm -f problematic_file.ext

If you cannot move a file:

mv problematic_file.ext ~/Desktop/

If you cannot copy a file:

cp -p original_file.ext /path/to/destination/

Using -p preserves permissions, which can sometimes help if the issue was related to permission stripping. If these commands also fail with a "Permission denied" or "Input/output error" message, you have confirmed a hardware or deep file system issue, and you should stop immediately to prevent data loss.

Troubleshooting Network & SMB Specific Issues

A significant gap in most generic troubleshooting articles is the distinction between local disk errors and network errors. If you are accessing a file via \\server\share or smb://server/share, error code -36 has a different root cause.

Why SMB Sharing Triggers Error -36

When you encounter error code -36 smb, the issue is rarely about the local disk. It’s about the SMB (Server Message Block) protocol negotiation. macOS 13+ (Ventura and later) has stricter SMB implementation checks. If the server is running an older version of Windows (pre-2019) or a Linux Samba config with mismatched encryption requirements, macOS may block the write operation for security reasons, throwing a -36 error.

To fix this:

1. On the Mac, go to System Settings > General > Sharing.
2. Ensure "File Sharing" is configured correctly if you are the server.
3. If you are the client, check if the server requires SMB 2.0 or higher. Modern macOS prefers SMB 3.1.
4. Verify that the specific share allows "Everyone" or your specific user group Write access. Often, network shares are mounted as read-only by default, and when you try to save, the Mac gets a "can't be written" response.

Fixing Peripheral Disconnect Errors on Bluetooth/USB

If the -36 error happens when you plug in a device, such as an external hard drive or a Bluetooth keyboard's memory stick, it may be a peripheral disconnect error. The device is flapping in and out of the USB/Bluetooth stack.

Perform a hardware fault diagnosis checklist:

• Try a different USB port (preferably a direct port on the Mac, not a hub).
• If using USB-C, try a different cable. Many "data" cables are actually charge-only, causing intermittent I/O failures.
• For Bluetooth, unpair the device completely, restart the Mac, and re-pair.
• If the error persists on multiple ports and cables, the device's controller board is likely failing. This is a hardware issue, not a software bug.

Preventing Future Occurrences & Safe Recovery

Prevention is cheaper than recovery. Implementing a few habits can stop permanent fix for error code -36 searches in the future.

Best Practices for Device Driver Installation

Always verify system compatibility before installing new drivers. If you are running Apple Silicon (M1/M2/M3), ensure the driver explicitly supports ARM64. Universal binaries are great, but native ARM64 drivers are more stable. Before a major macOS update, check your peripheral manufacturers' forums for known conflicts.

When to Seek Professional Hardware Repair

If Disk Utility's First Aid fails to repair the drive, and you hear clicking, grinding, or humming noises from an HDD, stop using it immediately. This is a physical failure. For SSDs, if the drive becomes unreadable after multiple reformatting attempts, it is likely suffering from controller failure.

Note: Do not use sfc /scannow on Mac; that is a Windows command. If you are in doubt, boot into Recovery Mode (hold Power button on Apple Silicon, Cmd-R on Intel) and run First Aid from there. If that fails, the drive needs data recovery specialists, not more software attempts.

FAQ

Can I fix Mac Error Code -36 without using Terminal? Yes. In about 80% of cases, the issue is resolved by running First Aid in Disk Utility or adjusting Finder Permissions via the Get Info window. These are purely graphical interface solutions that require no command-line knowledge.

Why does Error Code -36 appear after a macOS update? Updates often change file system structures or invalidate cached metadata. The .DS_Store files may contain attributes that no longer map correctly to the new OS version's file hierarchy. This causes a temporary read conflict until the system rebuilds its index. Usually, restarting or running First Aid resolves this post-update glitch.

Is it safe to delete all .DS_Store files system-wide? Technically, yes, because they regenerate automatically. However, it can temporarily reset your custom Finder view settings (e.g., icon size, sort order) for every folder. I recommend using dot_clean instead, which merges and repairs them rather than just deleting them, preserving your layout preferences where possible.

Does Error Code -36 indicate a failing hard drive? Not always. It is primarily a permissions or metadata issue. However, if the error persists across multiple files, occurs on a specific drive only, and First Aid cannot repair the volume, it is a strong indicator of hardware failure. At that point, treat the drive as dying and back up data immediately.

Conclusion

Dealing with Mac error code -36 is rarely about the file itself being "broken" in a traditional sense; it’s almost always a conversation failure between your file system, your user permissions, and your hardware drivers. In the vast majority of cases, you can resolve this by running First Aid in Disk Utility or correcting Sharing & Permissions in Finder. These two steps cover most local file issues.

If you are dealing with network shares, focus on SMB configuration and write permissions on the server side. And if you are using external peripherals, remember that a loose cable or a outdated driver suite can mimic a disk error. Keep your device driver installation packages up to date, and always maintain a backup. Your Mac is powerful, but it’s not psychic—if a drive starts throwing I/O errors, assume the worst and save your data first.

Did you encounter a specific scenario not covered here, such as errors with DaVinci Resolve projects or a specific Logitech device? Let me know in the comments below. Also, if you found this guide helpful, share it with a colleague who might be stuck on a copy operation—it’s a pain no one enjoys.