macOS 'The operation can’t be completed' Fix That Actually Works

That vague error usually comes from a stuck Finder or a corrupted .DS_Store file. Here's a quick fix that takes under a minute, plus the deeper causes.

That vague “The operation can’t be completed” message is annoying, especially when you don't know what operation it's talking about. You try to move a file, delete a folder, or drag something to the trash, and macOS just shrugs. Let's fix it.

The Quick Fix: Restart Finder

Nine times out of ten, Finder has just gotten itself into a weird state. You don't need to restart your Mac. Just relaunch Finder.

  1. Click your desktop so you're in Finder.
  2. Press Command + Option + Escape to open the Force Quit window.
  3. Select Finder from the list (it's usually at the bottom).
  4. Click Relaunch.

After you click Relaunch, the screen will flicker for a second. That's normal. Your desktop icons will disappear and come back. Then try moving or deleting that file again. In most cases, it works now.

Why That Works

Finder is the app that handles all file operations on your Mac. When it gets bogged down with a network mount, a syncing cloud folder, or just a lot of small files, it can lose track of what it's doing. Restarting clears its memory and forces it to re-read the folder structure. It's like turning your Wi-Fi router off and on again, but for files.

When the Quick Fix Doesn't Work: Check .DS_Store

If Finder relaunch doesn't help, the culprit is often a corrupted hidden file called .DS_Store. That file stores folder view settings like icon size, sort order, and background color. When it gets corrupted, it can cause exactly this kind of error when you try to move or delete the folder it lives in.

Here's how to delete it safely:

  1. Open Terminal (found in /Applications/Utilities/).
  2. Type cd (that's 'change directory'), then drag the problem folder from Finder into the Terminal window. It will fill in the path for you.
  3. Press Return.
  4. Type this exactly, then press Return:
rm .DS_Store

Don't worry about typing it wrong – Terminal won't delete anything else unless you point it at the wrong folder. After you run that command, you won't see any confirmation. Just type ls -a and press Return to list all files, including hidden ones. If .DS_Store is gone, you're good.

Now go back to Finder and try your operation again. The folder's view settings might reset to default (that's fine), but the error should be gone.

Less Common Variations

Sometimes the error text includes more details, like “The operation can’t be completed because one or more required items can’t be found.” That one usually means you're trying to move a file that's already been moved or deleted by another app, like a cloud sync client. Check your Downloads folder or Desktop for a duplicate that's actually there.

Another variation: “The operation can’t be completed because you don’t have permission to access some of the items.” That's a permissions problem. To fix it:

  1. Select the file or folder in Finder.
  2. Press Command + I to Get Info.
  3. Scroll to Sharing & Permissions at the bottom.
  4. Click the padlock and enter your password.
  5. Change the privilege for your username to Read & Write.

After you close that window, try again. That fix works when you're dealing with files copied from an external drive or from another Mac.

Prevention Tips

You can't stop every corrupted .DS_Store, but you can reduce the chances. Here's what I tell my techs:

  • Keep your Mac updated. Apple patches Finder bugs regularly. Go to System Settings > General > Software Update.
  • Don't force-quit Finder constantly. If you do it too often, you're more likely to hit this error. Let it work.
  • If you use OneDrive, Dropbox, or Google Drive, pause syncing before you do big folder moves. Those apps hold file locks, and Finder gets confused.
  • Restart your Mac once a week. It clears out all those hidden temp files and resets everything, not just Finder.

That's the whole toolkit. Start with the Finder relaunch, then the .DS_Store deletion, then check permissions. You'll be back to work in two minutes, not two hours.

Related Errors in macOS Errors
Fix com.apple.launchd.peruser Crash Loop on macOS Fix com.apple.launchd.peruser Crash Loop on macOS null macOS 'The operation can’t be completed' error fix Fix com.apple.launchd.peruser Crash Loop on macOS

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.