


The thing is, I know Linux Mint works with SecureBoot on this PC, so I'm hesitant to change this setting permanently, even though it does actually work.Īlso, I have been using CloneZilla 2.8.0-27 on the same PC and now I am getting the same verification error message as Linux Mint.

If someone in this forum can explain the benefits and risks in turning this feature off please let me know.

Some users suggest to turn SecureBoot off to remedy this issue, but without understanding SecureBoot properly, I prefer to leave it enabled. If the latter is the case, and Canonical updated their UEFI Secure Boot signing key, is there any way to reset the BIOS key, so that I can install and Linux Mint the way I used to, without issue? Or will I have to wait for the next version of Linux Mint (21.2) in June/July 2023 and hopefully the key issue is addressed in that version? Could the latest Kubuntu install have messed my BIOS settings up, which prevents me installing anything older than the current versions? Another user suggested this here. The other scenario is that the cause could have been a result of me installing Kubuntu 22.04.2 on the same PC via USB ISO (verified SHA256) just to see what it was like. There was a video suggesting the latest BIOS upgrade is the problem as it fixed BIOS security vulnerabilities, but I don't think this is the case. I thought that it may have been due to a BIOS upgrade via Dell, but I have done the same upgrades on other similar PCs and the problem isn't repeating itself - they all work okay. When I attempt the installation, it comes up with a blue screen with the text: Verification failed: (0x1A) Security Violation The strange thing is, I have used the same ISO image (verified SHA256) on this PC previously and it worked fine with no issues.įrom what I have researched, it seems to be an issue with the BIOS / UEFI key, but I am not sure what has changed since the last install of Mint. I have a problem installing Linux Mint on my Dell OptiPlex 7060 SFF PC (i7-8700) from either DVD or USB.
