Path Finder not working: what to check, in order

Something in Path Finder has stopped behaving and the obvious next move is to reinstall it. That is almost always the wrong first move, because the four most common faults live in four different places, and only one of them is inside the application bundle. A reinstall fixes that one and leaves the other three exactly as they were, while costing the time it takes to download and reconfigure everything.

The faster route is to work out which layer is broken before touching anything. There are four candidates: the macOS privacy system, a cloud sync client, the app's own preference files, and the licensing service. Each announces itself differently.

The test that saves the most time

Before anything else, open the same folder in Finder.

This one comparison separates roughly half of all reported problems from the rest. If files are missing in Path Finder and present in Finder, the fault is a permission or a view setting inside the app. If they are missing in both, the fault is macOS or the cloud service, and no amount of work on the file manager will change it. The same logic applies to wrong cloud sync badges, to a stalled copy, and to a folder that refuses to open.

Cocoatech's own troubleshooting article uses this split as its organising principle, noting for missing files that if Finder also shows them missing, the issue is caused by macOS or cloud sync rather than by Path Finder. It is a rare piece of support writing that actively tells people to stop debugging the product.

Symptom	First check	Where the fault usually sits
Licence says expired	Registration panel	Licensing service
Folder appears empty	Same folder in Finder	Full Disk Access, or cloud
Sidebar and toolbar reset	Does it survive a relaunch	Preference files
Beachballs, high CPU	Which module is open	Folder size calculation
Copy stuck at 0%	Is the file marked Locked	File flags, or cloud

A licence that reports itself expired

This is the fault with the most documented history, and it is worth knowing that history before assuming a payment problem.

The release notes record it repeatedly. Build 2211 describes an improvement to the registration, license code and subscription manager, with the note that it hopefully fixes a hard to reproduce issue which would put some users randomly back into trial mode. Version 26.1.7 lists a fix for potential incorrect invalidation of valid license keys. Earlier builds around 2129 and 2130 fixed potential subscription deactivation after a computer reboot. In other words, an activation that silently reverts is a known class of bug rather than a sign that something was bought incorrectly.

The documented repair is not a reinstall. It is a credential flush:

1. Open the menu Path Finder > Registration and click Sign Out.
2. Quit the app completely with Command Q.
3. Open Keychain Access, search for pfx, and delete the entry it finds.
4. Relaunch Path Finder and sign in again.

Deleting the keychain item is the step that matters, and it is also the step that a reinstall does not perform, because the keychain lives outside the application. That is exactly why reinstalling tends to change nothing here.

Two details are worth having ready before signing back in. A subscription has no key at all: it is tied to the purchase email address, and the password was created on first sign in, which is why the help centre advises storing it separately. A license key needs three things entered together, the key itself, the email used at purchase, and a name for the computer. Mixing the two up, by pasting a key into the subscription section, produces an error that looks like an invalid purchase.

A folder that looks empty

The order here matters, because the cheap checks resolve most cases and the expensive one is last.

Start by switching to List View with Command Option 1, or through View > As List. The support article recommends this specifically because list view sidesteps several macOS indexing issues, so a folder that is blank in column view and populated in list view is a display fault rather than a data loss. Next, right click inside the folder and choose Reset View Settings to Defaults, then refresh with Command R.

If the folder sits in iCloud Drive, Dropbox, OneDrive or Google Drive, check whether the files are actually downloaded rather than online only placeholders. Placeholder handling is the single most common source of reports that files vanished.

Only when those fail is it time for the permission reset:

Open System Settings > Privacy & Security > Full Disk Access, find Path Finder in the list, turn the switch off, wait 5 seconds, turn it on again, quit and reopen Path Finder. Source: support.cocoatech.com

Toggling the switch off and on again re-registers the app with the macOS privacy database, which can hold a stale entry after an update. Granting the permission once is not permanent in the way most people assume. The app has been chasing this for years: release notes for the Ventura era list an improved Full Disk Access detection and a redesigned Full Disk Access window, which indicates the gap is on the operating system side rather than in the app's own logic.

Google Drive deserves its own line. Direct Google Drive login inside Path Finder was removed at build 2185, so there is no account to reconnect. Access now runs through Google Drive for Desktop and the local folder at ~/Google Drive or ~/My Drive. A Drive folder that appears empty usually means the desktop client is not running.

Layout, sidebar and toolbar that will not stay put

