Beelink CS-Bony Unfortunately, the issue was not resolved with the BIOS I received. While it includes a 2023 certificate, the PK used to verify that the certificate is legitimate was the PKfail key. This means that, at the very least, the EQ12 is not protected at all even with Secure Boot enabled. It is likely that most Beelink products share this same vulnerability.
With Secure Boot enabled, launch Windows PowerShell as an administrator and run the following command:
Get-SecureBootUEFI PK -Decoded
If the output displays “DO NOT TRUST AMI test PK,” your Beelink product is not secure, even if it shows that Secure Boot is enabled.
