How to uninstall UU Remote on Mac

End remote sessions, save work on the remote computer and keep another way to reach it. Removing this Mac’s client is separate from deleting remote files. The paths below were observed in a read-only inspection of the installed Mac app. This is not a completed uninstall or a data-recovery test. Product reference

Quit and remove the app

The official pkg installs background services. Use the removal flow supplied with that installed version; trashing only the app does not establish that its agent and daemon are gone. If there is no documented removal entry, keep the app available and contact NetEase support instead of manually deleting launchd files.

Review local data

Use Shift + Command + G in Finder to inspect each location. Skip missing paths. These directories existed during the local inspection; their personal contents were not read. Keep settings, sign-in material and user data unless you have verified a wanted backup, and never delete an entire vendor parent by name.

Check the result

if [ -e "/Applications/UURemote.app" ]; then
  printf '%s\n' 'App bundle still exists'
else
  printf '%s\n' 'App bundle not found at this path'
fi
ls -ld "$HOME/Library/Application Support/com.netease.uuremote"

The first check explicitly reports whether the app bundle remains at that path; absence does not prove all data was removed. An ls listing means the data path survives, No such file means it is absent, and Permission denied leaves its state unknown.

If you installed it with Homebrew

brew uninstall --cask uuremote

This uninstalls the cask without zap. It still processes its declared apps, links or background components, so it is not a guarantee of app-only removal.

The ordinary cask uninstall stops com.netease.uuremote.agent and com.netease.uuremote.daemon, and removes the app, /Library/Caches/UURemote, /Library/LaunchAgents/com.netease.uuremote.agent.plist and /Library/LaunchDaemons/com.netease.uuremote.daemon.plist without zap. Administrator authorization may be required.

Adding --zap directly runs the cask’s data-removal list without consulting Mole’s checkboxes. Listed paths include ~/Library/Application Support/com.netease.uuremote, ~/Library/Caches/com.netease.uuremote, ~/Library/Caches/com.netease.uuremote.server, ~/Library/HTTPStorages/com.netease.uuremote, ~/Library/HTTPStorages/com.netease.uuremote.server, ~/Library/Preferences/com.netease.uuremote.plist, ~/Library/Preferences/com.netease.uuremote.server.plist, ~/Library/WebKit/com.netease.uuremote. Keep or back up wanted data before choosing zap.

Mole uses zap only when its entire scope passes review. Unchecked, shared, out-of-boundary or unrecognized entries suppress zap; selected entries can still use Mole’s own removal path. Homebrew cask

Zap also includes the UURemote folder in the Shared folder under Users. Do not run zap if that folder contains settings or data you want to keep.

Accounts and saved files

Removing the local app is separate from deleting an account or cancelling a subscription. Keep wanted documents, remote files and independent components. Account deletion, subscription cancellation and backup restoration were not tested.

What Mole lists

With the include-app-data preference off, these locally verified paths are selected by default. They can still contain settings or user data; back them up or uncheck them before removal: ~/Library/Application Support/com.netease.uuremote, ~/Library/Preferences/com.netease.uuremote.plist.

These paths are listed but are not selected by default: ~/Library/HTTPStorages/com.netease.uuremote.server.

Opting into app-data selection can also select eligible reviewed data. Shared stores, protected personal profiles and agent archives retain their individual-review or protection rules. These observed paths are not guaranteed to exist for every installation channel.

Mole also lists /Library/Caches/UURemote as a system cache requiring individual review. It is unselected even when app-data selection is enabled.

What this test covered

The installed Mac version was inspected on October 4, 2026 through a read-only review export and path comparison. It was not reinstalled, quit or uninstalled, and the removal commands in this guide were not executed. This establishes review coverage and selection policy, not deletion permission, post-uninstall residue, account sync or data recovery.