Uninstall
Remove Turboism with its own uninstaller while deciding what personal configuration to keep.
Use the uninstaller generated by the installer that installed your build. Do not remove files while Turboism or Cubism is running.
Use the installer's uninstaller
-
Windows,
.exeinstallation — rununinstall.exein the Turboism home directory. -
Windows,
.jarinstallation — run:java -jar <home>\Uninstaller\uninstaller.jar -
macOS,
.jarinstallation — double-clickuninstall.commandin the home directory, or run it in a terminal.
Then:
- Close Turboism and Cubism normally.
- Start the matching uninstaller.
- Follow its confirmation steps.
- When asked, choose whether to keep your configuration. Keep it if you may reinstall or need the same preferences later; remove it only if you no longer need it and have saved anything important.
- After completion, confirm that Cubism no longer starts through the removed installation.
What is removed and what is kept
- The uninstaller removes installer-owned files plus the runtime
logs,state, andcachedata. config.jsonis removed only when you choose to delete it. Both the NSIS and Java uninstallers default to keeping it.- Unknown files and third-party plugin JARs are preserved, because the uninstaller does not delete material it cannot identify as its own.
- Plugin data under
data/<pluginId>/is not silently discarded.
Review the remaining Turboism home after uninstalling and back up anything you may want. Do not treat removal as a way to erase unrelated host files or projects.
Launcher integration
If you enabled integration with the official Cubism startup BAT, that integration is restored from its hash-guarded backup during removal. If the managed files were edited afterwards, cleanup reports a conflict and preserves the state and backups instead of overwriting your changes.
Before and after
Read Update Policy before replacing an installation. If an update or mode change failed, start with Downgrade and Recovery rather than assuming an older build can be safely restored.