If the window opens small every time, forgets dual pane, or loses sidebar items, try the cheap fix first: arrange the window the way it should be, then choose Window > Save As Default and relaunch.

When that does not hold, the preference files are damaged. Quit the app and remove these five, using Go > Go to Folder in Finder:

• ~/Library/Application Support/Path Finder
• ~/Library/Preferences/com.cocoatech.PathFinder.plist
• ~/Library/LaunchAgents/com.cocoatech.PathFinder.plist
• ~/Library/Caches/com.cocoatech.PathFinder
• ~/Library/Saved Application State/com.cocoatech.PathFinder.savedState

This is the reset that the support article also recommends for general strangeness: modules that will not open, panels stuck in place, missing interface elements. It costs the current layout, which is the price of the fix, so it is worth photographing the window first if the arrangement took a while to build.

One related note for anyone who upgraded recently rather than installed fresh. The 26.0 release states that some settings and options were removed as obsolete and are not preserved after the update. A setting that has gone missing since an upgrade may not be broken at all. It may simply no longer exist.

Slowness, stalled copies and stubborn deletes

High CPU and beachballs usually trace to work the app was told to do. Folder size calculation is the main culprit, since it walks entire trees in the background; disabling Calculate Folder Sizes is the first lever. After that, turn off modules that are not being used, avoid previewing very large media, and let indexing finish after an install or update rather than judging performance during it. Version 26.1.1 also fixed a longstanding hang when previewing very large text files, so an outdated build can be the cause on its own.

For a copy stuck at 0%, a Trash that will not empty, or an operation that cannot be completed, check three things in order: whether the file is marked Locked in Get Info, whether cloud files are fully downloaded, and whether the queue itself is jammed, which is visible under Window > File Copy Queue. Secure Delete Trash handles items the normal empty refuses.

Crashes have their own recent history worth knowing. Version 26.1.2 fixed crashes when the app activates after sleep or a screensaver, when opening certain file types, and when unplugging an iPhone from the Mac. If the crash matches one of those, updating is the fix rather than resetting anything.

Check the version number before debugging anything

A surprising share of reported faults are fixed in a build the reporter is not running, and the app makes this easy to get wrong because it has two update tracks.

Version 26.1.5 added an update channel selector with a Release Only option and a Release and Beta option. A Mac set to the beta track is running builds that are explicitly work in progress, which changes what a crash means. A Mac set to release only, and left alone for a few months, is missing fixes that are already published. Either way, the version number is the first fact to establish, and it sits in Path Finder > Check for updates.

The updater itself was rebuilt at build 2184, moving to the Sparkle 2.x framework for speed and security. Copies that have not been updated since before that point may be checking for updates through the old mechanism, which is a reason to download a fresh installer from the site rather than waiting for an in-app prompt.

Matching a symptom against the published notes takes a couple of minutes and often ends the investigation. Crashes when waking from sleep, crashes when unplugging an iPhone, hangs on very large text previews, a sidebar that loses its items, dual pane position not restoring on launch, and the Goto Folder shortcut not responding are all listed as fixed in specific 26.1.x releases. A fault that appears on that list is not something to reset preferences over.

When the answer is not in the app

Three situations are outside what any amount of troubleshooting will reach.

The first is the operating system version. Path Finder 26 requires macOS 13 Ventura or later, and the 11.2 line covers macOS 10.13 High Sierra upward. Odd behaviour on a Mac running Monterey with a version 26 installer is a requirements mismatch, not a bug.

The second is macOS 26 Tahoe, where interface glitches are still being worked through. The notes for build 2209 describe fixing a lot of UI glitches on Tahoe and state in the same line that this remains work in progress.

The third is documentation language. The help centre publishes in English only, a single locale, while the application itself ships in around twenty languages. Anyone searching for a fix in another language is likely to land on a machine translated copy of the article rather than the source, which is where outdated steps creep in. Checking the Languages a tool supports in its documentation, not just in its menus, is a fair thing to do before committing to it. Support itself is reachable at [email protected], with agents on business days across CEST and AMT hours, and the points that come up repeatedly tend to end up in a FAQ.

What to change first

Run the Finder comparison before anything else, because it decides which of the four layers to work on and takes ten seconds. If the answer keeps coming back as permissions and windows rather than files, the thing to reconsider is how many windows the work is spread across, which is the question Atriens starts from.