How to uninstall MuMu Player Pro (MuMu 模拟器 Pro) on Mac

Save wanted emulator data before removing MuMu Player Pro (MuMu 模拟器 Pro). The current Mac cask identifies this edition, distinct from other MuMu products. Stop guest systems and quit both launcher and client before copying local data; keep ~/Library/Application Support/com.netease.mumu.nemux until wanted contents have a checked backup. This recorded run did not create a VM or install games, so it does not establish a complete game-save backup flow.

Remove the client and launcher

The recorded setup expanded MuMuLauncher.app into MuMuPlayer.app. After saving data and quitting, remove only those confirmed app copies from Applications. Keep similarly named apps from other editions and shared data until ownership is clear.

For Homebrew:

brew uninstall --cask mumuplayer

Ordinary removal handles the cask's MuMuPlayer app; the recipe has no separate launcher artifact. Zap targets support, matching caches/HTTP/WebKit/state, broad MuMu preference patterns and matching group containers/scripts. Direct zap ignores Mole choices, so review the scope and backup before using it; group names do not establish exclusive ownership by themselves.

ls -ld "/Applications/MuMuLauncher.app" "/Applications/MuMuPlayer.app"
ls -ld "$HOME/Library/Application Support/com.netease.mumu.nemux"

Printed paths remain. Missing-path errors apply only to those locations; permission errors leave them unknown. The checks do not verify VM or game-save recovery.

What Mole lists

The selected apps and exact identifier leaves are normally checked when present and unprotected. The exact team.group.app group can be selected by default, but deletion still checks independent ownership; uncheck it when keeping its contents. Remove data and settings with apps is off by default, with shared and protected stores retaining their boundaries.

What this test covered

The official launcher/client and selected data were removed with source-built Mole on October 3, 2026. Launch reached the sign-in page without login, agreement acceptance, VM creation or game downloads. The shared group container and scripts were retained after ownership refusal. Populated VM recovery and Homebrew-managed uninstall were not tested.