Hello Beelink Support,
Could your firmware team help investigate a Secure Boot/PCR7 measurement issue on my SER10 MAX?
System details
The installed BIOS version matches the downloaded package. The local ZIP has the same SHA-256 hash as a fresh download, and all 15 extracted files match the official archive.
TPM and Secure Boot appear operational. SecureBoot is 1, SetupMode is 0, and PK/KEK/db/dbx are readable. Measured Boot health reports “Attestable,” with TpmIsResponsive and PcrsMatchTcgLog both true.
However, the BitLocker Management log repeatedly reports Event 813:
“BitLocker cannot use Secure Boot for integrity because the expected TCG Log entry for variable ‘CurrentPolicy’ is missing or invalid.”
Event 893 also reports that the filtered PCR7 TCG log is invalid for Secure Boot integrity validation. The latest two Measured Boot logs contain SecureBoot, PK, KEK, db and dbx measurements, but no CurrentPolicy variable measurement was found.
I read your V105 support discussion about Microsoft Security Levels and Firmware Protection:
#12196
Could you please clarify:
- Is this a known issue with SERM2 V105 .11 and Windows 26H1?
- How do SERM1 and SERM2 differ, and how should the correct package be matched to a hardware revision?
- Do the “Standard” and “fTPM only” recommendations apply to my BIOS? Could they affect CurrentPolicy/PCR7 measurements?
- Is there a corrected firmware or safe diagnostic procedure that preserves TPM contents, Secure Boot keys and existing BitLocker protectors?
I can provide my serial number and additional diagnostic details privately if needed.
Thank you.