August 21st, 2024

Dual-boot systems fail after Microsoft update

Microsoft's update to fix a GRUB vulnerability caused boot failures in dual-boot systems, affecting Linux distributions. Users reported issues, and Microsoft has not acknowledged or provided support for the problem.

Read original articleLink Icon
Dual-boot systems fail after Microsoft update

A recent Microsoft update intended to address a significant vulnerability in the GRUB bootloader has inadvertently caused issues for many dual-boot systems running both Windows and Linux. Users began reporting boot failures with the error message, “Something has gone seriously wrong,” after the update was applied. The vulnerability, rated 8.6 out of 10 in severity, allowed potential bypassing of Secure Boot, a security feature designed to prevent malicious software from loading during startup. Despite Microsoft's assurances that the update would not affect dual-boot systems, it has rendered many devices unable to boot into Linux when Secure Boot is enabled. Affected distributions include popular ones like Ubuntu, Debian, and Linux Mint. Microsoft has not publicly acknowledged the issue or provided guidance for affected users, leaving them to seek solutions independently. One workaround involves disabling Secure Boot or deleting the SBAT policy introduced by the update. This incident highlights ongoing concerns regarding the reliability of Secure Boot and the complexities involved in managing security across different operating systems.

- Microsoft’s update intended to fix a GRUB vulnerability caused boot failures in dual-boot systems.

- Users received error messages indicating a serious issue after the update was applied.

- The update affected multiple Linux distributions, despite Microsoft’s claims it would not.

- Microsoft has not acknowledged the problem or provided support for affected users.

- Workarounds include disabling Secure Boot or deleting the SBAT policy.

Link Icon 5 comments
By @smittywerben - 5 months
Microsoft, still trembling from CrowdStrike's 8-million-system massacre, now claims their antitrust ruling is unfair for letting users install CrowdStrike to begin with. The eternal "POSIX for Windows" vs "Windows Subsystem for POSIX" rages on. The end result: Microsoft Store becomes the only way to use Windows's Windows, so we're stuck with shitty Electron text editors from Microsoft to code with. The end result: The Windows Phone. I have to quick exit this thread now.
By @dcan - 5 months
Ah. I ran into this last weekend when installing Linux to a secondary partition. I just disabled secure boot, good to know there is a proper workaround
By @rolph - 5 months
grub is borked when ms tries to mitigate a possible exploit.

sudo mokutil --set-sbat-policy delete

By @aurelien - 5 months
MicroPr0n!