A recent security update from Microsoft is causing problems for computers that run both Windows and Linux.
The update, released last week, was designed to fix a vulnerability in GRUB, a widely used open-source boot loader for Linux. While the patch was not intended for dual-boot systems, many users have reported that it prevents their Linux installations from booting correctly.
Users of dual-boot systems, running both Windows and Linux, are reporting widespread boot problems following a recent Microsoft security update. The issues, affecting various Linux distributions including Ubuntu, Debian, Linux Mint, Zorin OS, and Puppy Linux, stem from a patch designed to address a vulnerability in the GRUB boot loader.
As reported by Ars Technica, numerous users have encountered error messages such as “security policy violation” and “something has gone seriously wrong” when attempting to boot into their Linux installations. These problems have been widely reported on platforms like Reddit and Ubuntu forums.
Microsoft’s recent security update, intended to address a vulnerability in the GRUB boot loader, has inadvertently impacted dual-boot systems despite the company’s assurances to the contrary. The update was designed to prevent hackers from exploiting a flaw that allowed them to bypass Secure Boot, a crucial security feature used by both Windows and Linux to prevent loading malicious firmware during startup.
Microsoft had previously stated that the update, which applies a Secure Boot Advanced Targeting (SBAT) mechanism, would not be deployed on systems configured for dual-booting Windows and Linux. The company asserted that the update “should not affect these systems.” However, numerous user reports contradict this claim, indicating that the update is indeed causing boot problems on dual-boot setups.
While Microsoft has yet to comment on the boot problems caused by its recent security update, a workaround has surfaced for users of the Ubuntu Linux distribution. This solution involves temporarily disabling the Secure Boot feature in the computer’s BIOS settings. After disabling Secure Boot, Ubuntu users can regain access to their operating system by logging into their Ubuntu account and executing a command in the terminal to remove Microsoft’s SBAT policy, which is the root cause of the boot issue.