A file uploaded from a VM to the Vault appears in its folder, marked incomplete, as soon as its upload starts, and loses the mark once complete
VPN tunnels between VMs, including the ones batch nodes use to read the controller's drives, now encrypt traffic with AES-GCM when both VMs support it. AES-GCM needs much less CPU than the AES-CBC with HMAC-SHA256 used before, so batch jobs that read large files at the same time can run faster
VMs no longer offer the Repair corrupted database action, which could delete a VM's data when its database was damaged
NFS drives read several times faster. The VM now mounts them over four network connections with a 16 MB read-ahead
Batch nodes now reach the controller through its firewall instead of a strongSwan VPN, which raises their NFS throughput but leaves the traffic between them unencrypted. Set vpn = true in the batch section of the image config to keep using the VPN
Cancelling a Vault to VM or VM to Vault transfer in the browser, or closing the browser tab, now stops the transfer in the VM
A failed or cancelled download from the Vault into a VM no longer empties the file it was meant to replace, and no longer leaves an empty file behind
A VM to Vault upload that fails or is cancelled now leaves its partial file in the destination folder, marked incomplete, instead of an invisible file
Starting several background commands at once no longer crashes the VM controller, and a background command's result is shown only to the user who started it, with the reason it failed
On Windows VMs, moving files, running commands as a user and user-level hook commands no longer fail with a runas error. They now run under the user's own Windows account
A terminal stream that ends normally (a closed tab, a dropped connection or an exited terminal) is no longer logged as an error
