How to Fix Dual Boot Issues After Recent Windows Update
Recently updates from the Windows after the dual-boot setup with Linux aren’t working. This is happening to many people. Here’s what’s happening and how you can address it.
A recent Windows update inadvertently caused issues for users who dual-boot with Linux. Specifically, many are encountering error messages such as “Verifying shim SBAT data failed: Security Policy Violation” and “SBAT self-check failed: Security Policy Violation.” This problem is impacting various Linux distributions, including Ubuntu, Debian, Linux Mint, Zorin OS, and Puppy Linux.
The update aimed to address a vulnerability related to Secure Boot, which is designed to prevent unauthorized firmware from loading during the boot process. To fix this, Microsoft applied an SBAT (Secure Boot Advanced Targeting) update. Unfortunately, this update wasn’t meant for dual-boot systems, leading to the current issues.
Also Read | iPhone 16 series launch: Everything on the release date, features and more…
Microsoft has not yet issued a statement on this matter, but Ubuntu users have a workaround. Follow these steps to resolve the problem:
1. Disable Secure Boot in BIOS: The process for this will vary depending on your PC model.
2. Log in with sudo Privileges: Access a user account that has sudo rights.
3. Verify Secure Boot Status: Use the command `mokutil –sb` in the terminal. It should display “SecureBoot disabled.” If it doesn’t, restart your PC, enter BIOS, and ensure Secure Boot is turned off.
4. Remove Microsoft’s SBAT Policy: Open a terminal and run `sudo mokutil –set-sbat-policy delete`. Reboot your computer and log in again to update the SBAT policy.
5. Re-enable Secure Boot: After completing the previous steps, reboot, enter BIOS, and turn Secure Boot back on.
By following these steps you can restore your dual-boot functionality. The windows will not bother you!
