Symptom
Finder shows Error Code 8058 when trying to move or copy a file.
- Error 8058 is a Finder operation failure often related to a file being in use by another process, or a problem with the source or destination volume.
- Quitting apps that may be using the file and restarting Finder are the simplest first steps.
- The error can also appear when the destination volume has a problem.
What Error 8058 indicates
Error 8058 is a general Finder error code in the 'miscellaneous Finder error' range. It can indicate that the file cannot be read from the source, cannot be written to the destination, or that another process has the file open and is preventing the move.
Like many Finder error codes, 8058 is not precise about the cause. The situation in which it appears — which file, which operation, which volumes — provides more diagnostic information than the number itself.
Check whether the file is in use
If an application has the file open, Finder may be unable to move it. This is common with documents in productivity apps, preview panes in other Finder windows, or media files being played back.
Quit applications that may be using the file
Close any apps that have the file open: Pages, Word, Preview, Music, or any app that previews file contents.
Close other Finder windows
If another Finder window is previewing the same file, close it.
Retry the operation
Attempt the move or copy again with those apps closed.
Restart Finder
Finder can accumulate state problems during a long session. Restarting it is quick and safe:
Hold Option and right-click Finder in the Dock
A context menu appears with a Relaunch option.
Choose Relaunch
Finder quits and restarts. No data is changed.
Retry the file operation
Attempt the move or copy after Finder has relaunched.
Volume and destination checks
- Check free space on the destination volume. A volume with very little free space may produce errors on file operations.
- Eject and reconnect any external drive involved.
- If the destination is a network share, reconnect to the share.
- Check the source file for the Locked attribute in Get Info (Command-I).
Test in Safe Mode
If the error persists across multiple files and operations, booting into Safe Mode (which loads a minimal version of macOS with third-party extensions disabled) can help establish whether a third-party extension or background process is causing the interference. If the operation succeeds in Safe Mode, a background process or extension is the likely cause.
Safe Mode varies by hardware
The method for starting in Safe Mode differs between Intel Macs and Apple silicon Macs. Refer to current Apple documentation for your specific hardware.
Frequently asked questions
Sources and further reading
- Mac error codes — Apple Developer Documentation

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.
