How to Fix Apple Mac Error Code 8060

You are trying to reorganize your desktop or move a batch of important documents to an external drive, but instead of the files seamlessly copying over, your Mac halts the process and displays a frustrating message: "The operation can't be completed because an unexpected error occurred (error code -8060)."

If you've encountered Mac Error Code 8060, you're not alone. This is a notorious error in the macOS ecosystem that typically interrupts seemingly basic tasks like copying, moving, deleting, or even just renaming a file.

While an "unexpected error" sounds intimidating, Error 8060 is rarely a sign of critical hardware failure. It is almost exclusively tied to localized file corruption, network server dropouts, or rigid system permissions. In this comprehensive guide, we will break down the root causes of Error 8060 and walk you through several effective methods to bypass it and regain control over your files.

Understanding Mac Error Code 8060

Error Code 8060 is technically classified as an I/O (Input/Output) and permissions error. It means your Mac's file system is attempting to execute a command—like reading a file from your hard drive and writing it to a new folder—but it is being blocked by a software conflict.

The most common scenarios where Error 8060 rears its head include:

• Corrupted File Headers: The specific file you are trying to move has become slightly corrupted. macOS realizes it cannot read the file correctly, so it aborts the move to prevent spreading the corruption.
• Network Connection Drops: You are trying to copy a file from your Mac to a Network Attached Storage (NAS) drive or a shared server, and the connection experiences a micro-dropout.
• Strict System Permissions: The file was created by another user account or an application that locked the file's ownership, and your current user account doesn't have the authority to alter it.
• External Drive Incompatibility: You are interacting with a third-party external drive that hasn't been properly mounted or is using an incompatible file system format.

Step 1: Check Your File Permissions

Since Error 8060 is often a permission issue, your first line of defense is ensuring you actually have the right to modify the file or folder in question.

1. Locate the file or folder that triggered the error.
2. Right-click (or Control-click) on it and select Get Info.
3. At the very bottom of the Get Info window, look for the Sharing & Permissions section. (You may need to click the tiny padlock icon in the bottom right corner and enter your Mac password to unlock these settings).
4. Under the "Name" column, find your current user account.
5. Ensure the "Privilege" next to your name is set to Read & Write. If it says "Read Only," click the text and change it.
6. Close the Get Info window and attempt to move or rename the file again.

Step 2: Restart the Finder

Sometimes, the Finder app (the program responsible for drawing your desktop and handling all file transfers) gets caught in a temporary loop or caches a bad file state. Force-restarting the Finder can quickly clear out these temporary glitches without requiring a full system reboot.

1. Hold down the Option (Alt) key on your keyboard.
2. While holding Option, Right-click the Finder icon (the smiling blue face) in your Dock.
3. Select Relaunch from the pop-up menu.

Your desktop icons will disappear for a brief second and then pop back up. Try your file operation again to see if Error 8060 is gone.

Step 3: Run Disk Utility First Aid

If you are getting Error 8060 across multiple different files, or if it happens every time you interact with a specific external hard drive, there may be underlying corruption in the drive's file directory structure. Disk Utility's First Aid feature can scan for and repair these directory errors.

1. Open Launchpad (or press Command + Space to open Spotlight Search), type Disk Utility, and open the app.
2. In the left sidebar, select the drive where the problematic file lives (this might be your main "Macintosh HD" or an external USB drive).
3. Click the First Aid button in the top toolbar.
4. Click Run to confirm.

Wait for the process to complete (your Mac may become sluggish during the scan). If First Aid reports that it found and repaired errors, restart your Mac and try the file transfer again.

Step 4: Use Terminal to Move or Delete the File

If the graphical Finder interface keeps failing, you can bypass it entirely using the Terminal. Terminal executes commands at the root system level, often ignoring the minor permission hiccups that trigger Error 8060.

To Copy a File via Terminal:

1. Open the Terminal app.
2. Type cp -R (make sure to include the space at the end).
3. Drag the problematic file from Finder into the Terminal window.
4. Drag the destination folder (where you want the file to go) into the Terminal window.
5. Press Return.

To Force Delete the File:

If the file is useless and you just want it gone, you can force delete it.

1. In Terminal, type sudo rm -rf (include the space at the end).
2. Drag the stubborn file into the Terminal window.
3. Press Return, enter your admin password, and press Return again. The file will be permanently erased.

Step 5: Check Network Stability (For Server Transfers)

If you are encountering Error 8060 specifically while copying files to or from a NAS (Network Attached Storage) drive or a company server, the issue is almost certainly a micro-disconnect in your Wi-Fi or Ethernet connection.

macOS file transfers are very sensitive to latency. If the network drops packets for even a second, the Finder will panic and throw an 8060 error rather than risk writing a corrupted file to the server.

• If you are on Wi-Fi, try plugging your Mac directly into the router via an Ethernet cable before attempting large file transfers.
• Ensure the NAS drive's firmware is fully updated to handle the SMB protocol used by modern macOS versions.
• Instead of transferring 100 files at once, try transferring them in smaller batches of 10.

Conclusion

Mac Error Code 8060 is a frustrating barrier to basic file management, but it is rarely a symptom of terminal Mac failure. By manually adjusting file permissions, relaunching the Finder, running Disk Utility, or leaning on the power of the Terminal, you can bypass this error and get your files exactly where you need them to be.