Fix macOS 'The operation can’t be completed' Error Fast

Start with the 30-second fix: restart Finder and check the basics

I've lost count of how many times I've walked into a client's office and that exact error is plastered on their screen, usually after they tried to move a folder to an external drive or delete a stubborn PDF. The message reads something like:

The operation can’t be completed because an unexpected error occurred (error code -36).

Before you panic, do two things. First, restart Finder. It's often stuck in a weird state. Click your desktop, hit Command + Option + Escape, select Finder, and click Relaunch. That takes 10 seconds and clears dead file handles.

Second, check if the file or folder is actually open in another app. A client once spent an hour fighting this because she had a PDF open in Preview and kept trying to move the folder that contained it. Close all apps that might be using the file, then try again.

Still stuck? The 5-minute fix: check disk permissions and format

If the restart didn't do it, the problem is usually permissions on the volume you're working with. This happens a lot with external drives, especially if they're formatted as NTFS or exFAT. macOS can read those but often can't write reliably, which throws those cryptic error codes.

Open Disk Utility (in Applications/Utilities). Select the drive and click First Aid. Let it run. That repairs permissions on the volume. I've seen this fix error -36 more times than I can count.

If the drive is NTFS, you might be out of luck without third-party software like Paragon NTFS. But first, check if the drive is failing. Use Smart Utility or just listen for clicking sounds. I had a client whose external drive was dying and this error was the first symptom.

Also, if you're copying to a network share (SMB), try copying to a local folder first. Network hiccups cause these errors too.

Advanced fix (15+ minutes): reset Finder preferences and clear caches

If the error persists on local files, it's time to reset Finder's preferences and clear its cache. This is my go-to when the simple stuff fails. Here's how:

1. Quit Finder completely (use Activity Monitor to force quit it if needed).
2. In Finder, press Command + Shift + G and go to ~/Library/Preferences/.
3. Find com.apple.finder.plist and move it to the Desktop (don't delete yet).
4. Also go to ~/Library/Caches/ and delete the com.apple.finder folder there if it exists.
5. Relaunch Finder (it'll rebuild the preferences).

That resolves most weird Finder behavior. If the error is tied to a specific file, try copying it to a new folder with a shorter name. Long filenames or special characters (like emojis) can trip up macOS and cause error -8080 or -36.

For the truly stubborn cases, I run this command in Terminal to reset ACL permissions on the problematic folder. It's safe, but it does remove custom permission settings:

sudo chmod -RN /path/to/problem/folder

Then set the folder back to your user's ownership:

sudo chown -R $USER:staff /path/to/problem/folder

That's fixed a few situations where even Disk Utility First Aid failed. I remember a client who had a folder full of design assets that would always throw this error when copying. The ACL reset did it.

If you're still hitting the error after all this, your macOS install might be corrupted. Back up your data and reinstall macOS from Recovery Mode. It's a nuclear option, but I've had to do it twice in the last year.

One last thing: if the error happens when using iCloud Drive, sign out of iCloud and sign back in. That's a separate beast, but it acts the same way.

Bottom line: start with Finder relaunch, move to Disk Utility, then reset preferences. You'll fix 95% of these errors without touching the terminal. It's the other 5% that keep me in business.