Bloons+
WIKI / SETUP

VM connection

Bloons+ reference · updated 6 October 2026

Where each part runs

The main PC displays controls. The guest runs BTD6, the replay engine and relevant save readers. Simulated input remains inside the guest while you use the main desktop.

Setup checks

Open Settings → Game & VM to see what is ready and which step needs attention. Setup checks existing components before installing them, then validates each finished step before continuing. Steam sign-in stays in the Steam window inside the VM.

What each setup state means
StateWhat to do
PendingThis step has not started. Use the setup action when it becomes the next step.
CheckingBloons+ is checking readiness. If Steam is not signed in, finish sign-in and the BTD6 installation in the VM.
Already readyThe existing component passed its check; no installation is needed.
Installing / RetryingWait for the current action. Retrying means setup is attempting this step again.
ValidatingThe action finished; Bloons+ is checking that its result is usable.
CompleteThis setup attempt completed the step and verified its readiness.
Restart requiredRestart Windows, then reopen Bloons+. The app will not reboot your PC itself.
FailedRead the failed step and its error. Correct the cause, then retry. Later steps have not been started.

Some Windows feature changes need administrator permission. Completed checks are detected again after reopening; an interrupted installer may still need attention in the VM window.

Current installers lock their installation folder while working. A repeated setup request waits for the active installer; it reuses a completed update only when the installer files match. A duplicate installer cannot replace the active result. If setup times out, inspect its log in the VM before retrying. Older installers and interrupted package processes may still need manual attention.

Updating

Use Update Bloons+ in VM from the main PC when no replay is active. A GitHub push does not update installed software. The update checks the guest app connection before reporting completion. If files were updated but connection validation failed, inspect the VM app and reconnect before starting a replay.

SSH authentication

Permission denied indicates an identity or provisioning problem, not necessarily a crashed game. Check the selected guest, deployed SSH key and signed-in desktop. Never share private key files.

Suggest a correction ↗ · Back to wiki