I'm using ventoy ventoy/Ventoy#1080
lubuntu-20.10-desktop-amd64.iso not working
Failed to set MokListRT

ENG: Is it possible to install this image on Windows 10-11 as a rEFInd in a hidden partition and NOT on a flash drive?
If so, how different is the installation?

RU: Можно ли установить этот образ на Windows 10-11 как rEFInd в скрытый раздел, а НЕ на флешку?
Если да, то насколько отличается установка?

Hello, i have been looking a solution to install linux by bypassing secure boot. Can you tell me how to use this exactly? because i thought it requires to put an .iso in /iso/ folder i.e kali, I'm currently using this with ventoy or should i need to copy files from ./Boot folder into another /Boot folder (in Parrot Os's .iso) and paste them to bypass signature error ? Because i enrolled the certificate via efi and nothing changed at all. I mean, i don't probably know how to use and i really wanted to. Best regards

i have pre-installed ubuntu partition with full root/physical access. can i overwrite existing grub2 files with these to disable secureboot?

Перенёс файловую структуру в корень tftp-сервера, дополнительно скопировав все файлы из EFI/BOOT и каталог EFI/grub в корень. DHCP-сервер настроен так:

} elsif substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
                next-server 10.10.10.10;
                option option-66 "10.10.10.10";
        if option arch = 00:06 {
                filename "bootia32.efi";
        } elsif option arch = 00:07 {
                filename "bootx64.efi";
        } else {
                filename "pxelinux.0";
        }

После добавления ключей через MOK (аддон через ZeroNet скачал, но пока не добавлял) происходит загрузка, но пишет ошибку failed to start grubx64_real.efi: (14) Not Found

Кусок syslog:

in.tftpd[16105]: remap: input: bootx64.efi
in.tftpd[16105]: remap: done
in.tftpd[16105]: RRQ from 10.10.10.112 filename bootx64.efi
in.tftpd[16105]: tftp: client does not accept options
in.tftpd[16106]: remap: input: bootx64.efi
in.tftpd[16106]: remap: done
in.tftpd[16106]: RRQ from 10.10.10.112 filename bootx64.efi
in.tftpd[16108]: remap: input: grubx64.efi

Если делать как написано тут - меню grub появляется, ubuntu начинает ставиться и в syslog гораздо больше информации о запрошенных файлах.

Could you also provide a g2ldr or core.img file in the download please or suggest a way in which I can add this to an existing grub4dos USB drive without having to run linux and the .sh script, etc and overwite the PBR? Thanks.

....

Hi. I'm trying to boot a customized distro that I made without luck.
I put your image in a usb drive via dd and then added a new partition with gparted.
I then changed the grub.cfg file in order to search the root filesystem by label to complete boot.

When I start the pc some screen flashes occurs and the a message says that /vmlinux was not found.
pressing a key appears a message that says that both default and fallback entries failed.
Then my grub menu is shown but if I try to go ahead a new /vmlinux was not found message is printed.

Can you help me?
Thanks in advance

please help. factory bios settings not working.

O

I have a Dell AW3821DW 3840x1600 wide-screen gaming monitor connected to a Nvidia RTX 3080 GPU over a DisplayPort connection.

When initially booting into Ventoy with Secure Boot enabled in BIOS, I expected the UEFIinSecureBoot to indicate a boot security failure and bring up the screens for the initial MOK registration.

However, I only see a black screen, without a cursor.

When I disconnected the 3840x1600 wide screen and connected an old 1024x1280 screen to my GPU over an HDMI connection, I do see the expected UEFIinSecureBoot boot security failure displays when I rebooted Ventoy.

Something is preventing the UEFIinSecureBoot from displaying properly on my 3840x1600 display.

I have an MSI X570 ACE motherboard with a 5950X processor and the latest MSI BIOS firmware loaded.

I am attempting to register the ENROLL_THIS_KEY_IN_MOKMANAGER.cer keys in MOK Manager.

With SECURE BOOT=STANDARD (Enabled) in the UEFI BIOS, I booted from a USB drive loaded with the Super-UEFIinSecureBoot-Disk_v3 image.

