VD#0: DEK is missing Log Attached

[wtfcowisown]

VM worked perfectly before. VM files stored on separate internal hdd, VirtualBox on my ssd. Had to wipe my ssd, so I reinstalled VirtualBox. Tried the same version I used before, and the newest. No luck with either. (5.2.26 & 6.0.4 respectively)

VM not launching anymore. Stays paused until I manually shut down.

[Socratis]

Replying to wtfcowisown:

VM files stored on separate internal hdd, VirtualBox on my ssd. Had to wipe my ssd, so I reinstalled VirtualBox.

When you talk about "VM files", what exactly do you mean? All the VM files, or just the VDIs? Because here's the error that you're getting:

00:00:05.227473 VD#0: DEK is missing
00:00:05.227530 VM: Raising runtime error 'DrvVD_DEKMISSING' (fFlags=0x6)

And here's I think what happened...

• You encrypted your VMs, but the VDIs were in the HDD, and the definition, the "recipe", the ".vbox" files were on their default folder in the SSD.
• When you wiped out the SSD, you wiped out the ".vbox" files, leaving the VDIs without their encryption key, which is stored in the ".vbox" file, not in the VDI itself.
• You then tried to recreate the setup, by creating a new VM and attaching the existing VDI to the new VM.

That is going to fail. And unfortunately, unless you restore your original ".vbox" files from a backup, you're out of luck.

BTW, it's usually better and faster, if issues get first addressed in the ​VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help you, me, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

[wtfcowisown]

The Vbox file is in the folder on the second hdd. How do I manually point the vm to it?

[Socratis]

Post the .vbox file here first so we can take a look at it.

Also, could you please edit your message and remove the whole verbatim quote of my message? There's no point in quoting the whole previous message, it makes reading the ticket harder... ;)

[wtfcowisown]

Edited the post and added the files! Thank you for helping.

[Socratis]

OK, this is getting more and more complicated. For example, this?

"E:\New group\New group\Yolo Clone\Yolo Clone.vdi"

This looks like you've created two new VM groups and in there you have a clone of a VM named "Yolo". Not sure if it's something that you would have done willingly, or if only by accident.

And since I would like to have a 2nd/3rd/4th/more opinions on this, please open a new thread in the ​VirtualBox on Windows Hosts section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

Just to save you a post, I'm going to need you to include the following files in your new thread, ZIPPED please, saves a (virtual) tree ;):

• The file: Yolo Clone.vbox
• The file: C:\Users\Computer\.VirtualBox\VirtualBox.xml
• The file: C:\Users\Computer\.VirtualBox\VBoxSVC.log
• The output of: VBoxManage showmediuminfo "E:\New group\New group\Yolo Clone\Yolo Clone.vdi"
• The output of: dir "E:\New group\New group\Yolo Clone\" /s

All of them as fresh as possible, i.e. close and restart VirtualBox, try to launch the VM, get the error, shut down the VM, quit VirtualBox, then get the requested files above.

[wtfcowisown]

Solved it!

I needed the extension pack to run the "VBoxManage" command you listed above. I installed it and ran the virtual server to get updated logs, and then ti worked perfectly.

Turns out I just needed to reinstall the extension pack after reinstalling VirtualBox.... I'm dumb. Sorry! Thank you for your help.

[Socratis]

Of course! Disk encryption requires the ExtPack, and you had none:

00:00:01.951688 Installed Extension Packs:
00:00:01.951726   None installed!

I should have noticed it from the first pass. Mea culpa...

BTW, the "VBoxManage" command shouldn't require the ExtPack. Unless this specific command ("VBoxManage showmediuminfo") needed the ExtPack due to the fact that the disk was encrypted. Got to try it...

I guess the ticket can be closed as ... [WorksForMe](?), since it does actually does work for you after all.