It has little to nothing to do with your USB sticks, rather, it a problem that has been around since VEntoy started. In doing some more reading and for some reason or and another I created a Ventoy folder within the ventoy folderĪt first the first ventoy worked.I am having problems trying to boot both 64- and 32-bit versions with Ventoy. The list was created.Īt this point I booted an iso pe and booted.īut then I was looking for the VHD folder to boot from, No such thing showing ventoyignore with no name and just an extension to exclude certain folders So i tried to find if you could negate searching to folders that had nothing to do with ventoy. It stayed there for a loooooooooooooooooooooong time I think I had nearly 400GB of data on the drive.īefore the move it didnt seem to have a problem creating a list. Tried to boot into ventoy and it worked to the part to where it creates the list. So i moved all the stuff back and forth using FreeFileSync old version upon someone else's recommendation and it worked. You can leave the ventoy partition where it is. The only way to do it was thru moving all data to a new drive.Then you can Format the whole EXFAT Partition into NTFS. So i tried to convert the drive into NTFS because in reading one of the articles it said I need that NTFS.įound out that converting a drive from exfat to NTFS without damage to data in not possible as of this wring in 2023 using free or other methods. found that by default Ventoy formats the drive in Exfat. Booted the VHDX and it worked.Īnother test. So in reading it turns out its not included in the installer of ventoy and a file ventoy_vhdboot.img needs to be put in a ventoy folder in the ventoy drive. Ran into a problem that ventoy would not see VHD or VHDX file. you can come back and create a new vhdx and select the option to Activate Windows repair mode option at the bottom. THANKS!)įor File name : Open file image using the right side button StarWind V2V Converter (VERY USER Friendly. In the final chase the chosen app was "StarWind V2V Converter". The Vmware vmdk file had to be converted to VHD or VHD(x). So in order to get the boot VHD(x) file Needed by Ventoy. I tried a Trimmed down WIndows 11 installed on Vmware. The thing that interested me was booting VHD or VHD(x) growable image. In reading the description about what ventoy can do to create bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files I had to read that the Ventoy2Disk.exe was to be used to start the process. In trying to find how to use it on a usb drive. So it will not work if it is on a partition layout not created by itself. Prohibit the use of Ventoy in unofficial environments. Ventoy starting from version 1.0.28 has this note on page: I used as a guide the USB_FORMAT tool from wimb, wich I used to format a USB device and just copied all content of U-BOOT partition to my FAT-32 partition, edited the BCD and added the grub4dos for UEFI renamed file on FAT-32 partition \EFI\Boot\boot圆4_g4d.efi, created my menu.lst on \EFI\grub\menu.lst and made the entries and finally edited the \grub\grub.cfg, after this just created the new entries on UEFI by means of BootIce as said. NOTE: Not working fine yet, but chainloading to grub2 first, then it can can be called, and we get MS Boot Menu. The standard MS Windos: /EFI/Microsoft/Boot/bootmgfw.efi > Not working fine yet, see NOTE.Grub4dos for UEFI: On \EFI\grub\menu.lst there are entries to chainload to: grub4dos for UEFI: /EFI/Boot/boot圆4_g4d.efi.The standard MS Windos: /EFI/Microsoft/Boot/bootmgfw.efi.Grub2: On \grub\grub.cfg there are entries to chainload to: grub4dos for UEFI: \EFI\Boot\boot圆4_g4d.efi > Created using BootIce.Grub2: \EFI\Boot\BOOTX64.EFI > Created using BootIce.The standard MS Windos: \EFI\Microsoft\Boot\bootmgfw.efi (unmodified). The second HD (MBR formated too) first primary partition is FAT-32 for UEFI booting, by means of BootIce I created 2 additional entries so now using the boot override key (F8) there are 3 options to boot on UEFI The first HD first primary active Partition is NTFS for MBR booting Win7, Win10 and several VHDs, ISOs & WIMs files, that can be ran by means of Win bootmgr, grub4dos or agFM. I was thinking in chainloading to Ventoy from grub4dos or grub2, not in installing it as the main bootmanager and loose al info on one of the the internal HDs, in fact on this PC I have 2 internal HDs, both MBR formated. Thanks for your answer, but ufortunatelly it is not what I would like to do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |