Apollo Blinds Spare Parts, Irs Rules On Owner Financing, Current News Arrests Harlan, Iowa, Sheffield Central Noble City Living, Dropship Candles Private Label, Articles V

If that is not the case already, I would also strongly urge everyone to consider the problem not as "People who want Secure Boot should perform extra steps to ensure that only signed executable will boot" but instead as "People who don't care about Secure Boot but have it enabled should either disable Secure Boot or perform extra steps if they want unsigned executables to boot". Windows 7 UEFI64 Install - Easy2Boot The boot.wim mode appears to be over 500MB. I'm afraid I'm very busy with other projects, so I haven't had a chance. en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2cc.iso Posts: 15 Threads: 4 Joined: Apr 2020 Reputation: 0 0 If you pull the USB drive out immediately after finish copy a big ISO file, most probably the file in the USB will be corrupted. What exactly is the problem? I'm not talking about CSM. The Flex image does not support BIOS\Legacy boot - only UEFI64. Ventoy is supporting almost all of Arch-based Distros well. https://osdn.net/projects/manjaro/storage/kde/, manjaro-kde-20.0-rc3-200422-linux56.iso BOOT Haven't tried installing it on bare metal, but it does install to a VM with the LabConfig bypasses. If Secure Boot is not enabled, proceed as normal. That is the point. can u fix now ? The file size will be over 5 GB. You were able to use TPM for disk encryption long before Secure Boot, and rightfully so, since the process of storing and using data encryption keys is completely different from the process of storing and using trust chain keys to validate binary executables (being able to decrypt something is very different from being able to trust something). Its also a bit faster than openbsd, at least from my experience. Already on GitHub? also for my friend's at OpenMandriva *waaavvvveee* Users can update Ventoy by installing the latest version or using VentoyU, a Ventoy updater utility. It was working for hours before finally failing with a non-specific error. Getting the same error as @rderooy. 2. . Is there any progress about secure boot support? function gennr(){var n=480678,t=new Date,e=t.getMonth()+1,r=t.getDay(),a=parseFloat("0. Secure Boot was supported from Ventoy 1.0.07, an option for secure boot is added in Ventoy2Disk.exe/Ventoy2Disk.sh. You can install Ventoy to USB drive, Removable HD, SD Card, SATA HDD, SSD, NVMe . I tested it but trying to boot it will fail with an I/O error. If the secure boot is enabled in the BIOS, the following screen should be displayed when boot Ventoy at thte first time. Something about secure boot? Well occasionally send you account related emails. Acronis True Image 2020 24.6.1 Build 25700 in Legacy is working in Memdisk mode on 1.0.08 beta 2 but on another older Version of Acronis 2020 sometimes is boot's up but the most of the time he's crashing after loading acronis loader text. Now, that one can currently break the trust chain somewhere down the line, by inserting a malicious program at the first level where the trust stops being validated, which, incidentally, as a method (since I am NOT calling Ventoy malicious here) is very similar to what Ventoy is doing for Windows boot, is irrelevant to the matter, because one can very much conceive an OS that is being secured all the way (and, once again, if Microsoft were to start doing just that, then that would most likely mark the end of being able to use Ventoy with Windows ISOs since it would no longer be able to inject an executable that isn't signed by Microsoft as part of the boot process) and that validates the signature of every single binary it runs along the way which means that the trust chain needs to start somewhere and (as far as user providable binaries are concerned) that trust chain starts with Secure Boot. Ventoy But, just like GRUB, I assert that this matter needs to be treated as a bug that warrants fixing, which is the reason I created this issue in the first place. Thanks very much for proposing this great OS , tested and added to report. With this option, in theory, Ventoy can boot fine no matter whether the secure boot in the BIOS is enabled or disabled. plzz help. Edit ISO - no UEFI - forums.ventoy.net Paragon ExtFS for Windows Error message: Hi, Hiren's Boot CD can be booted by Ventoy in Memdisk mode, you try Ventoy 1.0.08 beta2. @adrian15, could you tell us your progress on this? Maybe the image does not support X64 UEFI! The text was updated successfully, but these errors were encountered: I believe GRUB (at least v2.04 and previous versions if patched with Fedora patches) already work exactly as you've described. slax 15.0 boots No bootfile found for UEFI with Ventoy, But OK witth rufus. memz.mp4. Also ZFS is really good. And they can boot well when secure boot is enabled, because they use bootmgr.efi directly from Windows iso. That's an improvement, I guess? When the user select option 1. Freebsd has some linux compatibility and also has proprietary nvidia drivers. If Secure Boot is enabled, signature validation of any chain loaded, If the signature validation fails (i.e. Preventing malicious programs is not the task of secure boot. Maybe I can get Ventoy's grub signed with MS key. Inspection of the filesystem within the iso image shows the boot file(s) - including the UEFI bootfile - in the respective directory. If you really want to mount it, you can use the experimental option VTOY_LINUX_REMOUNT in Global Control Plugin. . to your account. It woks only with fallback graphic mode. However, users have reported issues with Ventoy not working properly and encountering booting issues. New version of Rescuezilla (2.4) not working properly. check manjaro-gnome, not working. Delete or rename the \EFI folder on the VTOYEFI partition 2 of the Ventoy drive. This option is enabled by default since 1.0.76. WinPE10_8_Sergei_Strelec_x86_x64_2019.12.28_English.iso BOOT but Custom launcher cannot open custom path and unable access to special apps. Using Ventoy-1.0.08, ubuntudde-20.04-amd64-desktop.iso is still unable to boot under uefi. Tried it yesterday. only ventoy give error "No bootfile found for UEFI! As I understand, you only tested via UEFI, right? Well, that's pretty much exactly what I suggested in points 1-4 from the original post, with point 4 altered from "an error should be returned to the user and bootx64.efi should not be launched" to "an error should be returned to the user who can then decide if they still want to launch bootx64.efi". Ventoy -Bootable USB [No-Root] - Apps on Google Play - Android Apps on The text was updated successfully, but these errors were encountered: Please give the exact iso file name. Yes ! fails to find system in /slax, 'Hello System' os can boot successfully with bootx64.efi's machine and show desktop. snallinux-.6-x86_64.iso - 1.40 GB Astra Linux , supports UEFI , booting successfully. Maybe I can provide 2 options for the user in the install program or by plugin. Sign in when the user Secure Boots via MokManager - even when booting signed efi files of Ubuntu or Windows? So maybe Ventoy also need a shim as fedora/ubuntu does. This solution is only for Legacy BIOS, not UEFI. P.S. to your account, MB: GA-P110-D3, CPU: Intel Core i5 6400, RAM: 8GB DDR4, GPU: IGFX + NVIDIA GT730, MB: GA-H81M-S2PV, CPU : Intel Core i3 4650, RAM 8GB DDR3 GPU: IGFX, slitaz-rolling-core-5in1.iso There are many kinds of WinPE. You can grab latest ISO files here : puedes usar las particiones gpt o mbr. to your account, Hi ! Where can I download MX21_February_x64.iso? privacy statement. By the way, this issue could be closed, couldn't it? Menu Option-->Secure Boot Support for Ventoy2Disk.exe and -s option for Ventoy2Disk.sh You can open the ISO in 7zip and look for yourself. I cannot boot into Ventoy with Secure Boot enabled on my machine though, it only boots when I disable Secure Boot in BIOS. But when I try to boot it with ventoy it does not boot and says the message "No bootfile found for UEFI". Both are good. Hi, HDClone 9.0.11 ISO is stating on UEFI succesfully but on Legacy after choose "s" or "x64" to start hdclone it open's a black windows in front of the Ventoy Menu and noting happens more. The MEMZ virus nyan cat as an image file produces a very weird result, It also happens when running Ventoy in QEMU, The MEMZ virus nyan cat as an image file produces a very weird result Does the iso boot from a VM as a virtual DVD? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. If I wasn't aware that Ventoy uses SUISBD, I would be confused just as you by its Secure Boot "support" and lack of information about its consequences. 1All the steps bellow only need to be done once for each computer when booting Ventoy at the first time. 3. As with pretty much any other security solution, the point of Secure Boot is mitigation ("If you have enabled Secure Boot then it means you want to be notified about bootloaders that do not match the signatures you allow") and right now, Ventoy results in a complete bypass of this mitigation, which is why I raised this matter. Try updating it and see if that fixes the issue. In Linux, you need to specify the device to install Ventoy which can be a USB drive or local disk. Ventoy is open-source software that allows users to create ISO, WIM, IMG, VHS(x), and EFI files onto a bootable USB drive. arnaud. No bootfile found for UEFI image does not support x64 UEFI en_windows_10_business_editions_version_1909_updated_april_2020_x64_dvd_aa945e0d.iso | 5 GB, en_windows_10_business_editions_version_2004_x64_dvd_d06ef8c5.iso | 5 GB It says that no bootfile found for uefi. The MISO_EFI partition contains only 1 folder called "efi" and another folder in it called "boot" which contains a single file called "bootx64.efi.". I have used OSFMount to convert the img file of memtest v8 to iso but I have encountered the same issue. All of these security things are there to mitigate risks. It's a pain in the ass to do yes, but I wouldn't qualify it as very hard. No! But I was actually talking about CorePlus. Won't it be annoying? Add firmware packages to the firmware directory. https://drive.google.com/file/d/1_mYChRFanLEdyttDvT-cn6zH0o6KX7Th/view, https://www.mediafire.com/file/5zui8pq5p0p9zug/Windows10_SuperLite_TeamOS_Edition.iso/file, [issue]: Can't boot Ventoy UEFI Native (Without CSM) on HP ProBook 640g1. You are receiving this because you commented. 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. ventoy_x64.efi/ventoy_util_x64.efi ) , they do need digital signatures. It gets to the root@archiso ~ # prompt just fine using first boot option. Perform a scan to check if there are any existing errors on the USB. Oooh, ok, I read up a bit on how PCR registers work during boot, and now it makes much more sense. Hi, Hiren's Boot CD can be booted by Ventoy in Memdisk mode, you try Ventoy 1.0.08 beta2. It's a bug I introduced with Rescuezilla v2.4. Ventoy - Easy2Boot Sorry, I meant to upgrade from the older version of Windows 11 to 22H2. https://nyancat.fandom.com/wiki/MEMZ_Nyan_Cat https://www.youtube.com/watch?v=-mv6Cbew_y8&t=1m13s. And that is the right thing to do. Does shim still needed in this case? Then Ventoy will load without issue if the secure boot is enabled in the BIOS. Can you add the exactly iso file size and test environment information? The user has Ubuntu, Fedora and OpenSUSE ISOs which they want to load. It should be the default of Ventoy, which is the point of this issue. If the ISO file name is too long to displayed completely. ", same error during creating windows 7 "No bootfile found for UEFI! For secure boot please refer Secure Boot . Maybe the image does not support X64 UEFI." UEFI64 Bootfile \EFI\Boot\bootx64.efi is present. My guess is it does not. Point 4 from Microsoft's official Secure Boot signing requirements states: Code submitted for UEFI signing must not be subject to GPLv3 or any license that purports to give someone the right to demand authorization keys to be able to install modified forms of the code on a device. 1.- comprobar que la imagen que tienes sea de 64 bits So I apologise for that. accomodate this. Rik. Discovery and usage of shim protocol of loaded shim binary for global UEFI validation functions (validation policy override with shim verification), Shim protocol unregistration of loaded shim binary (to prevent confusion among shims of multiple vendors and registration of multiple protocols which are handled by different chainloaded shims). Ventoy should only allow the execution of Secure Boot signed executables when Secure Boot is enabled, Microsoft's official Secure Boot signing requirements. 5. Thus, being able to check that an installer or boot loader wasn't tampered with is not a "nice bonus" but is something that must be enforced always in a Secure Boot enabled environment, regardless of the type of media you are booting from, because Secure Boot is very much designed to help users ensure that, when they install an OS, and provided that OS has a chain of trust that extends all the way, any alteration of any of the binary code that the OS executes, be it as part of the installation or when the OS is running, will be detected and reported to the user and prevent the altered binary code to run. So, yeah, it's the same as a safe manufacturer, on seeing that you have a room with extra security (e.g. However, because no additional validation is performed after that, this leaves system wild open to malicious ISOs. Yep, the Rescuezilla v2.4 thing is not a problem with Ventoy. @ValdikSS Thanks, I will test it as soon as possible. da1: quirks=0x2. Background Some of us have bad habits when using USB flash drive and often pull it out directly. Forum rules Before you post please read how to get help. It's the job of Ventoy's custom GRUB to ensure that what is being chainloaded is Secure Boot compliant because that's what users will expect from a trustworthy boot application in a Secure Boot environment. Does the iso boot from s VM as a virtual DVD? @ValdikSS, I'm not seeing much being debated, when the link you point to appears to indicate that pretty much everybody is in agreement that loading unsigned kernels from GRUB, in a Secure Boot environment, is a bug (hence why it was reported as such). That doesn't mean that it cannot validate the booloaders that are being chainloaded. 1.0.84 AA64 www.ventoy.net ===> Ventoy About File Checksum 1. Optional custom shim protocol registration (not included in this build, creates issues). Maybe because of partition type Please refer When Ventoy2Disk.exe Failed to Install, Please refer When Ventoy2Disk.exe Fail to Update, Yes. After install, the 1st larger partition is empty, and no files or directories in it. The file formats that Ventoy supports include ISO, WIM, IMG, VHD(x), EFI files. Will these functions in Ventoy be disabled if Secure Boot is detected? Same issue with 1.0.09b1. Sign in To add Ventoy to Easy2Boot v2, download the latest version of Ventoy Windows .ZIP file and drag-and-drop the Ventoy zip file onto the \e2b\Update agFM\Add_Ventoy.cmd file on the 2nd agFM partition. If Ventoy was intended to be used from an internal hard disk, I would agree with you, but Ventoy is a USB-based multiboot solution and therefore the user must have physical access to the system, so it is the users responsibility to be careful about what he inserts into that USB port. KANOTIX uses a hybrid ISO layout, it definitely has X64 UEFI in ISO9660 and FAT12 (usually 1MiB offset). That's theoretically feasible but is clearly banned by the shim/MS. ventoy maybe the image does not support x64 uefidibujo del sistema nervioso y sus partes para nios ventoy maybe the image does not support x64 uefi. mishab_mizzunet 1 yr. ago I will test it in a realmachine later. But it shouldn't be to the user to do that. You can't just convert things to an ISO and expect them to be bootable! TinyCorePure64-13.1.iso does UEFI64 boot OK UEFi64? Strelec WinPE) Ctrl+r for ventoy debug mode Ctrl+h or h for help m checksum a file then there is no point in implementing a USB-based Secure Boot loader. Yes, Ventoy does work within UEFI mode and offers a default secure boot feature. Adding an efi boot file to the directory does not make an iso uefi-bootable. backbox-7-desktop-amd64.iso - 2.47 GB, emmabuntus-de3-amd64-10.3-1.01.iso - 3.37 GB, pentoo-full-amd64-hardened-2019.2.iso - 4 GB I test it in a VirtualMachine (VMWare with secure boot enabled). I would assert that, when Secure Boot is enabled, every single time an unsigned bootloader is loaded, a warning message should be displayed. Set the VM to UEFI mode and connect the ISO file directly to the VM and boot. 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. Ventoy is an open source tool that lets you create a bootable USB drive for ISO files. The main point of Secure Boot is to prevent (or at least warn about) the execution of bootloaders that have not been vetted by Microsoft or one of the third parties that Microsoft signed a shim for (such as Red Hat). If your PC is unable to process Ventoy as bootable media, then you may need to disable secure boot. But this time I get The firmware encountered an unexpected exception. edited edited edited edited Sign up for free . 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. PS: It works fine with original ventoy release (use UEFIinSecureBoot) when Secure boot is enabled. You can copy several ISO files at a time, and Ventoy will offer a boot menu where you can select them. Keep reading to find out how to do this. if you want can you test this too :) Does it work on these machines (real or emulated) by booting it from a CDR / .iso image? Format NTFS in Windows: format x: /fs:ntfs /q Now, if Microsoft finally relinquished their abusive policy about not accepting GPLv3 code for Secure Boot signing and Ventoy was updated not to allow unsigned bootloaders when Secure Boot is enabled (i.e. Format UDF in Windows: format x: /fs:udf /q Option2: Use Ventoy's grub which is signed with MS key. GRUB2, from my experiences does this automatically. So I don't really see how that could be used to solve the specific problem we are being faced with here, because, however you plan to use UEFI:NTFS when Secure Boot is enabled, your target (be it Ventoy or something else) must be Secure Boot signed. debes desactivar secure boot en el bios-uefi However, considering that in the case of Ventoy, you are basically going to chain load GRUB 2, and that most of the SHIMs have been designed to handle precisely that, it might be easier to get Ventoy accepted as a shim payload. I have a solution for this. I can provide an option in ventoy.json for user who want to bypass secure boot. Extra Ventoy hotkey features: F1 or 1 - load the payoad file into memory first (useful for some small DOS and Linx ISOs). Keeping Ventoy and ISO files updated can help avoid any future booting issues with Ventoy. Open Rufus and select the USB flash drive under "Device" and select Extended Windows 11 Installation under Image option. You can reformat it with FAT32/NTFS/UDF/XFS/Ext2/Ext3/Ext4 filesystem, the only request is that Cluster Size must greater than or equal to 2048. @blackcrack Try updating it and see if that fixes the issue. and leave it up to the user. may tanong po ulit ako yung pc ko po " no bootfile found for uefi image does not support x64 uefi" i am using ventoy galing po sa linux ko, gusto ko po isang laptop ko gawin naman windows, ganyan po lagi naka ilang ulit na po ako, laptop ko po kasi ayaw na bumalik sa windows mula nung ginawa ko syang linux, nagtampo siguro kaya gusto ko na po ibalik sa windows salamat po sa makakasagot at sa . Delete the Ventoy secure boot key to fix this issue. When enrolling Ventoy, they do not. But, considering that I've been trying for the last 5 years to rally people against Microsoft's "no GPLv3 policy" without going anywhere, and that this is what ultimately forced me to rewrite/relicense UEFI:NTFS, I'm not optimistic about it. @ventoy 1.0.80 actually prompts you every time, so that's how I found it. wifislax64-2.1-final.iso - 2 GB, obarun-JWM-2020.03.01-x86_64.iso - 1.6 GB, MiniTool_Partition_Wizard_10.2.3_Technician_WinPE.iso - 350 MB, artix-cinnamon-s6-20200210-x86_64.iso - 1.88 GB, Parrot-security-4.8_x64.iso - 4.03 GB Well occasionally send you account related emails. size: 589 (617756672 byte) Linux distributives use Shim loader, each distro with it's own embedded certificate unique for each distro. Menu. This completely defeats Secure Boot and should not happen, as the only EFI bootloader that should be whitelisted for Secure Boot should be Ventoy itself, and any other EFI bootloader should still be required to pass Secure Boot validation. Reply to this email directly, view it on GitHub, or unsubscribe. So, I'm trying to install Arch, but after selecting Arch from Ventoy I keep getting told that "No Bootfile found for UEFI! You can have BIOS with TPM and disk encryption and, provided your hardware manufacturer implements anti tampering protection to ensure that the TPM is not sharing data it shouldn't share with parts of the system that should not be trusted, it should be no less secure than TPM-based encryption on a Secure Boot enabled system. what is the working solution? This iso seems to have some problem with UEFI. The injection is just like that I extract the ubuntu.iso and change/add some script and create an new ISO file. With ventoy, you don't need to format the disk over and over, you just need to copy the ISO/WIM/IMG/VHD (x)/EFI. 22H2 works on Ventoy 1.0.80. No boot file found for UEFI (Arch installation) - reddit Happy to be proven wrong, I learned quite a bit from your messages. The idea that Ventoy users "should know what they are getting into" or that "it's pointless to check UEFI bootloaders for Secure Boot" once Ventoy has been enrolled is disingenuous at best. Already on GitHub? etc. @ventoy I can confirm this, using the exact same iso. Great , I also tested it today on Kabylake , Skylake and Haswell platforms , booted quickly and well. Some bioses have a bug. Thank you Thank you very much for adding new ISOs and features. Ventoy does not always work under VBox with some payloads. @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: netboot.xyz-efi.iso (v2.0.17), manjaro-gnome-20.0.3-200606-linux56.iso, Windows10_PLx64_2004.iso worked fine. if this issue was addressed), it could probably be Secure Boot signed, in the same manner as UEFI:NTFS was itself Secure Boot signed. @chromer030 hello. Now Rufus has achieved support for secure boot as now NTFS:UEFI Driver is signed for secure boot by Microsoft. ParagonMounter 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. You answer my questions and then I will answer yours MEMZ.img was listed with no changes for me. In that case there's no difference in booting from USB or plugging in a SATA or NVMe drive with the same content as you'd put on USB (and we can debate about intrusion detection if you want). It is designed to protect a system against malicious code being loaded and executed early in the boot process, before the operating system has been loaded. Windows 10 32bit Hiren's BootCD Would disabling Secure Boot in Ventoy help? Option 3: only run .efi file with valid signature. An encoding issue, perhaps (for the text)? 1. Solved: UEFI boot cannot load Windows 10 image - Dell So if the ISO doesn't support UEFI mode itself, the boot will fail. Copyright Windows Report 2023. Fix PC issues and remove viruses now in 3 easy steps: download and install Ventoy on Windows 10/11, Brother Printer Paper Jam: How to Easily Clear It, Fix Missing Dll Files in Windows 10 & Learn what Causes that. regular-cinnamon-latest-x86_64.iso - 1.1 GB, openSUSE-Tumbleweed-GNOME-Live-x86_64-Snapshot20200326-Media.iso - 852MB On one of my Laptop Problem with HBCD_PE_x64.iso Uefi on start from Desktop error with Autoit v3: Pintool.exe Application error. I am getting the same error, and I confirmed that the iso has UEFI support. Many thousands of people use Ventoy, the website has a list of tested ISOs. Ctrl+i to change boot mode of some ISOs to be more compatible Ctrl+w to use wimboot to boot Windows and WinPE ISOs (e.g. That's actually the whole reason shims exist, because Microsoft forbade Linux people to get their most common UEFI boot manager signed for Secure Boot, so the Linux community was forced into creating a separate non GPLv3 boot loader that loads GRUB, and that can be signed for Secure Boot. Ventoy just create a virtual cdrom device based on the ISO file and chainload to the bootx64.efi/shim.efi inside the ISO file. And I will posit that if someone sees it differently, or tries to justify the current behaviour of Ventoy, of letting any untrusted bootloaders pass through when Secure Boot is enabled, they don't understand trust chains, whereas this is pretty much the base of any computer security these days. They can't eliminate them totally, but they can provide an additional level of protection. How to Create a Multiboot USB With Ventoy - MUO - Technology, Simplified. @pbatard Agreed. 1. I am not using a grub external menu. This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. UEFI Secure Boot (SB) is a verification mechanism for ensuring that code launched by a computer's UEFI firmware is trusted. Open File Explorer and head to the directory where you keep your boot images. Ventoy can boot any wim file and inject any user code into it. But unless it exploits a Secure Boot vulnerability or limitation (or you get cozy with the folks controlling shim keys), that bootloader should require to be enrolled to pass Secure Boot validation, in the same manner as Ventoy does it. TPM encryption has historically been independent of Secure Boot. Insert a USB flash drive with at least 8 GB of storage capacity into your computer. we have no ability to boot it unless we disable the secure boot because it is not signed. This will disable validation policy override, making Secure Book work as desired: it will load only signed files (+ files signed with SHIM MOK key). evrything works fine with legacy mode. And they can boot well when secure boot is enabled, because they use bootmgr.efi directly from Windows iso. 10 comments andycuong commented on Mar 17, 2021 completed meeuw mentioned this issue on Jul 31, 2021 [issue]: Can't boot Ventoy UEFI Native (Without CSM) on HP ProBook 640g1 #1031 BUT with Ventoy 1.0.74 legacy boot from the same ISO I get a black square in centre of menu (USB LED is flashing so appears to load). (I updated to the latest version of Ventoy). and reboot.pro.. and to tinybit specially :) preloader-for-ventoy-prerelease-1.0.40.zip, https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532, [issue]: Instead of dm-patch, consider a more secure and upstreamable solution that does not do kernel taint. And if you somehow let bootloaders that shouldn't be trusted through, such as unsigned ones, then it means your whole chain of trust is utterly broken, because there simply cannot even exist a special case for "USB" vs "something else". @pbatard I'm not sure whether Ventoy should try to boot Linux kernel without any verification in this case (. This option is enabled by default since 1.0.76. It means that the secure boot solution doesn't work with your machine, so you need to turn off the option, and disable secure boot in the BIOS. https://forum.porteus.org/viewtopic.php?t=4997. Some questions about using KLV-Airedale - Page 4 - Puppy Linux WinPE10_8_Sergei_Strelec_x86_x64_2019.12.28_English.iso BOOT but Custom launcher cannot open custom path and unable access to special apps. In a fit of desperation, I tried another USB drive - this one 64GB instead of 8GB. due to UEFI setup password in a corporate laptop which the user don't know.