How to uninstall CrystalFetch on Mac

CrystalFetch is a free app from Turing Software that builds Windows 11 installer ISO images from UUP dump, from its GitHub project. It has no account or license. The ISO files it produces are yours and live in the folder you chose when you saved them; removing the app does not delete them, so keep the ones you still need for a virtual machine and delete the rest by hand, since each is several gigabytes. A Windows license is separate from the app and is not affected. While an ISO is being built, its source downloads files into a temporary directory, which for a sandboxed app sits inside its container, so an interrupted build can leave a large leftover there. This guide covers the disk image from the project's GitHub release and the Homebrew cask crystalfetch.

Quit and remove the app

1. Let a running download or build finish, or stop it, then check that the ISO files you want are in the folder where you saved them.
2. Quit CrystalFetch with Command + Q.
3. Open Finder, go to Applications and drag CrystalFetch to the Trash.
4. Remove the container as described in the next section.

CrystalFetch registered no login item or launch agent in the test.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

Moving the container needs Full Disk Access for Mole (System Settings › Privacy & Security › Full Disk Access); without it Mole's report asks for that permission and the container stays. To do it by hand, quit CrystalFetch, open the path in Finder and move the folder to the Trash. macOS may refuse while it treats the sandbox data as protected; grant the app doing the removal Full Disk Access, or leave the folder in place.

Check the result

pgrep -il crystalfetch
ls -d /Applications/CrystalFetch.app "$HOME/Library/Containers/llc.turing.CrystalFetch" "$HOME/Library/Application Scripts/llc.turing.CrystalFetch"

• No output from pgrep means CrystalFetch is not running. A printed line names a process still alive; quit it, or restart the Mac once.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk; the container is the likeliest survivor if macOS refused to move it.

If you installed it with Homebrew

brew uninstall --cask crystalfetch

The cask has no uninstall step beyond removing the app. Its zap list trashes ~/Library/Containers/llc.turing.CrystalFetch and ~/Library/Application Scripts/llc.turing.CrystalFetch, so brew uninstall --cask --zap crystalfetch removes both whatever you selected in Mole, and does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate: both paths are inside ~/Library and both are rows Mole listed and you left ticked. Otherwise Mole leaves --zap off and removes the rows you selected itself.

What Mole lists

Mole selects the app, the container, the Application Scripts folder and the temporary cache row. Before removing, Mole asks CrystalFetch to quit. Mole does not look at the ISO files you saved elsewhere. Status shows CrystalFetch as one row. Mole found no update channel for the app.

What this test covered

On November 9, 2026, on a second Mac running macOS 26, the test took CrystalFetch 2.2.0 (Universal) from the project's GitHub release disk image, whose checksum matched the Homebrew cask crystalfetch, copied it to Applications without running brew install, opened it once and removed it with a source-built, re-signed Debug build of Mole with every review row ticked. Mole's notarized release build was not used. Mole moved the app, the Application Scripts folder and the temporary cache to the Trash. The container stayed because the test build ran without Full Disk Access. Status showed one CrystalFetch row with 1 process. No ISO was built or downloaded. Building an ISO, an interrupted download, Homebrew and Mole's notarized release build were not tested.