How to uninstall Arturia Software Center on Mac

Save audio projects and presets before removing Arturia Software Center. The official product page describes management of instrument installations and activations; removing ASC is separate from deleting instruments or changing licenses. Finish product operations and quit audio hosts and ASC before removing its service.

Remove the manager and its confirmed agent

For Mole, review the installed manager and its confirmed system launch-agent row, then complete the quit-and-remove flow. The recorded app is /Applications/Arturia/Arturia Software Center.app; keep other Arturia apps and shared instrument data.

For Homebrew, the current cask supports:

brew uninstall --cask arturia-software-center

Ordinary uninstall unloads ArturiaSoftwareCenterAgent and acts on the fonts and resources package receipts. Zap additionally deletes the system ASC and ArturiaSC folders and targets user cache, saved state and WebKit, removing the Arturia parent only if empty. Direct --zap ignores Mole choices. This is a manager-package flow, not removal of every instrument or license.

ls -ld "/Applications/Arturia/Arturia Software Center.app"
ls -ld "/Library/LaunchAgents/com.Arturia.ArturiaSoftwareCenterAgent.plist"

Printed paths remain. Missing-path errors apply only to those locations; permission errors leave them unknown. A missing plist alone does not prove a loaded service stopped, and these checks do not verify instrument recovery.

What Mole lists

The selected app and confirmed own agent can be selected, with process and safety checks before deletion. Keep the Arturia parent, other products and shared Juce lock files. Remove data and settings with apps is off by default; shared content remains outside automatic selection.

What this test covered

The maintainer-installed official package was removed with official Preview Mole on October 3, 2026. App, system agent and selected temporary cache were absent afterward, with no product process or startup row. Shared Juce lock files remained. No login or instrument installation was performed; populated project recovery, license changes and Homebrew-managed uninstall were not tested.