mirror of
https://github.com/ventoy/Ventoy.git
synced 2026-03-03 00:07:49 -05:00
No bootfile found for UEFI! #298
Labels
No labels
Denied Feature Request
File Corrupted
Fixed
Good practice
Not an issue
Not planed
USB 2.0/3.0
USB Hardware Issue
Wait Upstream Fix
bug
documentation
duplicate
enhancement
help wanted
question
wontfix
【Tested Image Report】
【Tested Image Report】
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Ventoy-ventoy#298
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bouhlal on GitHub (Jul 16, 2020).
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
@ventoy commented on GitHub (Jul 16, 2020):
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@BxOxSxS commented on GitHub (Jul 17, 2020):
I have the same for
Memtest86-4.3.7.isoandipxe.isobut works fine withnetboot.xyz-efi.iso(v2.0.17),manjaro-gnome-20.0.3-200606-linux56.iso,Windows10_PLx64_2004.isoandHBCD_PE_x64.iso(v1.0.1) Lenovo Ideapad Z580. evrything works fine with legacy mode@BxOxSxS commented on GitHub (Jul 18, 2020):
@ventoy I have tested on laptop Lenovo Ideapad Z570 and
Memtest86-4.3.7.isoandipxe.isogived same error but with additional information:netboot.xyz-efi.iso(v2.0.17),manjaro-gnome-20.0.3-200606-linux56.iso,Windows10_PLx64_2004.isoworked fine.Hope it would helps
@BxOxSxS commented on GitHub (Jul 24, 2020):
@ventoy I still have this error on z580 with ventoy 1.0.16
@ventoy commented on GitHub (Jul 25, 2020):
@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 commented on GitHub (Jul 25, 2020):
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?
@ventoy commented on GitHub (Jul 25, 2020):
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.
@SaryZainoun commented on GitHub (Nov 23, 2020):
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
@rderooy commented on GitHub (Dec 30, 2020):
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.
@rengare commented on GitHub (Jan 25, 2021):
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
@eogut commented on GitHub (Feb 4, 2021):
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
@steve6375 commented on GitHub (Feb 5, 2021):
V4 is legacy version. It does not contain efi boot files.
@rderooy commented on GitHub (Feb 5, 2021):
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.
@eogut commented on GitHub (Feb 5, 2021):
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
@steve6375 commented on GitHub (Feb 5, 2021):
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).
@eogut commented on GitHub (Feb 5, 2021):
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...
@kirvedx commented on GitHub (Feb 22, 2021):
I've been trying to do something I've done a milliion times before:
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!
@akalongman commented on GitHub (Feb 22, 2021):
@ventoy imho its a bug.
Installer is Ubuntu 20.04 x64
@JonnyTech commented on GitHub (Feb 22, 2021):
I assume that file-roller is not preserving boot parameters, use another iso creation tool.
@steve6375 commented on GitHub (Feb 22, 2021):
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.
@kirvedx commented on GitHub (Feb 22, 2021):
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.
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 notifications@github.com wrote:
@vidyli commented on GitHub (Mar 30, 2021):
what is the working solution? check manjaro-gnome, not working.
@dausruddin commented on GitHub (Jun 13, 2021):
Is there any solution for this? Getting the same error with Arch Linux.
@steve6375 commented on GitHub (Jun 13, 2021):
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.
@dausruddin commented on GitHub (Jun 14, 2021):
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.
@DonielMoins commented on GitHub (Jul 24, 2021):
Seriously? FFS I just spent hours reinstalling arch just to get this in the end...
@steve6375 commented on GitHub (Jul 24, 2021):
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.
@DonielMoins commented on GitHub (Jul 24, 2021):
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.
@gabriel-messas commented on GitHub (Aug 28, 2021):
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.
@steve6375 commented on GitHub (Aug 28, 2021):
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.
@GrimPixel commented on GitHub (Nov 19, 2021):
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.
@SelfRef commented on GitHub (Dec 8, 2021):
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!
@kichito commented on GitHub (Dec 17, 2021):
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.
@Mr-McBride commented on GitHub (Mar 2, 2022):
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.
@steve6375 commented on GitHub (Mar 2, 2022):
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.
@cloudxone commented on GitHub (Mar 22, 2022):
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."
@abhin44 commented on GitHub (Mar 28, 2022):
same error during creating windows 7
plzz help
@Aholicknight commented on GitHub (May 3, 2022):
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".
@DocAciD commented on GitHub (May 16, 2022):
^^ maybe a lenovo / thinkpad / thinkcentre issue ?
@Aholicknight commented on GitHub (May 18, 2022):
@DocAciD I don't have a Lenovo, ThinkPad or a ThinkCentre
@Suleman-Elahi commented on GitHub (Aug 19, 2022):
Getting the same on TinyCoreLiInux (CorePlus)
URL; http://tinycorelinux.net/downloads.html
@steve6375 commented on GitHub (Aug 19, 2022):
The ISO must be UEFI-bootable and have a UEFI64 boot file \EFI\BOOT\BOOTX64.EFI
You can open the ISO in 7zip and look for yourself.
see http://tinycorelinux.net/13.x/x86_64/release/
TinyCorePure64-13.1.iso does UEFI64 boot OK
but CorePure64-13.1.iso does not as it does not contain any EFI boot files
@Suleman-Elahi commented on GitHub (Aug 19, 2022):
@steve6375 Okay thanks. But I was actually talking about CorePlus. I see your point, this CorePlus ISO is indeed missing that EFI file.
@vlad54rus commented on GitHub (Oct 1, 2022):
Any way to disable UEFI booting capability from Ventoy and only leave legacy? I have some systems which won't offer legacy boot option if UEFI is present at the same time.
@steve6375 commented on GitHub (Oct 1, 2022):
Delete or rename the \EFI folder on the VTOYEFI partition 2 of the Ventoy drive.
@vlad54rus commented on GitHub (Oct 3, 2022):
@steve6375 I've mounted that partition and deleted EFI folder but it's still recognized as EFI, both in Windows Disk Management and the BIOS, just doesn't boot anymore.
@steve6375 commented on GitHub (Oct 3, 2022):
Maybe because of partition type
You can change the type or just delete the partition
@theotheroracle commented on GitHub (Jul 19, 2023):
i have a really weird edge case, i have the lastest ventoy 1.0.93, and on one machine it will boot uefi fine, specifically the gnome-nixos iso, and on my supermicro server, it's giving the no bootfile found for uefi error, so i'm not sure what's happening in this case
( i also tried grub mode and memcache mode, and neither worked, although the grub mode was just stuck on "booting linux lts" )
@theotheroracle commented on GitHub (Jul 19, 2023):
guix does boot in uefi though, but it looks to be using a more standard grub install, i'm not sure what the nixos installer is using
@poopybunghole commented on GitHub (Jul 23, 2023):
I tried running Windows 10 32Bit version ISO using Ventoy on a Thinkpad X230T and I got the same error, turns out UEFI was configured in BIOS and Windows 10 32bit ISO won't start if UEFI boot is configured, so I changed the bios to boot Legacy mode first and it worked. Doesn't really seem to be a problem with Ventoy as far as I can tell. Although the error could be more helpful.
@steve6375 commented on GitHub (Jul 24, 2023):
There are two sorts of x86 UEFI BIOS firmware, UEFI32-bit and UEFI64-bit.
Most systems have a UEFI64-bit BIOS and so can only UEFI-boot from 64-bit OS's which have a \EFI\BOOT\BOOTX64.EFI boot file (this is on Windows 64 ISOs and Linux 64-bit ISOs).
A few (very few) systems have a UEFI32 BIOS and boot using the \EFI\BOOT\BOOTIA32.EFI file (found in 32-bit Windows ISOs and a few 32-bit Linux ISOs).
So to UEFI boot a Win 64-bit ISO you need a system with a UEFI64 BIOS. To UEFI-boot a WIn32-bit ISO you need a system with a UEFI32 BIOS.
Note that it does not necessarily depend on what CPU you have because some systems have a 64-bit CPU but have a UEFI32 BIOS and so can only be UEFI-installed using source files which have the UEFI32 boot files (e.g. Win10/11 32-bit ISOs).
@pbatard commented on GitHub (Mar 29, 2024):
Got hit with this issue, using the
UEFI-Shell-2.2-23H2-RELEASE.isofrom https://github.com/pbatard/UEFI-Shell/releases while starting to test for #135.Unfortunately, this ISO most certainly includes working UEFI bootloaders (and you can see how it is generated, through
genisoimagehere), so it's rather annoying that it does not appear to work with Ventoy.Tested in all of
normal,grub2andmemdiskmode using Ventoy 1.0.97.Hopefully, other people can replicate the issue, to confirm that it's not just me, and this issue can be fixed in a future release of Ventoy...
@nabeelr commented on GitHub (Apr 5, 2024):
Having this issue with Proxmox VE 8.1-2 as well.
@askoa commented on GitHub (Jun 9, 2024):
The default UEFI shell provided in espack does not boot with Ventoy either. I just unzipped the latest release file, run
sh esp.shcreating anesp.imgwith UEFI shell provided in the release file. I am not able to boot the generated image using Ventoy. I am getting the error mentioned in this issue.@ant-222 commented on GitHub (Jun 26, 2024):
I am having exactly the same problem with TinyCore v.15. Could it be because of it is for x86? Does Ventoy support pre-UEFI images for older 32-bit systems, or does is it require x64 UEFI?
@Hyourinmaru0 commented on GitHub (Aug 29, 2024):
MSI Z97 Gaming 7 | Intel Core i7-4790K | 4x 8GB DDR3 | Primary OS: Windows 10 Pro 22H2
I have the same issue, but i think, it's not ventoy related.
I'm not able to boot several linux live images, downloaded from their original webpages.
My ventoy ssd is configured by the following:
I have tried the following images:
I had tested these iso images with ventoy and I'm only able to start these, where are Debian-/Ubuntu-based, such as Ubuntu, Kubuntu, KDE neon, Linux Mint and Linux Mint Debian Edition. All other throw the
No bootfile found for UEFI!Maybe the image does not support x64 UEFI!error.Arch Linux and EndeavourOS displays first
EFI stub: ERROR: exit_boot() failed!EFI stub: ERROR: efi_stub_entry() failed!Failed to execute EndeavourOS x86_64 UEFI Default (\arch\boot\x86_64\vmlinuz-linux): Buffer too smalland then I get the error message displayed by the other images.
All these images have an bootx64.efi file in the /efi/boot/ directory.
If i select the grub2 method in ventoy, the live linux starts and let me install it on my second internal ssd which is empty, but the following boot cannot performed and i get the error message above.
I get this issue also if I burn the images on a usb drive with rufus (GPT/UEFI/FAT32), except for Debian-based images.
I have also turn off trusted platform module and secure boot and tried to switch between UEFI only and Legacy+UEFI in my bios, but it has no impact.
It's very suspicious, two years ago i have tried out the current Manjaro release at the time and it has worked without problems. With the same hardware as i listed at the top of my posting.
@truefriend-cz commented on GitHub (Nov 17, 2024):
I have same problem. I installed in VirtualBox: debian-12.4.0-amd64-netinst.iso (to VHD file/image).
After configuration i adding .vtoy extension and after booting from image file show:
No bootfile found for UEFI!
Mybe the image does not support X64 UEFI!
My instalation is for UEFI only but Ventoy have problem accepted this.
If i switch in BIOS mode to Legacy i am get this Linux message:
How i can fix please?
@truefriend-cz commented on GitHub (Nov 21, 2024):
Devs you are working on fixed this bug or not?
@abdoei commented on GitHub (Feb 23, 2025):
I tried both formatting styles and both give the same error. I just can't use it with the UEFI turned on, it just works on legacy, but it is fine.
@truefriend-cz commented on GitHub (Feb 3, 2026):
Why don't you plan to fix this error?