Uninstall Windows App on Mac

Record connection names, gateways and credentials you will need again, using your organization’s approved method. Removing this Mac client does not delete the remote Windows PC or cloud workspace, but local client settings may be hard to reconstruct. If a work account manages this Mac, check its policy before uninstalling. This guide covers the app copied from the official package tested on September 19, 2026.

Quit and remove the app

Disconnect active remote sessions, quit Windows App, and move Windows App.app from Applications to Trash. This guide concerns the Mac client, not the old Windows operating system or the remote computer. If Microsoft AutoUpdate is also installed, decide separately whether another Microsoft app still needs it. For current connection and account behavior, use Microsoft’s Windows App instructions. Do not cancel a workplace subscription or delete a remote resource as part of uninstalling this client.

Review the app's own data

The Homebrew cask identifies ~/Library/Containers/com.microsoft.rdc.macos, matching app scripts and ~/Library/Group Containers/UBF8T346G9.com.microsoft.rdc. The last folder is a separate Microsoft app group and can hold client state. Inspect it before removal; leave other Microsoft group containers and shared Office data alone. The official product page describes the product; the Homebrew cask supplies the installation and zap paths. Keep anything you cannot identify until its owner is clear.

If you installed it with Homebrew

To remove the cask without applying its whole zap list, use:

brew uninstall --cask windows-app

Homebrew's separate brew uninstall --cask --zap windows-app also acts on every path in the cask's zap list. It does not consult Mole's selected files. Review the paths above before choosing that action. Mole checks the cask deletion list and suppresses zap when it reaches unchecked, shared, unknown or unsupported data; selected associated files still follow Mole's own deletion path.

Check the result

These Terminal commands only inspect the current state:

pgrep -il "Windows App"
ls -ld ~/Library/Group\ Containers/UBF8T346G9.com.microsoft.rdc

No pgrep output means no matching process; a hit may indicate an active client. ls output means the group container remains, which says nothing about the remote workspace. ls reports “No such file or directory” for an absent path; a permission error requires separate investigation.

What Mole lists

Mole selects the exact app container and scripts when it can prove ownership. A product-scoped group container declared by the signed app can be listed for review, but starts unchecked; inspect this Microsoft container separately. Mole does not remove a remote workspace or another Microsoft updater.

What this test covered

On September 19, 2026, the Windows App .app was copied from the official package and removed. The full installer and Microsoft AutoUpdate were not installed in that test. The short UBF8T346G9.com.microsoft.rdc group container remained, so this is not evidence of a complete package uninstall or signed-in workspace cleanup.