When my system boots up, I see the expected Access Denied error message. But when I get to the Perform MOK management screen and select Enroll key from disk, the screen freezes and I have to power down the PC to reboot. I can't get to the screen that shows the ENROLL_THIS_KEY_IN_MOKMANAGER.cer file selection to register the keys.

Wimboot support would be good as a feature.

Hello.
First of all, thanks for creating this rep it's really helpful.

i want to asking about is there anyway to chainload a windows booted by BIOS in （if [ "${grub_platform}" == "efi" ]）？

when i use ntldr /bootmgr，i get error ：can't find command 'ntldr'

sorry if i asking in wrong place.. it's possible to boot winpe using grub2 in uefi with wimboot ?? if so how ?

surface pro 7，windows11，unsupported format

Распотрошил Super UEFIinSecureBoot Disk, скопировал на ssd, прописал через mokmanager сертификат.

Грузится до grubx64_real.efi, дальше ядро не грузит.

Если grubx64_real.efi из Super UEFIinSecureBoot Disk, то ядро не грузит (ошибку забыл но не shim_lock). Может надо через chainloader дальше грузить мой grub2 а потом уже ядро?

Если grubx64_real.efi подменяю своим (неподписанным), то grub и меню нормально запускаются, но ошибка shim_lock protocol not found при загрузке ядра.

Since this project is using Fedora's shim, beware that the shim that shipped with Fedora 37 and 38 doesn't work on some motherboards. Fedora 36 was the last working shim. They're working on Microsoft certification of the fixed shim. So be sure that this project doesn't use any of the broken shims. :)

Here's the upstream info:

A problem was identified and fixed in Fedora's "shim" UEFI bootloader. Unfortunately, due to a difficult certification process for this component, the fix isn’t present on Fedora 37 nor Fedora 38 install media.

https://discussion.fedoraproject.org/t/install-media-dont-boot-in-uefi-mode-on-certain-motherboards/71376

https://bugzilla.redhat.com/show_bug.cgi?id=2113005

Hello. At that platform page, link "from Fedora" is obsolete. that is the valid link for Packages section. As noticeable, a search against the package named shim-signed won't return match, therefore that package name too is obsolete.

grub command linux16 is missing

not a big deal, just copy it from other sources, but it would be better to include it

Many Ventoy users report that with
Super-UEFIinSecureBoot-Disk v3.4, it report error when Secure BOOT is disabled in the BIOS. With v3.3 it was OK.
ventoy/Ventoy#1707

Hi,
Above all, thanks for your great S-U-D.

I've got a problem

https://ftp.gnu.org/gnu/grub/
What I use is grub-2.06-for-windows.zip.
How do I apply your security bypass patches to chainloader, linux/linuxefi and shim？

Is there a linux.mod, chain.mod or kernel.img patched with security bypass?

Hi, i have a laptop Aorus 17G XC and its my fifth day of trying to boot a live version of kali linux. I have tried every possible tutorial and and i cannot get trough. Right now im stuck at error: prohibited by secure boot policy in grub and have no idea what to do next. Ive read somewhere that you can help directly with the issue so ive decided to write here. I tried many manual fixes but lastly i tried ventoy with secure boot support enabled. It launches nicely and then when the grub shows up with the menu to start live or smth like that it just shows this "error: prohibited by secure boot policy". Have you got any clue what am i doing wrong?

git clone /home/smopro/ZeroBundle/ZeroNet/data/1KVD7PxZVke1iq4DKb4LNwuiHS4UzEAdAv/silent-uefiinsecureboot-disk.git 
fatal: репозиторий «/home/smopro/ZeroBundle/ZeroNet/data/1KVD7PxZVke1iq4DKb4LNwuiHS4UzEAdAv/silent-uefiinsecureboot-disk.git» не существует

Арч линукс, зеро нет Version: 0.6.5 r3862, Python 2.7.11

Hello,
On new motherboards such as Gigabyte B550 Vision D-P, the UEFI comes out of the box with Microsoft UEFI CA issued in 2011 in the revoked keys list, so all such motherboards will refuse to boot the shim version used in this project.

It is recommended to use the shim version of a recent linux distribution such as ubuntu or opensuse.

Details about the revocation:
https://support.microsoft.com/en-us/topic/microsoft-guidance-for-applying-secure-boot-dbx-update-kb4575994-e3b9e4cb-a330-b3ba-a602-15083965d9ca