An Azure service that is used to provision Windows and Linux virtual machines.
Trusted Launch: Guest Attestation Failure on Linux VMs Due to Event Log Truncation — PCR Mismatch
Problem description
I am experiencing guest attestation failures on three production Trusted Launch Linux VMs running Ubuntu. The attestation used to succeed until late October 2025, but after a routine reboot around October 26, 2025, all three VMs began rejecting attestation requests. The error indicates that the measured boot event log does not replay to the PCR values reported by the VM’s virtual TPM, specifically failing at PCR 4 with a PcrDoesNotMatchTcg error.
Environment
Three production Ubuntu virtual machines using Trusted Launch in East US, with Secure Boot enabled and virtual TPM active.
What I've already tried
I verified core Trusted Launch prerequisites, including Secure Boot, vTPM, and kernel integrity. Outbound connectivity to the attestation endpoint was checked but did not resolve the issue. The same failure pattern appears across all three VMs at the same timestamps, suggesting a shared platform change. Diagnostics captured a guest restart but did not reveal irregularities. I also tested on an existing VM in a separate subscription, which showed similar event log truncation, indicating a possible platform or firmware issue.
Current status
Currently, guest attestation continues to be rejected before boot health evaluation because the event log does not replay to the PCR 4 value. I am seeking guidance on whether event log truncation is a known issue, how to check for firmware or vTPM updates around the failure time, and steps to resolve this problem.