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

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

What you need to know

  • Some dual-boot devices running Windows and Linux are unable to boot after a recent update from Microsoft.
  • The security update fixed a two-year-old vulnerability in GRUB, which is an open source boot loader used on many Linux devices.
  • The update was not supposed to ship to dual-boot systems, but it was sent out to them, seemingly by accident.
  • Affected devices are unable to boot and show an error message stating, “something has gone seriously wrong.”

As a seasoned researcher with decades of experience in the tech industry, I can’t help but shake my head at the latest debacle involving dual-boot systems. The incident where Microsoft’s security update, intended for a two-year-old vulnerability in GRUB, left many Linux and Windows dual-boot users stranded with an error message that read “something has gone seriously wrong,” is a classic case of good intentions paving the wrong path.


In many situations, having two instead of one can be advantageous, and this is especially true when it comes to computer operating systems. While running both Windows and Linux on the same machine through dual booting is quite common, some users might currently encounter a problem. This predicament arises due to an error by Microsoft, causing these dual-boot systems to fail and display an alarming message: “Something catastrophic has occurred.”

As a researcher, I encountered an error message on several systems last week, following Microsoft’s monthly security update release. This update apparently addressed a longstanding vulnerability in GRUB, a widely-used open-source boot loader for many Linux systems. The fact that it took two years to fix this issue leaves me puzzled. It seems the update was not intended for dual-boot systems running both Windows and Linux, yet it appeared on those machines unintentionally.

“The Security Bulletin from Microsoft states that the SBAT value is not relevant for systems that can boot both Windows and Linux. This should not cause any issues within these dual-boot setups. However, you might encounter situations where older Linux distribution ISOs fail to start. If this happens, collaborate with your Linux vendor to obtain an update.”

The following error message appears on affected systems:

1. “The process of validating Shim SBAT data encountered a security policy violation. This suggests a significant issue: The self-check for SBAT also failed, reporting a security policy violation.”

As an analyst, I delved into the digital realm to shed light on a pressing matter, sparking conversations across various platforms. On Reddit and forums dedicated to Ubuntu and Linux Mint, threads were initiated. The scope of this issue seemed far-reaching, encompassing numerous Linux distributions such as Debian, Linux Mint, Puppy Linux, Ubuntu, and Zorin OS. Ars Technica provided valuable insights into the situation with additional context.

As a tech enthusiast, I’ve run into an unexpected hiccup with my device – Microsoft hasn’t pinpointed the root cause yet. However, Ars Technica offers a workaround that might help. On Tuesday, August 13, 2024, they suggest deleting the SBAT (System Boot Application Technology) that could be causing the issue. To do this, you’ll need to temporarily disable secure boot, delete the problematic SBAT, and then re-enable secure boot again. It’s a bit of a dance, but it might just get your device humming along smoothly once more!

Read More

2024-08-21 15:09