Windows broke my installation, mokutil --set-sbat-policy delete doesn't seem to make any changes. Am I forced to keep SecureBoot off?

Question

August 13th update of Windows triggered a SBAT error: security policy violation, like in the following question:

I followed the instructions and get the following (everything executed as root):

# mokutil --list-sbat-revocations 
sbat,1,2022052400
grub,2
mokutil --set-sbat-policy delete
mokutil --list-sbat-revocations
sbat,1,2022052400
grub,2

It seems like grub,2 should be gone from the list. Is my only option to keep SecureBoot disabled?

I am familiar with the command line, but have zero familiarity with dealing with SecureBoot, since I've never had to deal with it.

score 0 · Answer 1 · answered Aug 19 '24 at 08:49

0

As said by @david, you need to do the mokutil --set-sbat-policy delete and then reboot. Then you can re-enable secure boot on your BIOS.

I hope this helps!

answered Aug 19 '24 at 08:49

mokutil --set-sbat-policy delete