Mac error code 8003: what it means and how to fix it
Error 8003 is the Trash refusing to empty: 'The operation can't be completed because an unexpected error occurred (error code -8003)'. Behind it is almost always one stubborn item, a file that is locked, still in use by an application, owned by another user, or left in a strange state by an external drive. The Trash empties as a single operation, so one protected file blocks everything in it, and the fix is to find and neutralize that item rather than attack the whole Trash at once.
What causes it
- A file in the Trash is still open or in use by a running application.
- A locked file, or one owned by a different user account, resisting deletion.
- Items trashed from an external drive whose permissions or filesystem confuse the process.
- A file with a damaged name or a leftover fragment from an interrupted delete.
Fix it, in order
- Quit your applications and try again. Close everything, especially whatever created or used the files, then empty the Trash. In-use files are the most common single cause.
- Restart the Mac and empty the Trash before opening anything. A fresh session guarantees nothing is holding files open invisibly.
- Secure Empty the stubborn way: hold Option and choose Empty Trash. The Option key forces the Finder to override locked-file complaints for files you own.
- Isolate the offender. Move most items back out of the Trash, then empty in small batches. The batch that fails contains your problem file; deal with it individually: unlock it via Get Info (uncheck Locked), or check its permissions.
- For items from an external drive, reconnect that drive. Files trashed from a removable volume live in that volume's own Trash folder and can only be fully deleted while it is attached.
- Use Terminal only as the last resort and only if you are comfortable there: the rm command with the exact path of the stubborn item. One wrong path in a delete command is unrecoverable, which is why every gentler method comes first.
Check before you force. The files a force-empty overrides are usually junk, but 'usually' is doing work in that sentence. Glance at what the stubborn item actually is before overriding its lock; a file locked by a running backup or a system process deserves a second thought.
Common questions
Why does one file block the entire Trash? Because Empty Trash is a single operation that the Finder abandons when any item refuses. The Finder does not skip failures and continue with the rest, so one locked or in-use file produces error 8003 for the whole bin.
Is using Terminal to force-delete safe? It is powerful rather than safe. The rm command deletes instantly and permanently, with no Trash to rescue mistakes. If you use it, target one exact file path you have verified, never a folder pattern. The Finder-based methods on this page solve the problem without that risk in nearly every case.
Related errors