Troubleshoot without losing your setup

Start with reversible checks

1. Record the visible error and what you were trying to do before dismissing it. Remove private names, paths, server details, and credentials from any report.
2. Check the active pane, current path, selection, and destination. Identical folder names in different volumes or cloud services are not the same directory.
3. Clear a listing filter and check Show Hidden Files when items seem to disappear. For search results, verify query, mode, scope, and indexing limits.
4. Check whether the folder is local, remote, read-only, disconnected, or online-only. These distinctions explain many unavailable actions.
5. Wait for a current operation to finish or cancel it once before retrying. Repeatedly clicking an operation can make its outcome harder to understand.

Match the symptom to the right setting

• A drag copies instead of moving: inspect the drag-default preference, modifier keys, source application, and provider capabilities. Use an explicit Move To… for comparison.
• Repeated prompts: distinguish an incoming request, a move confirmation, a filename conflict, and an extension warning. Record the prompt title and the action that triggered each one; do not disable unrelated safety prompts blindly.
• Unexpected dates: inspect Preferences > Layout > Dates. Relative date labels and date grouping are separate choices.
• A command is disabled: select an appropriate item and verify whether the command requires a local folder, supported file type, model, or provider.
• Scroll or location jumps during a file change: record the view, sort/group keys, open tabs, operation, and whether the change came from Pathem or another application. Use disposable files for a reproduction.

Check access and availability

1. For protected local folders, review the installed app's Full Disk Access entry and follow any macOS relaunch request.
2. For a cloud file, verify it is downloaded when an operation needs contents. For an external disk, check whether macOS mounted it and whether it is writable.
3. For a remote site, separate authentication, host/certificate verification, connectivity, and path permissions. Keep secrets out of screenshots and exported diagnostics.
4. For an app-specific opening or paste problem, compare the same harmless file in the same receiving app. Record whether you used Copy, Copy Name, a drag, or another action.

Write a useful report before resetting anything

Include the Pathem build/version, macOS version, view mode, local/cloud/remote context, exact steps, expected result, actual result, and whether the problem repeats. A short recording of a disposable example is more useful than an unredacted screenshot of private files.

If restart is appropriate, finish transfers and save editor work first. Keep a backup of any configuration you intend to preserve. Reset Pathem Data is a separate destructive cleanup workflow that can clear settings and restore folder-opening behavior; it is not a routine diagnostic step.

A successful workaround does not prove the original cause. Report what the workaround changed so a later fix can address the actual mechanism rather than hide the symptom.