Cannot access the BIOS after August 2024 Windows update in Swift 3

el56

I have a Swift 3 that dual boots Windows and Linux.

Everything has been working fine until now. However, after the August Windows update (specifically, KB5041585) upon bootup this message appears:

“Verifying shim SBAT data failed: Security Policy Violation
Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation”

The recommended temporary solution is to go into the BIOS and disable secure boot until Microsoft supplies a remedy. However, I cannot access the BIOS. Pressing F2, Fn+F2 or F10 just keeps the screen frozen, sometimes displaying the above message. Sometimes the laptop shuts down after displaying the message.

I can actually get to both the Linux and Windows systems by pressing F12 and then selecting which to boot to. But I cannot get to the BIOS by any know means. Please advise.

[Edited the thread to add model number to the title]

StevenGen

https://community.acer.com/en/discussion/714053/cannot-access-the-bios-after-august-2024-windows-update-in-swift-3

The Win-11 August 13, 2024—KB5041585 (OS Builds 22621.4037 and 22631.4037) is an update that makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates, this is clashing with Linux, if you want to use Linux more than Win-11, I suggest that you delete this update if you want to use Win-11 and/or update it to the latest version 24H2 OS build: 26100.2033 and/or follow the below guides, good luck and hope this helps you out.

The error message “Verifying shim SBAT data failed: Security Policy Violation Something has gone seriously wrong: SBAT self-check failed: Security Policy Violation” typically occurs when there’s an issue with the Secure Boot Advanced Targeting (SBAT) data in your system’s UEFI firmware. This can happen due to a recent update or changes in the system’s security policies.

Here are some common causes and solutions:

1. Recent Updates: This error has been reported after certain Windows updates. If you can access Windows, you might try uninstalling the recent update.
2. Dual Boot Systems: If you’re dual-booting Windows with Linux, this error might be more common. You can try disabling Secure Boot temporarily to see if it resolves the issue12.
3. reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\SBAT /v OptOut /d 1 /t REG_DWORDThen, restart your computer.
4. Secure Boot Settings: You can also try changing the Secure Boot settings in your BIOS. Some users have found success by setting the target OS for Secure Boot to “Other OS” instead of "Windows"2.
5. Updating Shim: Ensure that you have the latest version of the Shim bootloader, as older versions might be blacklisted.

If this answers your question and solved your query please "Click on Yes" or "Click on Like" if you find my answer useful👍