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.
Uninstall by installation method
- Windows
.exeinstallation (TurboismInstaller-<version>.exe): rununinstall.exein the Turboism home directory. - Portable ZIP installation (Windows manual setup, macOS, or Linux): portable archives have no uninstaller and do not enable official-BAT integration. Close Cubism completely and delete the Turboism folder.
- Legacy installations (0.44.0 and earlier): installations made with the retired Java IzPack installer ran
java -jar <home>\Uninstaller\uninstaller.jaron Windows/Linux oruninstall.commandon macOS.
Procedure for .exe installations:
- Close Turboism and Cubism normally.
- Run
uninstall.exein the Turboism home directory. - Follow the confirmation steps.
- When asked, choose whether to keep
config.json(user configuration). The checkbox is checked by default; uncheck it if you want to deleteconfig.json. - After completion, confirm that Cubism no longer starts through Turboism shortcuts or managed launch entries.
What is removed and what is kept
- The uninstaller removes installer-owned runtime files, managed launch shortcuts, registration state, and runtime
logs,state, andcachedirectories. config.jsonis kept by default and is removed only if you explicitly uncheck the retention box.- The uninstaller removes only the first-party plugin JARs deployed by the installer; unknown files and third-party plugin JARs are preserved.
- Persistent plugin data under
data/<pluginId>/and configuration underconfig/<pluginId>/are not deleted by the uninstaller.
Review the remaining Turboism directory after uninstalling and back up anything you wish to preserve.
Launcher integration
Official Cubism startup BAT integration is pre-selected by the Windows installer. If it was applied, the uninstaller automatically restores the original BAT file from its hash-guarded backup. If those files were edited manually after installation, cleanup reports a conflict and preserves both state and backups instead of overwriting your changes.
Before and after
Read Update Policy before replacing an installation. If an update or installation change failed, start with Downgrade and Recovery.