Finder not responding on Mac? Protect file work first

Protect active file work before changing Finder

A spinning pointer or a Finder window marked Not Responding does not tell you whether macOS, one folder, a file provider, a network share, or a storage device is waiting. Preserve the work before testing.

Save documents in other responsive apps. Write down the Finder task, source path, destination path, file count or approximate size, and the time it stopped moving. If a copy dialog still changes, wait. If an external drive's activity light is flashing or the drive is making normal access sounds, do not disconnect it just to test the cable.

• A copy or move is active: do not start another transfer. Preserve the source and destination until you know which operation completed.
• A deletion is pending: do not empty Trash or run a cleanup app.
• A cloud folder is involved: do not sign out, remove the account, or delete cloud-only files as a first step.
• A network share is involved: record the share and connection type before disconnecting it.

A synced folder is not automatically a separate backup. Confirm that important files exist in another protected location before storage repair, account changes, or service.

Find whether one window, one path, or all Finder is stuck

Check the smallest useful scope without opening many new windows. Does one folder stall while another local folder opens? Does the desktop respond? Can you select a file without previewing it? Is the problem limited to search, Quick Look, tags, a sidebar item, or an external location?

Record the macOS version from Apple menu > About This Mac and the exact path that triggers the wait. Also note what changed recently, such as a macOS update, a new external drive, a VPN, a cloud-storage update, or a Finder extension. Timing is evidence to test, not proof of cause.

• One folder or file stalls: keep its contents, permissions, metadata, and backing storage in scope.
• One external or network path stalls: compare a small local folder before blaming Finder itself.
• Every Finder window stalls: a Finder relaunch and startup-software comparison become more useful.
• Other apps also freeze: widen the scope to storage, memory pressure, system software, and hardware. Do not treat it as a Finder-only result.

Relaunch Finder once and record the result

Apple says Finder stays open, so its Force Quit action is Relaunch. Press Option-Command-Esc, select Finder, and choose Relaunch. Use this once after protecting active work. Do not repeatedly relaunch while a transfer, backup, or sync operation may still be writing.

When Finder returns, open one simple local folder first. Then open the original location and repeat only the smallest action that caused the stall. Record whether the same path, file, view, or search triggers it again.

If Finder does not return or the whole Mac is unresponsive, a normal restart is the next supported step. Wait for drive activity to settle when possible, use Apple menu > Restart if the menu responds, and avoid holding the power button unless ordinary controls are unavailable. After restart, do not reopen every old window at once.

Compare local, external, network, and cloud paths

Use a small, non-secret test file that already has a backup. Do not use the only copy of an important file. Open or copy it through one path at a time.

Unmount an external volume before disconnecting it when Finder is responsive. If eject does not complete, do not pull the cable during obvious activity. A clicking drive, repeated disconnect, disk-read warning, or missing volume needs a backup-first storage path rather than more copy tests.

If iCloud Drive is the only affected location, keep local file availability, account state, and Apple service status separate. Do not remove files or sign out to force a new sync.

Check current updates and available space

Save work and confirm a separate backup, then install compatible macOS and app updates through their supported paths. On a managed Mac, follow the organization's update policy. Record the version before and after the update so a later support case has a clear timeline. If macOS itself will not update, use the macOS update guide instead of forcing the installation.

Apple's Storage view can show which categories use space. Open Apple menu > System Settings > General > Storage on current macOS releases. Review space before deleting anything. Do not remove unknown library files, caches, snapshots, or application support folders to chase a Finder delay.

Very low free space can affect ordinary work, but one storage number does not identify the cause of a Finder stall. Preserve the amount and repeat the smallest safe test after updates. If the problem follows one path, keep that path in scope even when local free space looks adequate.

Test login items, Finder extensions, and Safe Mode

System Settings > General > Login Items & Extensions lists software that opens at login, runs in the background, or adds extensions. Record the current state before changing it. Disable one relevant, nonessential item at a time, restart normally, and repeat the same Finder action. Re-enable it if the test does not change the result.

Do not disable security, backup, device-management, accessibility, or workplace software without authorization. A file-provider or Finder extension may be essential to reach its data, so confirm the provider's current support instructions first.

Safe Mode can compare startup-loaded software without uninstalling it. Apple documents different steps by processor:

Apple silicon: Shut down. Press and hold the power button until startup options appear. Select the startup volume, hold Shift, then choose Continue in Safe Mode.

Intel: Start or restart the Mac and immediately hold Shift until the login window appears.

Test one local folder in Safe Mode. Some network, cloud, graphics, and peripheral features may behave differently there, so a Safe Mode result is a branch, not a diagnosis. If Finder works only in Safe Mode, startup-loaded software becomes more likely. If it still stalls on the same local path, keep macOS, storage, and hardware branches open.

Collect a Finder sample without sharing private paths

Activity Monitor can capture a sample or spindump for an unresponsive process. Open Activity Monitor, select Finder, use the More button, then choose Sample Process or Spindump as appropriate. Capture one report while the problem is present. Do not terminate unrelated processes to make the list shorter.

A sample can contain account names, personal paths, mounted share names, filenames, server addresses, and proprietary information. Save it in a protected location. Review and redact it before sharing it with an app developer, administrator, Apple, a repair provider, or a public forum.

The report can show where Finder was waiting, but one stack trace is not a reliable automatic diagnosis. Pair it with the exact time, path type, macOS version, recent changes, and the local-versus-external comparison.

Use Disk Utility First Aid carefully

Apple says to back up data before using First Aid. Close documents and apps where practical. Open Disk Utility from Applications > Utilities, choose View > Show All Devices, and use Apple's documented order for the affected storage device: start with the last volume, then work upward through other volumes, containers, and the device itself.

First Aid is not a data-recovery tool, and a successful result does not prove every file or hardware component is healthy. If Disk Utility cannot see the device, First Aid reports an error it cannot repair, the drive disconnects, or the data has no separate backup, stop and get storage-specific help.

Do not erase or reformat a volume as part of this Finder guide. Apple lists erase as a later action for some repair failures, but it destroys the current file-system contents. That decision belongs after backup or recovery planning, not before.

When to get help

Contact the cloud, storage, VPN, or app provider when the stall follows one current extension, service, or network path and local Finder work remains stable. Give them the version, exact time, repeatable path, and a redacted sample only when needed.

Contact Apple support or arrange service when Finder remains unresponsive across local paths after a relaunch, normal restart, current updates, and the correct Safe Mode comparison. Get help sooner for missing disks, repeated disconnects, read errors, unusual drive sounds, startup trouble, rapid system-wide freezes, heat, odor, swelling, liquid, or impact history.

If the Mac recently restarted unexpectedly too, use the Mac restart guide to preserve the separate restart evidence. For a Microsoft app that shows a specific code rather than a Finder stall, see the Office for Mac 0x0 guide.

Where OmniMend fits

On a supported Apple Silicon Mac, OmniMend 1.7.16 can organize local, non-secret system, application, update, storage-space, and symptom-timeline evidence around the Finder problem. Its Mac build is diagnostic and local. It does not repair Finder or storage, recover files, interpret a spindump, erase a disk, manage cloud accounts, or support Intel Macs.

Apple's tools and the affected storage or file provider remain the primary path. If you want a separate local evidence record on Apple silicon, review what OmniMend can do or download OmniMend. Keep a separate backup and review every report before sharing it.