Ubuntu 21.10 can load on my computer through secure boot, and the shim version is 15.4. Then refer to the official tutorial, I installed rEFInd v0.13.2 (the latest version when I posted this blog) via PPA in Ubuntu 21.10. However, when I restart the system and load rEFInd, it always fails with the message
Verification failed:(0x1A)Security Violation. I'm sure that both
refind.cer under the
EFI/refind/keys/ have been enrolled through
MokManager (Although only
refind_local.cer is needed through PPA installation).
The post also indicates that the author of rEFInd is currently studying how to solve the related problems. I hope the later versions can fix this issue.
To conclude, you need to use shim 15 to solve this problem. For this purpose, you can perform the following steps (applicable to amd64. Steps are also similar if you are on other architectures):
- Obtain MokManager and the shim efi file signed by Microsoft from Ubuntu launchpad. To achieve this, download shim_15+1552672080.a4a1fbe-0ubuntu2_amd64.deb and shim-signed_1.45+15+1552672080-064ubuntub_bed64.deb.
- Unpack the downloaded shim_15+1552672080.a4a1fbe-0ubuntu2_amd64.deb and take out the
- Unpack the download shim-signed_1.45+15+1552672080.a4a1fbe-0ubuntu2_amd64.deb, take out the
usr/lib/shim/shimx64.efi.dualsigned) Rename it to
- Go to download refind-bin-0.13.2.zip. Then create a new folder, and put the two files taken out together with the downloaded zip file into the new folder.
- Open terminal in the fore-mentioned folder, then execute the following commands:
unzip refind-bin-0.13.2.zip cd refind-bin-0.13.2 sudo ./refind-install --shim ../shimx64.efi
If you encounter any confirmation during the installation process, just enter
y to confirm.
- After restarting, if it prompts
Verification failed, refer to step 9 of the official tutorial. Select
Enroll key from disk, and then select the ESP disk where you installed rEFInd. Finally, choose the file of path
- If you use a non-Ubuntu Linux system on your computer, you can continue to import the cer files corresponding to your distributions in
EFI/refind/keysas above. Failure to do so may cause your Linux distribution to be unable to boot via rEFInd.