I have an older Acer Swift 3 Notebook with Windows 10 and Debian 13.5
dual boot.
Suddenly secure boot does not work any more, probably due to updates I
installed on 18th May, which according to history.log included:
grub-efi-amd64-unsigned:amd64 (2.12-9+deb13u1, 2.12-9+deb13u2),
grub-efi-amd64:amd64 (2.12-9+deb13u1, 2.12-9+deb13u2),
grub-efi-amd64-signed:amd64 (1+2.12+9+deb13u1, 1+2.12+9+deb13u2),
grub-efi-amd64-bin:amd64 (2.12-9+deb13u1, 2.12-9+deb13u2),
grub2-common:amd64 (2.12-9+deb13u1, 2.12-9+deb13u2),
grub-common:amd64 (2.12-9+deb13u1, 2.12-9+deb13u2)
but not SHIM, nevertheless I get the bad SHIM signature error.
According to Synaptic I have installed:
shim-helpers-amd64-signed 1+15.8+1
shim-signed 1.47+15.8-1
shim-signed-common 1.47+15.8-1
shim-unsigned 15.8-1
For the time being I have disabled Secure Boot in BIOS. I did not test
whether or how Windows does boot or not (I keep it only because it was
pre-installed and I might need it some day...)
Could it be that the GRUB update broke secure dual boot?
Regards, Mike
