VB doesn‘t start after update 6.0

[Bob_Bob]

Hello,
I have a Windows 10 VB on a Linux Host and updated to virtualbox 6.0. The follows error occurs when I try to start the VB:

Für die virtuelle Maschine Win konnte keine neue Sitzung eröffnet werden.

The virtual machine 'Win' has terminated unexpectedly during startup with exit code 1 (0x1).

Fehlercode:NS_ERROR_FAILURE (0x80004005)
Komponente:MachineWrap
Interface:IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Has anyone an idea what to do?

Thanks
Bob

[socratis]

We need to see a complete VBox.log, from a complete VM run, where the problem occurs:

• Start the VM from cold-boot (not from a paused or saved state) / Observe problem / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[Bob_Bob]

Unfortunately no log is created.

[mpack]

Unfortunately no log is created.

It couldn't get as far as the reported error message if it didn't produce a log. Look in the "Logs" subfolder of the VM folder.

[Bob_Bob]

It creates really no logs in the subfolder of my VM. The only thing I cloud create was a BugReport.

I also uninstalled with apt purge and reinstalled VB 6.

[socratis]

Can you completely remove/uninstall/delete/purge what you have already as far as VirtualBox goes? Not your VMs of course, just the program. And then do a clean install of the official version from the Linux Downloads section of VirtualBox.

[Sarke]

Try

Code: Select all

sudo apt autoremove

or

Code: Select all

sudo apt remove virtualbox-dkms

For me the virtualbox-dkms was left from version 5, and it was interfering with version 6.