Firmware does not log all PCR[0] events to the TCG event log — measured boot replay fails, attestation blocked (Acer PHN16-73, Insyde V1.26, Intel PTT)

Matheus Santana 0 Reputation points
2026-07-26T01:31:35.8933333+00:00

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

  1. 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.
  2. Does a device in this state have any path to passing MAA, or is an OEM firmware fix the only remedy?
  3. 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.
Windows for home | Windows 11 | Performance and system failures
0 comments No comments

2 answers

Sort by: Most helpful
  1. Carl-L 25,345 Reputation points Microsoft External Staff Moderator
    2026-07-28T06:33:52.3066667+00:00

    Hello Matheus Santana,

    Welcome to Microsoft Q&A forum.

    Based on the description, I believe your assumption is correct, this is highly likely not a TPM, AIK, secure boot or configuration issue. For your first questions, as I know, there is no official Microsoft tool to check where a PCR0 event is from, at least not alone. Microsoft official way can give you the logs and relevant information, but it is unable to tell which one cause it exactly. You will need a third-party tool to parse the information.

    Regarding the second question, the short answer is no. If any verifier requires consistency in PCR0 replay, then a firmware fix is required.

    This is a public forum, so forum moderators are unable to know about what happened in backend side. However, from what I know, even if Microsoft does report to OEM for this, there is no known way that is visible to customers.

    I hope this clarifies.

    Was this answer helpful?


  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.