How to uninstall NoMachine on Mac
Before removing NoMachine, save and copy your connection settings and any local session recordings to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
For a complete NoMachine installation, the vendor’s Mac uninstall guide says moving NoMachine.app to Trash triggers its automatic nxuninstall.sh removal. End remote sessions first and let that procedure finish before removing support files or emptying Trash. If the automatic procedure was interrupted and the app is already absent, the vendor documents this recovery command. Keep that script available until removal completes.
sudo "/Library/Application Support/NoMachine/nxuninstall.sh"
Quit and remove the app
Finish current work and quit NoMachine. Check Activity Monitor for its process before removing the app in Finder. In Applications, move NoMachine.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'NoMachine|nxserver|nxplayer|nxnode'
No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.
If you installed it with Homebrew
Use the installed cask receipt and uninstall without zap.
brew uninstall --cask nomachine
Ordinary uninstall manages NoMachine launch services, package receipts and the app; its automatic uninstaller must finish before you remove support files. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.
/Library/Application Support/NoMachine~/Documents/NoMachine~/Library/Preferences/com.nomachine.nxdock.plist
A direct brew uninstall --cask --zap nomachine runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.
What Mole lists
Mole lists the application and attributable remnants it can inspect, including crash reports. Exact bundle-identity preferences and caches are normally selected by default when present; cask-only data is offered for review. This application-payload test does not establish server, launch-service or helper coverage. Keep ~/Documents/NoMachine as user data until you have reviewed and backed it up.
These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.
What this test covered
The September 21, 2026 record covers the following test. Only the nxplayer payload was extracted from the official personal-edition DMG. nxserver installer scripts were not run and no server helper was installed. The app crashed instead of successfully launching; the app and crash reports were removed. Full server installation, remote connections and automatic server uninstallation were not tested.