The platform firmware on this device extends PCR[0] with measurements that are not
recorded in the TCG event log. As a result, TCG log replay does not reproduce the
hardware PCR[0] value, and remote attestation (Microsoft Azure Attestation) fails.
SYSTEM
- Model: Acer Predator PHN16-73, baseboard Macan_ARX
- Firmware: INSYDE Corp. V1.26 (2026-02-23) — latest published by the OEM
- CPU: Intel Core Ultra 7
- TPM: Intel PTT (INTC), firmware 700.19.5.1992
- OS: Windows 11, build 26200, fully updated
- Secure Boot: enabled, Standard mode, UEFI, GPT
THE PROBLEM
Windows TPM-WMI Event ID 1041 (Attestation Readiness Verifier) reports on every boot:
"HealthStatus": "Possibly attestable",
"Expected": [{
"Field": "PcrsMatchTcgLog",
"Value": false,
"DesiredValue": true,
"DiagnosticInfo": {
"SoftwarePcrReplayHresult": 0,
"HardwarePcrReplayHresult": 0,
"BitMaskOfPcrMismatches": 1
}
}]
Both replay HRESULTs are 0 — the replay operation itself succeeds. The values simply do
not match. BitMaskOfPcrMismatches = 1 identifies PCR[0], the platform firmware
measurement register.
This appears to be non-conformance with the TCG PC Client Platform Firmware Profile
Specification, which requires every PCR extension to have a corresponding event recorded
in the log.
WHAT PASSES
TpmPresent : true
TpmMeetsMinimumVersion : true
TpmIsResponsive : true
EkCertIsAvailable : true
TcgLogFound : true
SecureBootEnabled : true
WindowsAikCertRsa2048IsAvailable : true
WindowsAikCertEccP256IsAvailable : true
WindowsAikCertEccP384IsAvailable : true
tpmtool getdeviceinformation reports "Ready For Attestation: True".
Secure Boot 2023 CAs applied and verified (KEK 2023, Windows UEFI CA 2023,
Microsoft Option ROM UEFI CA 2023).
CORRELATED SYMPTOMS
- SmmIsolationLevel: 0
- System Guard Secure Launch appears in SecurityServicesConfigured but not in SecurityServicesRunning
- Firmware Protection cannot be enabled from Windows Security > Device security; clicking Enable and rebooting has no effect
ALREADY RULED OUT
Clearing the TPM; TPM reprovisioning and AIK re-enrollment; restoring Secure Boot factory
keys in firmware; enabling VT-x, VT-d, VBS and Memory Integrity; full cold boot; latest
BIOS confirmed. Another user with the identical model reports the same result after clean
installs of both Windows 11 Home and Pro.
BROADER SCOPE
The same defect is reported on HP OMEN Max 16 with Insyde F.22 firmware, which suggests
an issue originating at the IBV level rather than with a single OEM.
QUESTIONS
- Is there any supported way to inspect which PCR[0] event is missing or malformed, short of a firmware debugger? I have the TCG logs from C:\Windows\Logs\MeasuredBoot and the output of tpmtool gatherlogs.
- Does a device in this state have any path to passing MAA, or is an OEM firmware fix the only remedy?
- Is there a channel through which Microsoft flags measured boot conformance failures back to OEMs and IBVs? The device is being sold as supporting TPM 2.0, Secure Boot and Secured-core PC features that it cannot actually deliver.