How to Fix Error Code 36 on Mac: Simple Step-by-Step Guide

How to Fix Error code 36 mac Step by Step

How to Fix Error Code 36 on Mac: Simple Step-by-Step Guide

Encountering an unexpected error while copying or moving files on your Mac can be incredibly frustrating.

One of the most common issues users face is the dreaded Error code 36.

This error usually occurs when the system cannot read or write data properly during a file transfer, leaving your workflow at a standstill.

To understand our goal today, consider the dictionary definition of the word ‘fix’: it means to repair something, to arrange or agree a time, place, price, etc., or to fasten something.

In our context, we are looking at the first definition: repairing your file system process to ensure your data transfers proceed without interruption.

What Causes Error Code 36 on macOS?

Error code 36 typically indicates an issue with hidden files, specifically ‘DS_Store’ files. macOS creates these hidden files to store folder attributes, such as icon positioning or view settings.

If these files become corrupted or incompatible during a move from one drive (like an external HDD) to another (like your Mac’s internal SSD), the operating system triggers Error code 36.

It essentially acts as a safeguard, stopping the process to prevent potential data corruption, although it often creates more inconvenience than it solves.

Read Also: Arsip

Step 1: Using the Terminal to Clear Hidden Files

The most effective and widely recognized solution involves using the Terminal app to execute the ‘dot_clean’ command. This command merges the hidden attribute files with the source files, essentially cleaning up the discrepancy that causes the error. First, open ‘Terminal’ from your Applications folder or via Spotlight search. Once the window is open, type dot_clean followed by a space. Do not press enter yet. Instead, locate the folder or drive that is causing the error in Finder and drag it directly into the Terminal window. This action will automatically paste the correct file path. Now, press ‘Enter’. Terminal will process the command and merge the hidden files, which often resolves the issue instantly.

Read Also: Index

Step 2: Repairing File Permissions

If the Terminal command did not resolve the problem, the issue might be related to permission settings.

Files often have specific read and write access rules that can become corrupted over time.

To fix this, navigate to the folder where the files are stored, right-click it, and select ‘Get Info’.

At the bottom of the window, you will see ‘Sharing & Permissions’.

Unlock the settings by clicking the padlock icon and entering your administrator password.

Ensure that your user account has ‘Read & Write’ access.

Click the gear icon and select ‘Apply to enclosed items’ to ensure the permissions cascade down to all the files inside the folder.

Attempt the transfer again to see if the error persists.

Step 3: Restarting Finder

Sometimes, the issue is not with the files themselves, but with the Finder process being stuck or unresponsive.

The Finder is the heart of the macOS file system, and if it encounters a minor glitch, it might report a false error during transfers.

You can force a restart of Finder by pressing ‘Option + Command + Escape’ on your keyboard.

This opens the ‘Force Quit Applications’ menu.

Select ‘Finder’ from the list and click ‘Relaunch’.

Once Finder restarts, try performing your file transfer operation again.

This simple step often clears temporary cache issues that might be blocking the process.

Step 4: Using Safe Mode

If the steps above do not yield results, it is time to check if third-party software or background processes are interfering with your system.

Restart your Mac and hold the ‘Shift’ key during the boot-up process to enter Safe Mode.

Safe Mode performs a system check and prevents third-party extensions from loading.

If the file transfer works in Safe Mode, you know for certain that another application installed on your Mac is causing the conflict.

You may need to review recently installed software or antivirus tools that could be locking the file transfer process.

Conclusion

Error code 36 can certainly feel like a major roadblock, but with the right approach, it is easily manageable.

By using the ‘dot_clean’ command in Terminal, verifying file permissions, and ruling out software conflicts via Safe Mode, you can quickly get back to your work.

Always ensure that your macOS is updated to the latest version to prevent these types of system errors from recurring in the future.

Remember, taking a systematic approach to troubleshooting is the best way to repair any system issue effectively.


Frequently Asked Questions (FAQ)

What is the fastest way to fix Error code 36?

The fastest method is using the ‘dot_clean’ command in the Terminal, which merges hidden files and often resolves the error immediately.

Is Error code 36 dangerous for my data?

Generally, no.

It is a system safeguard that halts the transfer to prevent corruption.

However, ensure you do not force-delete files until you have verified the integrity of your data.

Can I fix this on an external hard drive?

Yes, the ‘dot_clean’ method works perfectly for external hard drives, USB sticks, and network drives that are showing this error.

Why does my Mac keep showing Error code 36?

It usually happens when transferring files between different file systems (like FAT32 to APFS) where hidden system files become incompatible.


Written by: John Smith

Leave a Comment