1

This is the error I’m getting.

image
image836×807 40 KB

The host DOES have VBS enabled in the BIOS. Not SecureBoot tho. Basically I had issues with the image on my desktop (the image running on the host, not the VM) so I deployed a generalized sysprep’d image on it, no issues. The VM had BitLocker on it, just like the host. I don’t know the Recovery Key of the VM’s BitLocker.

How can I solve this issue? Thanks a lot

6 Spice ups
2

I can’t read most of your error message, unfortunately, but the text I quoted here is concerning. If you don’t have the recovery key, you cannot unlock it without the key/TPM that normally unlocks it.

If you haven’t already, you really should back up all of your bitlocker recovery info for all of your production machines/VMs.

If it was tied to a Microsoft account you can find instructions for recovering the key here. If it wasn’t, but was Entra-joined, this MS Support page might help.

2 Spice ups
3

I actually took the screenshot, and asked Gemini to translate it:

—BEGIN QUOTE—
Virtual machine connection

The application detected an error while attempting to modify the state of the MDT Server.

The MDT Server cannot be started.

The MDT Server cannot be initialized.

Cannot start the MDT Server virtual machine because virtualization is not running on the host.

‘MDT Server’: Startup failed. (Virtual machine ID: FA439C48-44FA-4944-B636-CEA01A10E02C)

The ‘MDT Server’ could not start the worker process: The group or resource is not in the correct state to perform the requested operation. (0x8007139F). (Virtual machine ID: FA439C48-44FA-4944-B636-CEA01A10E02C)

The virtual machine (MDT Server) could not be initialized either. (Virtual machine ID: FA439C48-44FA-4944-B636-CEA01A10E02C)

Cannot start the MDT Server virtual machine because virtualization is not running on the host. Check the necessary virtualization settings for the virtual machine with one of the virtual machine tools, and look for events in the Kernel-Boot event log that relate to kernel-boot source virtualization security. (Virtual machine ID: FA439C48-44FA-4944-B636-CEA01A10E02C)
—END QUOTE—

I don’t have a solution, but maybe that will be helpful to someone. Of course, I can’t validate how accurate the translation is either. I was kind of impressed at Gemini for doing this from a screenshot.

4 Spice ups
4

Have you tried turning it off and back on again?
Seriously tho… have you?

On the re-imaged host - is Hype-V host installed, and running on boot up?

1 Spice up
5

Yes and yes.

1 Spice up
6

On the host, since it was re-imaged, the VM is looking for the old host (assumed) On the freshly imaged host you probably still need to import the VM, even if the directory structure is identical. Also you will probably/should need the BitLocker Key: Follow what @Josh-J-Spiceworks mentioned above and get the keys (we are janITors, without keys (read as credentials) we are bad janITors)

It’s been a while since I had hands on with Hype-V, but I did spent “too much time”, (quoting my old boss), reading and documenting what what what on our setup.

If this does not bring it into a working condition, I would have to ask for further help form others in the community, TBH.

1 Spice up
7

I don’t have the BitLocker Recovery Key :confused: