Closed yezivvvv closed 2 years ago
I had the same issue on a surface laptop, you can enroll the hash from the efi binary instead and it works
The certificate is already in DER format. I have a Surface 3 (not Pro), will try to boot it later, but if I recall correctly, everything worked fine earlier. Maybe the certificate is not totally valid, but I doubt.
@ValdikSS Some Ventoy users also have the same issue.
I had the same issue on a surface laptop, you can enroll the hash from the efi binary instead and it works
How do I do this?
How do I do this?
you should have two options when enrolling, enroll from cert and enroll from hash. If you select the later you need to then select the efi binary you are trying to boot to which should be "grubx64.efi" provided you haven't customized this project
Thanks. I got that working by trial and error.
Could anybody affected by this bug take a photo of the file selection dialog inside shim? Could it be that all the files are uppercased?
New version contains MokManager from shim 15.4-5, which should fix this issue. https://github.com/ValdikSS/Super-UEFIinSecureBoot-Disk/releases/tag/3-3
surface pro 7,windows11,unsupported format