![]() Method 2: Disable driver signature enforcement. Disable the secure boot option and check. Restart the computer keep pressing the Boot menu option key to enter the boot menu. Nevertheless, I've found some nice Ubuntu based documentation how to do the secure boot part, in case you chose to try. When your computer starts, wait for the manufacturer logo to check the option for boot menu, it will usually be any of the function key (eg: F12). I guess the difficulty is way beyond intermediate level sysadmin skills. If you wish to learn by this it may be worth doing, otherwise it's just a waste of time. The LM21.1 ISO was made in December before Microsoft made their changes. If you run Ubuntu 22.02.01, it will also fail. Microsoft recently changed the certs so older ISOs do not have the new certs. This may take days or weeks to solve it this way. There is already a topic on this exact message Verification failed: (0x1A) Security Violation while installing Linux Mint 21.1. If issues arise (yes there may be problems even if you have related experience) you have to start it over and check what went wrong. Then save the results to the internal file system. ![]() Then create a chroot environment, do all the complex work needed to prepare a secure boot. Also try to save settings or press F10 and choose yes at the save dialog.Įdit: On a second thought this could be solved by signing/trusting the bootloader, kernel and kernel modules for UEFI Secure Boot too.īut to do this one has to find a live media which will still boot the machine. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |