This error comes from running a VM with a saved state on a different Virtualbox version than when the VM state was saved. Saved states don't survive a Virtualbox version change.
If you don't care about the unsaved data in the VM, right-click the VM in the list of VMs and click Discard Saved State.
If you do care about the unsaved data, you have to downgrade Virtualbox to the version you had when you save-stated the VM.
ns4444 wrote:Kali is not booting up anymore (I get a blackscreen).
Kali is based on Debian. Ubuntu is also based on Debian. Ubuntu goes to blackscreen for known reasons, even on physical PCs. While it's a logical fallacy, it could be that Kali might do the same thing, if Debian does the same thing.
Better to get the VM running from cold boot, then we can try to solve the Kali blackscreen.
ns4444 wrote:I tried restoring from snapshots
If you thought that the snapshots were backups, then like Mad Dog Tannen said to Marty in Back to the Future III:
You thought wrong, dude.
Snapshots are not backups in any sense and cannot be used to restore a broken VM. They are more like time travel markers in the life of a VM. Snapshots make a VM more delicate.
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.