a while ago I upgraded my VBox installation from 6.1.38 to 7.0.6. While this worked somewhat, I experienced subpar performance (everything was very sluggish) and a failure to reboot my Windows 10 VM after upgrading it to version 22H2. Luckily I made a snapshot before so I retried the whole thing to no avail (Windows 10 was always "hanging" shortly before the screen changes from black to blue usually, e.g. the small wheel kept on rotating forever without any HD access visible).
So I decided to downgrade to VBox 6.1.38 hoping it would resolve the situation …
However, after two reboots of the host OS (Ventura 13.2 (Darwin MBP15.local 22.3.0 Darwin Kernel Version 22.3.0: Thu Jan 5 20:53:49 PST 2023; root:xnu-8792.81.2~2/RELEASE_X86_64 x86_64)) to enable the kexts I always get those kind of errors now, regardless which VM I try to start:
Code: Select all
Für die virtuelle Maschine Windows 10 konnte keine neue Sitzung eröffnet werden.
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1).
Fehlercode: NS_ERROR_FAILURE (0x80004005)
Komponente: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Code: Select all
Für die virtuelle Maschine Windows 7 konnte keine neue Sitzung eröffnet werden.
The virtual machine 'Windows 7' has terminated unexpectedly during startup with exit code 1 (0x1).
Fehlercode: NS_ERROR_FAILURE (0x80004005)
Komponente: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
Is there a way to get my VMs working again?
TIA,
Lars