No bootfile found for UEFI! #313
Comments
|
Please give the exact iso file name. For Hiren's BootCD HBCD_PE_x64.iso has been tested in UEFI mode. Besides, you can try a linux iso file, for example |
|
I have the same for |
|
@ventoy I have tested on laptop Lenovo Ideapad Z570 and
|
|
@ventoy I still have this error on z580 with ventoy 1.0.16 |
|
@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. |
|
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 |
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 |
|
V4 is legacy version. It does not contain efi boot files. |
|
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! |
|
I'll be damned... I guess this is a classic error 45, huh? The error sits 45 cm away from the screen, haha. |
|
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! |
|
@ventoy imho its a bug. Installer is Ubuntu 20.04 x64 |
|
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. |
|
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 ***@***.***> 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.
|
|
what is the working solution? check manjaro-gnome, not working. |
|
Is there any solution for this? Getting the same error with Arch Linux. |
|
If anyone has an issue - please state full and accurate details. |
|
Sorry for my ignorance. Turned out 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. |
|
Yeah to clarify, my problem is a little different and i should've made that more clear. |
|
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. |
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 relativo a uefi bios 1.-modo uefi: modo bios 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. |
|
The current release of Slax (slax-64bit-11.2.1.iso) fails to boot using UEFI64 using ventoy with the error message: |
|
same error during creating windows 7 |
|
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 |
|
Getting the same on TinyCoreLiInux (CorePlus) URL; http://tinycorelinux.net/downloads.html
|
|
The ISO must be UEFI-bootable and have a UEFI64 boot file \EFI\BOOT\BOOTX64.EFI |
|
@steve6375 Okay thanks. But I was actually talking about CorePlus. I see your point, this CorePlus ISO is indeed missing that EFI file. |
|
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. |
|
Delete or rename the \EFI folder on the VTOYEFI partition 2 of the Ventoy drive. |
|
@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. |
|
Maybe because of partition type |
|
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" ) |
|
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 |
|
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. |
|
There are two sorts of x86 UEFI BIOS firmware, UEFI32-bit and UEFI64-bit. |
|
Got hit with this issue, using the Unfortunately, this ISO most certainly includes working UEFI bootloaders (and you can see how it is generated, through Tested in all of 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... |
|
Having this issue with Proxmox VE 8.1-2 as well. |
|
The default UEFI shell provided in espack does not boot with Ventoy either. I just unzipped the latest release file, run |
and others
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
The text was updated successfully, but these errors were encountered: