Ventoy
Ventoy copied to clipboard
ventoy
No bootfile found for UEFI!
Hello I have installed Ventoy on my USB and I have added some ISO's files : MediCAT Hiren's BootCD Windows 10 32bit and windows password recovery BootCD all give ERROR on HP Laptop : No bootfile found for UEFI! Mybe the image does not support X64 UEFI! Best Regards
Please give the exact iso file name. Windows 10 32bit only support IA32 efi, your machine may be x86_64 uefi (amd64 uefi), so this distro can't boot and will show this message.
For Hiren's BootCD HBCD_PE_x64.iso has been tested in UEFI mode.
Besides, you can try a linux iso file, for example ubuntu-20.04-desktop-amd64.iso
I have the same for Memtest86-4.3.7.iso and ipxe.iso but works fine with netboot.xyz-efi.iso (v2.0.17), manjaro-gnome-20.0.3-200606-linux56.iso, Windows10_PLx64_2004.iso and HBCD_PE_x64.iso (v1.0.1) Lenovo Ideapad Z580. evrything works fine with legacy mode
@ventoy I have tested on laptop Lenovo Ideapad Z570 and Memtest86-4.3.7.iso and ipxe.iso gived same error but with additional information:
ASSERT EFI_ERROR (Status = Invalid Parametr)
ASSERT [Ventoy] /home/share/Ventoy/EDKII/edk2-edk2-stable201911/MdePkg/Library/UefiMemoryAllocationLib/MemoryAllpcationLib.c (813
) : !EFI_ERROR (Status)
No bootfile found for UEFI!
Maybe the image does not suport x64 UEFI
netboot.xyz-efi.iso (v2.0.17), manjaro-gnome-20.0.3-200606-linux56.iso, Windows10_PLx64_2004.iso worked fine.
Hope it would helps
@BxOxSxS Please test these ISO files in Virtual Machine (e.g. Vmware) with UEFI mode and to confirm that the ISO file does support UEFI mode.
@BxOxSxS Please test these ISO files in Virtual Machine (e.g. Vmware) with UEFI mode and to confirm that the ISO file does support UEFI mode.
I checked and they don't work. So it is impossible to get these ISOs to work with ventoy without enabling legacy support in the bios settings?
Yes. Ventoy virtualizes the ISO as a cdrom device and boot it. So if the ISO doesn't support UEFI mode itself, the boot will fail.
Hi All,
I have the same error, I can boot from the same usb, the same iso file and the same Ventoy on asus vivobook but not on asus ROG.
any helpe please
I'm getting the same error when booting "Fedora-Workstation-Live-x86_64-33-1.2.iso" or "pop-os_20.04_amd64_intel_8.iso" on either a new ThinkPad X13 or T14s using Ventoy 1.0.31 UEFI. Secure Boot is disabled in the BIOS on both systems, and the ISO boots just fine if I write it directly to a USB stick with Fedora Image Writer.
Ventoy is able to chain boot Windows 10 (build 2004) just fine on the same systems.
same here on ThinkPad x13 as for @rderooy EDIT: It looks like that version https://github.com/ventoy/Ventoy/releases/tag/v1.0.33 fixes issue with my thinkpad. @rderooy try to use newest version
same here on ThinkPad x13 as for @rderooy EDIT: It looks like that version https://github.com/ventoy/Ventoy/releases/tag/v1.0.33 fixes issue with my thinkpad. @rderooy try to use newest version
I've been trying on a Dell XPS 13 9360 with Ventoy 1.0.34 UEFI running and Memtest86-4.3.7.iso does not work. Getting the same error as @rderooy
I found that on modern systems (those not needing legacy boot) that using the GPT boot partition version (UEFI) only is a lot more reliable. With that with recent versions, all seems to work fine.
Thank you both for your replies. Indeed I have erroneously downloaded memtest v4 because I just read ".iso" and went for it. I have used OSFMount to convert the img file of memtest v8 to iso but I have encountered the same issue. ElementaryOS boots just fine. In Ventoy I had enabled Secure Boot and GPT. I cannot boot into Ventoy with Secure Boot enabled on my machine though, it only boots when I disable Secure Boot in BIOS. Would disabling Secure Boot in Ventoy help? Thanks!
Edit: Disabling Secure Boot didn't help. The only thing that changed is that the " No bootfile found for UEFI!" error was now displayed in 1080p. That's an improvement, I guess? /s
You need to make the ISO UEFI64 bootable. You can't just convert things to an ISO and expect them to be bootable! The easiest thing to do if you don't have a UEFI-bootable Memtest86 ISO is to extract the \EFI\BOOT\BOOTX64.efi file and just copy that to your Ventoy drive. Rename it as MemTest86_64.efi (or something similar).
I'll be damned... I guess this is a classic error 45, huh? The error sits 45 cm away from the screen, haha. Interestingly enough, the ISO does contain the efi files as I made sure to convert the whole IMG, which on the other hand is the basis for the creation of a memtest flash drive. Extracting the very same efi file and running that in Ventoy did work! So thanks a ton, @steve6375! By the way, this issue could be closed, couldn't it? I mean things work... as long as the user knows what to do...
I've been trying to do something I've done a milliion times before:
- Download Debian net installer.
- Download non-free firmware archive.
- Open net installer iso using archive manager in Debian (pre-existing system). This is also known as file-rolller.
- Add firmware packages to the firmware directory.
- Boot net installer and install Debian.
This has always worked for me. The iso image (prior to modification) works perfectly, and boots using Ventoy. However, after adding firmware packages Ventoy complains Bootfile not found. Inspection of the filesystem within the iso image shows the boot file(s) - including the UEFI bootfile - in the respective directory.
What's going on here? Is Ventoy checking md5sums and refusing to load an iso that doesn't match or something? If so, please include aflag to stop this check from happening!
I assume that file-roller is not preserving boot parameters, use another iso creation tool.
Adding an efi boot file to the directory does not make an iso uefi-bootable. Does the iso boot from a VM as a virtual DVD? My guess is it does not. Google for how to make an iso uefi bootable for more info.
Adding an efi boot file to the directory does not make an iso uefi-bootable. Does the iso boot from s VM as a virtual DVD? My guesd is it does not. Google for how to make an iso uefi bootable for more info.
I didn't add an efi boot file - it already existed; I only referenced its existence because of the context of the error message. Thank you for the suggestions.
I adsime that file-roller is not preserving boot parameters, use another iso creation tool.
JonnyTech's response seems the likely circumstance - however: I've always used Archive Manager to do this and have never had an issue. I'll try looking into the changelog on the deb package and see if maybe that's changed, or perhaps if there's a setting somewhere to accomodate this.
Thank you for your suggestions!
Rik
On Mon, Feb 22, 2021 at 12:25 PM Steve Si [email protected] wrote:
Adding an efi boot file to the directory does not make an iso uefi-bootable. Does the iso boot from s VM as a virtual DVD? My guesd is it does not. Google for how to make an iso uefi bootable for more info.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
If anyone has an issue - please state full and accurate details. ISO file name (full exact name) Ventoy version and details of options chosen when making it (Legacy\MBR\reserved space) Legacy\UEFI32\UEFI64 boot? Results when tested on different models\types of x86 computers - amount of RAM, make/model, latest BIOS? Error description screenshots if possible Many thousands of people use Ventoy, the website has a list of tested ISOs. If the ISO is on the tested list, then clearly it is a problem with your particular equipment, so you need to give the details. For instance, it could be that only certain models of PC have this problem with certain specific ISOs.
Sorry for my ignorance. Turned out archlinux-2021.06.01-x86_64 is not compatible. Tried with archlinux-2021.05.01-x86_64 which is listed as compatible and it is working flawlessly.
Thank you.
Sorry for my ignorance. Turned out
archlinux-2021.06.01-x86_64is not compatible. Tried witharchlinux-2021.05.01-x86_64which is listed as compatible and it is working flawlessly.Thank you.
Seriously? FFS I just spent hours reinstalling arch just to get this in the end...
archlinux-2021.06.01-x86_64.iso with Ventoy 1.0.47 boots for me on Lenovo IdeaPad 300 UEFI64 boot. It gets to the root@archiso ~ # prompt just fine using first boot option. I didn't try install using it though.
Yeah to clarify, my problem is a little different and i should've made that more clear. I made a VHD of an arch installation and installed the vtoyboot mod and it keeps on giving me the no UEFI error.
I have this same problem. Is there a way to force Ventoy to boot in Legacy mode? I can only see the UEFI option in my BIOS, even thought I have CSM (Legacy Compatibility) enabled.
Some bioses have a bug. They do not provide a legacy boot option if there is a fat partition with an /EFI folder on it. In this case, try renaming the efi folder as efixxx, and then see if you get a legacy boot option.
Hey, I have encountered the same problem and I found that after deleting the "System Volume Information" folder on Ventoy partition of the USB disk, it can boot now.
Hey, I have encountered the same problem and I found that after deleting the "System Volume Information" folder on Ventoy partition of the USB disk, it can boot now.
I didn't expect this folder to be an issue. I can confirm it was the reason for some ISOs to not boot (ChimeraOS, Manjaro Gnome). Many thanks!
para usuarios de habla hispana.
relativo a la imagen iso a utilizar 1.- comprobar que la imagen que tienes sea de 64 bits https://www.youtube.com/watch?v=F5NFuDCZQ00 2.-verificar que la arquitectura de la imagen iso sea compatible con el procesador
relativo a uefi bios
1.-modo uefi: la imagen iso,bin, etc debe ser de 64 bits sino no la reconoce debes activar modo uefi en el bios las particiones seran gpt
modo bios puedes poner cualquier imagen en 32 o 64 bits debes activar modo legacy en el bios-uefi debes desactivar secure boot en el bios-uefi puedes usar las particiones gpt o mbr
espero les sirva, pueden usar rufus, ventoy, easy to boot, etc. lo importante es conocer las diferencias entre uefi y bios y tambien entre gpt y mbr.
I have the same error with EndeavorOS_Atlantis_neo_21_5.iso using ventoy 1.0.70.
the EndeavorOS iso boots with no issues when on it's on usb, but not through ventoy.
EndeavourOS_Atlantis_neo-21_5.iso boots OK using UEFI64 on Ventoy and grubfm. What exactly is the problem? What system are you booting from? Legacy? UEFi64? etc.
The current release of Slax (slax-64bit-11.2.1.iso) fails to boot using UEFI64 using ventoy with the error message: "No bootfile found for UEFI! Maybe the image does not support X64 UEFI."
I am getting the same error, and I confirmed that the iso has UEFI support. I used Rufus on a new USB with the same iso image, and when I booted to it with UEFI it booted successfully. But when I try to boot it with ventoy it does not boot and says the message "No bootfile found for UEFI".
^^ maybe a lenovo / thinkpad / thinkcentre issue ?
@DocAciD I don't have a Lenovo, ThinkPad or a ThinkCentre