Delete of a VM does not delete unattended files, so can't recreate VM

[Justinh]

If you create a VM using unattended installation, then you RMB on the VM in the hypervisor -> Remove -> Delete All, the unattended files remain. then if you try to create a new VM using the same VM name, you get an error because of the left over files.

[Gene77072]

I am having the same problem with Linux Host and Guests. The leftover files are named: Unattended-df7776e3-731a-43e7-8b26-7df309cb8f8c-aux-iso.viso, Unattended-df7776e3-731a-43e7-8b26-7df309cb8f8c-preseed.cfg, Unattended-df7776e3-731a-43e7-8b26-7df309cb8f8c-grub.cfg, Unattended-df7776e3-731a-43e7-8b26-7df309cb8f8c-vboxpostinstall.sh . They are located in the VirtualBox VMs directory in a subdir named for the machine. In order to restore the ability to run Unattended install again for this machine, I delete the leftover directory.

[galitsyn]

Hi guys,

We just released VirtualBox 7.0.22 and 7.1.4. The issue should be fixed in this release. You can give it a try on Downloads page.