How to uninstall muCommander on Mac

Back up muCommander bookmarks and connection setup, and finish any file transfers before uninstalling. The app can access local and remote files, but removing the file manager is separate from deleting those files or closing the remote accounts.

Quit and remove the app

Quit muCommander after transfers finish, then move muCommander.app from Applications to the Trash. Leave files on your disks and servers where they are. Do not remove a shared Java runtime merely because muCommander uses Java.

Review the local data

In Finder, choose Go › Go to Folder and open each exact path below. Copy anything you need first, then move only the app-owned item you have decided to discard to the Trash. These locations come from the Homebrew removal list or the recorded local check; a missing location needs no cleanup.

Check the result

These commands only list the app and the locations discussed above. The app filename comes from the cask; adjust it if your official-download bundle has a different name.

ls -ld "/Applications/muCommander.app"
ls -ld "$HOME/Library/Preferences/muCommander"

An entry printed by ls still exists at that path. No such file or directory means that exact item is absent; Permission denied or Operation not permitted means the check could not establish its state. A retained data folder is expected if you chose to keep it. This check does not search every disk or cloud account.

If you installed it with Homebrew

Uninstall without running zap:

brew uninstall --cask mucommander

This removes Homebrew's managed app artifacts without applying its zap list. A “not installed” error means Homebrew has no matching cask installation; use the Finder route for a manually copied app.

The live cask source names these additional zap targets:

• ~/Library/Preferences/muCommander

Some targets can hold settings or personal data. Keep the paths you still need and back them up before considering brew uninstall --cask --zap mucommander. That direct command applies the cask's entire zap list regardless of Mole's checkboxes. Mole uses zap only when its complete scope passes its selection and shared-data checks; unchecked, shared, out-of-boundary or unsupported targets suppress zap, while selected remnants use Mole's own removal path.

What Mole lists

Mole selects the exact display-name preferences folder by default, so uncheck it if you want to retain bookmarks or connection setup. Matching app caches are selected by default. This selection does not cover the contents of connected servers or every Java application. These defaults describe the app-data option switched off. Opting into Remove data and settings with apps also selects eligible reviewed app data; shared stores and protected data retain their individual review or protection.

What this test covered

The official Apple-silicon bundle, selected preferences folder and temporary cache were removed on 21 September 2026. The record does not verify authenticated cloud connections, remote-file preservation or removal of a shared Java runtime. Homebrew instructions were checked against the current cask, but this record does not establish a Homebrew-managed uninstall or removal of every possible leftover.