we have the same error.
Workarround: Create a VM with the default settings. Know you can change erverything what you want.
after that you can delete the first created VM. I think this is a Bug.
In VB 4.1.22 it works fine.
greetings from Germany
Hansiii