VirtualBox VM's gone after 5.1.24-00324 update

[MooieBoot]

Hi,

After the firmware update to 5.1.24-00324, my VM list in VirtualBox is empty. The vdi and sparse files are not lost (still on the Volume), but when I try to add the existing VM I get the following error:

VirtualBox error: rc=0x80004005 Extra content at the end of the document. Location: '/home/xxxx/xxxx/xxxx.vdi', line 1 (0), column 2. /home/vbox/vbox-6.1.18/src/VBox/Main/src-server/MachineImpl.cpp[499] (nsresult Machine::initFromSettings(VirtualBox*, const com::Utf8Str&, const com::Guid*)) (0x80004005)

Was vbox updated in 5.1.24-00324 update? Can't find any info on this, however I would like to have my VM's up and running and/or can I revert the firmware update?

[TMRyan]

What systems do you have installed in VirtualBox? We haven't updated VirtualBox.

[MooieBoot]

I had 1 windows VM and 2 linux vm's, but that doesn't really matter.
Somehow the "Default machine folder" within phpvirtualbox was changed and it wasn't by me.
Looks a bit like an earlier bug: viewtopic.php?f=73&t=2041

[MooieBoot]

I think the update did something to my homefolder settings and is pointing to another location (/Volume1/User/xxx) instead of /home/xxx

[mmick]

What systems do you have installed in VirtualBox? We haven't updated VirtualBox.

Sadly, why don't terramaster update virtualbox, even if it`s every 12 Months. On my fully updated F4-423, the VB version (VirtualBox 6.1.18) was released on January 19 ...... 2021 (!). I bought from Terramaster to use W10 VMs and it doesn´t work (error due to newer CPU and Virtualbox is too old and returns errors.)

[rebelo92]

continue waiting for update to Virtualbox.......