- cross-posted to:
- technology@lemmy.ml
- linux@lemmy.ml
- cross-posted to:
- technology@lemmy.ml
- linux@lemmy.ml
You must log in or register to comment.
Ah, delete the windows partition. That should keep me safe.
The TLDR is that Microsoft released a secure boot update that blocked insecure versions of GRUB. This update was only meant to go out to Windows users since releasing it to dual booted users could break GRUB. However, it was accidentally also released to dual-booted users.
The fix involves disabling dual boot, running a command to reset secure boot, then re-enabling.
Secure boot borking systems? Windows assuming it’s the only OS on the machine? I’m shocked
Shocked, I tell you!
Windows assuming it’s the only OS on the machine
That’s not the case. The update was only meant to go out to Windows users. But Microsoft messed up and accidentally released to all users, or at least some who weren’t supposed to receive it. My guess is that Microsoft usually doesn’t update secure boot stuff for dual boot users and instead waits for the distro to push the update.
The bottom line is that a windows update broke grub. Again.
Newbie question: does this affect people using systemd-boot? Does anyone use systemd-boot?
I was planning to boot into Windows on one of my craptops in order to test a fix from a chip vendor whose configuration software only runs on Windows, but I guess I’ll just … not.
