Unfortunately I found out soon after that the command to confirm the applied certs was a false positive. The PC froze up sometime later.
Here’s the event in Eventviewer:
Updated Secure Boot certificates are available on this device but have not yet been applied to the firmware. Review the published guidance to complete the update and maintain full protection. This device signature information is included here.
DeviceAttributes: BaseBoardManufacturer:AZW;FirmwareManufacturer:American Megatrends International, LLC.;FirmwareVersion:SER6p_P5C8V11;OEMModelNumber:SER;OEMModelBaseBoard:SER;OEMModelSystemFamily:SER;OEMManufacturerName:AZW;OEMModelSKU:06;OSArchitecture:amd64;
BucketId: a0712dd7e03988c5f5a138c0bc7ec31ad9491b008571c64619db34bfb232f236
BucketConfidenceLevel: High Confidence
UpdateType: Windows UEFI CA 2023 (DB), Option ROM CA 2023 (DB), 3P UEFI CA 2023 (DB), KEK 2023, Boot Manager (2023)
For more information, please see https://go.microsoft.com/fwlink/?linkid=2301018.
And I’m trying the following command (in elevated powershell) to prevent Windows from trying to apply that update for now. Hopefully this will help prevent the freezes.
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot" -Name "AvailableUpdates" -Value 0
I’ll report back but, for Beelink support, are there BIOS version updates in the works to support these certificate updates which appear to currently be unsupported and causing issues for some?