Windows update KB5041580 seems to break BootIt UEFI 1.44 installation

[AGH1965]

Yesterday one of the Windows 10 boot partitions of my pc with BootIt UEFI 1.44 was updated with Windows update KB5041580. After completion of this update, when booting, after the BIOS screen disappears, BootIt UEFI doens't show up anymore. Instead there appears an error message starting with "Verifying shim SBAT data failed", which disappears after a few seconds and then my pc reboots. This secence of error message - rebooting - error message - rebooting - error message - ... goes on forever.

When I used another pc for a Google search, I only had to type "verifying" and Google added automatically "shim sbat data failed". The search results are all very recent. So it seems lots of people have trouble with Windows update KB5041580. However, Google's search results all seem Linux related. Many search results suggest that the problem disappears after updating to a more recent boot loader version.

Did this Windows update really break my BootIt UEFI 1.44 installation? How can I fix it? If I would need an updated bootloader, would that mean that I need to upgrade to BootIt UEFI 2.0?

[TeraByte Support]

You would need to upgrade to V2.x

[AGH1965]

Maybe I misunderstand, as English is not my native language. Are you saying that BootIt UEFI 1.44, which was introduced earlier this year, is not compatible with KB5041580, but that I can get compatibility by upgrading to BootIt UEFI 2.02?

[TeraByte Support]

Version 2.x has the latest secure boot signatures.

[AGH1965]

Is it correct that Microsoft updated Secure Boot with KB5041580 and because of that BootIt UEFI 1.44 is no longer recognized as a safe boot loader?

[TeraByte Support]

Yes, it says:

[Secure Boot Advanced Targeting (SBAT) and Linux Extensible Firmware Interface (EFI)] This update applies SBAT to systems that run Windows. This stops vulnerable Linux EFI (Shim bootloaders) from running. This SBAT update will not apply to systems that dual-boot Windows and Linux. After the SBAT update is applied, older Linux ISO images might not boot. If this occurs, work with your Linux vendor to get an updated ISO image.

[ohaya1000]

Hi - I hope this is ok but I'm in the same boat... rebooted my Dell Vostro with Bootit UEFI and Windows 10 this morning and got that same "shim sbat" error at boot.

I only have Windows 10 on it, not linux or other Windows.

I'm not sure what version of Bootit I have but are you saying JUST install Bootit UEFI latest version and then the machine should boot again?

If I should start a separate thread please let me know?

Thanks,
Jim

[TeraByte Support]

yes or disable secure boot.

[ohaya1000]

Hi,

WOWZA !!!

I purchased update license (nice discount TOO !!

Then I downloaded the BOOTIT COLL 2 ZIP file.

Unzipped the file.

Formatted a USB stick

Run MakeDisk to install BIU 2.02 on the USB stick.

Rebooted the machine and go to Boot menu (F12) and select the BIU and it boots and I install BIU 2.02.

Reboot and I get the BIU menu and boot into Windows 10 !!

Super!!

[ohaya1000]

Terabyte - I was really concerned about turning off secure boot, less I get stuck after that, so I did NOT want to go that route.

Going the way I posted seemed much safer, plus it's about time, I bought something again from you all after ALL of these years and ALL of the odd times that I've had odd problems !!!

Haha - just kidding!

Jim