Microsoft breaks dual-boot Windows and Linux PCs with security update sent to wrong systems

What you need to know

In a twist of fate for tech enthusiasts, a recent Microsoft update has inadvertently caused a disruption for users of dual-boot systems that run both Windows and Linux. While the practice of dual booting is celebrated for its versatility, many users are now facing an unexpected hurdle.

  • Some dual-boot devices are currently unable to boot following a security update from Microsoft.
  • This update addressed a two-year-old vulnerability in GRUB, the open-source boot loader that serves as a gateway for many Linux devices.
  • Despite the update’s intention, it was mistakenly rolled out to dual-boot systems, leading to significant booting issues.
  • Affected users are greeted with a rather ominous error message: “something has gone seriously wrong.”

As the adage suggests, two is often better than one, especially when it comes to operating systems. However, for those who have embraced the dual-booting lifestyle, the recent Microsoft security update has introduced a rather unwelcome complication. The error message, which surfaced last week, has left many users in a state of frustration.

The update was designed to rectify a longstanding vulnerability in GRUB, yet its unintended deployment to dual-boot systems has raised eyebrows. The error message displayed on affected devices reads: “Verifying shim SBAT data failed: Security Policy Violation. Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation.”

In the wake of this incident, users have taken to online forums and platforms like Reddit to share their experiences and seek solutions. A variety of Linux distributions, including Debian, Linux Mint, Puppy Linux, Ubuntu, and Zorin OS, have been reported as impacted by this issue. Ars Technica has provided additional insights into the situation, although Microsoft has yet to officially confirm the root cause of the problem.

For those looking for a workaround, Ars Technica suggests a potential solution: temporarily disabling secure boot to delete the SBAT that was included in the update released on August 13, 2024. After this step, users can re-enable secure boot to restore functionality.

Winsage
Microsoft breaks dual-boot Windows and Linux PCs with security update sent to wrong systems