Why does Error 43 appear when I haven't touched the file in question?

Finder may have been attempting a background operation — indexing, syncing, or a copy you started and forgot about. Check whether any background sync or backup process is running.

Can Error 43 mean my file is corrupted?

In some cases, a file that has become corrupt may not be readable, producing an error during any operation that requires reading its content. Try opening the file directly to see if it is accessible.

Is there a safe way to force-delete a file causing Error 43?

Restarting and immediately emptying the Trash is one approach. Some users use Terminal's rm command as an alternative when Finder cannot complete the deletion, but this requires knowing the exact file path and understanding that the command is irreversible.

Error 43 appeared when ejecting a drive. Is that the same problem?

An eject failure is similar — Finder cannot complete the operation because something still has the drive in use. Quit all applications, check whether any Finder windows are showing the drive's contents, and try ejecting again.

Mac Error Code 43: Finder File Error Troubleshooting

Symptom

Finder shows Error Code 43 when moving, copying or deleting a file, or when emptying the Trash.

Error 43 means Finder could not complete the operation because the required file was not found or could not be accessed at a critical point in the process.
Files on external drives that disconnect during an operation, files being deleted while in use, and corrupted Trash entries are common triggers.
Identifying the specific file involved is the key first step.

What Error Code 43 means

Error Code 43 in macOS historically corresponds to 'fnfErr' — file not found. Despite its name, it does not always mean the file literally cannot be found. It can also appear when Finder starts an operation on a file that becomes unavailable mid-operation (an external drive disconnects, for example) or when a Trash entry points to a file that no longer exists at the recorded path.

Identify which file is causing the problem

Finder's error dialog sometimes names the file. Note the name. If you are emptying the Trash and the error occurs, the problematic file is in the Trash.

Check the Trash
Open the Trash in Finder. Look for any files from external drives that are no longer connected, or files with unusual names.
Try to locate the specific file
If you know the file name, use Command-Space (Spotlight) to search for it and confirm whether it exists.

Fixes for Trash errors

Connect any external drives mentioned
If the Trash contains files from a disconnected external drive, reconnect the drive and try emptying the Trash again.
Quit all applications
Files held open by any application cannot be deleted. Quit all apps and try again.
Hold Option while emptying
In Finder, hold the Option key and choose Finder > Empty Trash. This can bypass certain error checks and force the Trash empty.
Restart and try again
A restart releases all file locks and often allows a previously blocked Trash to empty.

Fixes for copy and move errors

If the error appeared while copying to an external drive, check that the drive is still connected and accessible.
Check free space on the destination drive.
Try copying one file at a time to identify which file causes the error.
Check if the file is locked (Command-I > Locked checkbox) and unlock it if so.
Restart the Mac and retry the operation.

Check storage health

Recurring Error 43 errors across multiple files on the same drive can indicate that the drive is developing problems. Run First Aid in Disk Utility on the affected drive. If Disk Utility finds errors it cannot repair, copy important data off the drive promptly.

Prioritise data safety

If you suspect a storage drive is failing, copy your important data elsewhere before spending time on further troubleshooting. A drive that is failing can fail completely and without warning.

Frequently asked questions

Sources and further reading

If a file is stuck in the Trash on your Mac — Apple Support

Portrait of a consumer technology researcher

Ruben Alvarez

Mac troubleshooting writer

Mac troubleshooting writer covering startup behaviour, storage, Finder problems and macOS error messages.

View profile →

Apple Support 247 is an independent publication and is not affiliated with Apple Inc. Apple, Mac, MacBook, iPhone and other Apple marks are trademarks of Apple Inc.