VHDX file created by StarWind V2V Converter won't boot

[e9zlfhZI]

I tried to create a Hyper-V VM using Disk2VHD. I tried it a couple of times and couldn't get the VM's to start:

Microsoft Hyper-V UEFI
Virtual Machine Boot Summary

1. Network Adapter (00155D018000)
A boot image was not found.

2. SCSI Disk (0,0)
The boot loader did not load an operating system.

No operating system was loaded. Your virtual machine may be configured incorrectly. Exit and re-configure your VM or click restart to retry the current boot sequence again.

I did some research and thought it was because I was I was trying to do it from Disk2VHD on my computer. I couldn't figure out how to get a USB to boot with Windows 11 installed and then start Disk2VHD. So I looked for other solutions ... and found StarWind V2V Converter. I tried that and created a VHDX file.

When I created a VM using that VHDX, it ran ... but the VM never boots!

https://i.imgur.com/TsjGlTT.png

I'm thinking that I didn't create the VHDX file correctly.

There are the 3 disks on the computer:

https://i.imgur.com/ccQU9Mm.png

When I created the VHDX file, these are the options I chose:

Select the location of the image to convert: P2V - Convert physical machine or disk

Select physical data to convert: Physical Disk - Convert the physical disk to a virtual disk file.

Volume structure is preserved. It is possible to select a set of disk volumes for copying to a virtual disk file

In "Select physical disk to convert", there were 5 choices! In my first attempt (no notes on that one) I tried just C:\. This time, I tried all 5: https://i.imgur.com/6cLHNEQ.png

Select the location of the destination image: Local file: File on the local machine

Select destination image format: VHD/VHDX - Microsoft Virtual Hard Disk

Select option for VHD/VHDX image format: VHDX growable image - Disk space for this image is allocated on demand, so disk size of this image grows over time (I did not select "Activate Windows Repair Mode")

https://i.imgur.com/RawSCwl.png

Conversion Log:

Time | Information
14:37:05 | Started
14:37:05 | Opening image file 1
14:37:05 | Taking snapshots...
14:37:40 | Taking snapshot of volume C:\ - success
14:37:40 | Taking snapshot of volume \\?\Volume{61b9c6a7-e911-43da-8ce4-5b2b73d...
14:37:40 | Taking snapshot of volume \\?\Volume{521cae76-7997-4264-bdb5-11be78...
14:37:40 | Taking snapshot of volume \\?\Volume...
14:37:40 | Success
14:37:40 | Creating image file
14:37:40 | Success
14:37:40 | New file Hard Disks\EBT2250-20251226-StarWind V2V.vhdx
14:37:40 | Converting...
16:44:10 | Success
16:44:10 | Converted successfully!

Created VM

Settings > Hardware: https://i.imgur.com/4NoIInd.png
Settings > Management: https://i.imgur.com/Uc1LLYR.png

https://i.imgur.com/WWJwU04.png

Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device

Any ideas on what I am doing wrong?

Thanks,

John

[yaroslav (staff)]

If converted successfully, VM not booting is not the V2V Converter issue.
What V2V does is remap the contents of one file into another (similar to disk2VHD). It does not add or change anything. This being said, the VM is not OK with the destination.
In boot options, please try a different boot order. The VM is now booting from the virtual CD.

[e9zlfhZI]

In boot options, please try a different boot order. The VM is now booting from the virtual CD.

Thanks @yaroslav, you were correct, it was booting from the CD.

I set it to boot from IDE ... and received the same "Boot failure" message.

Any other ideas?

Thanks very much,

John

[yaroslav (staff)]

Hi,

Seems to be related to drivers.
Check these out
https://learn.microsoft.com/en-us/troub ... 0xc000000e
https://www.erniecosta.com/2020/02/26/h ... t-drivers/

[brandiknight]

How can I fix a non-bootable VHDX created with StarWind V2V Converter?

[yaroslav (staff)]

See the lins above.