Microsoft Hyper-V BootIt ISO is not starting

[gtalos]

Hi together. When I try to boot BootIt with an ISO, it tries to boot a few times and then aborts. Various settings during ISO creation (BIOS, UEFI, options) have had no effect. However, an ISO with tbosdts starts without problems. Also an ISO with gparted-live-1.4.0-5-amd64 works. What am I doing wrong?

[TeraByte Support]

A full BootIt BM disk requires HD emulation which a system may not implement. In that case, create two isos, one with disk imaging enabled, scripting disabled and another with disk imaging disabled and scripting enabled. boot from both and install to get the full package. UEFI should already boot in a VM like a physical machine but I think I've seen some VM's not handle it.

[gtalos]

Hi. Thank you. The disk iso with imaging only enabled starts without a problem. The other iso with bootitbm and disk imaging disabled does not start. (see screenshots att.) I need the disk partition features of bootitbm.

[TeraByte Support]

partition work will exist in either, the scripting part would be missing when not selected. you create an IFU boot disk, since you can use UEFI, create the BIU version instead of BIBM version.

[gtalos]

I have created a new ISO file with biu. When starting it breaks after a few quick attempts. The same problem as at the beginning. The VM switches off afterwards. Starting the ISO with image still works. I have now also tried it on a PC with Windows 11 and Hyper-V. Here I have the same problem.

[gtalos]

Screenshot

[TeraByte Support]

The ISO for UEFI is multi-boot, if booted on legacy BIOS you get a message that it's not usable, maybe the VM's aren't supporting it? But they boot on physical machine. If you can boot legacy mode, BIBM, that boots either 2.88FDD emulation or HD emulation, all the physical systems support FDD emulation, some have problems with HD emulation (which is why you create the two different versions with less data so it fits on a FDD size image). So you should be able to get the BIBM to boot from the ISO by creating two versions, one with imaging disabled and one with scripting disabled.

Or if you can put on a UFD, and have the VM take over the USB and boot from it.