Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | TPM attestation failed during Autopilot self-deploying mode — TPM chip not responding or PCR values do not match expected measurements after firmware update | Windows Event Logs | -> |
| Affected OS build range | Windows 11 23H2 | Microsoft Documentation | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Autopilot | Registry Editor | -> |
| Relevant service/endpoint URL | https://aka.ms/AutopilotTroubleshooting | Microsoft Support | -> |
| Log line signature | 0x80180026 TPM Attestation Failure | %windir%\System32\winevt\Logs\AppxDeployment-*.etl | -> |
Log Files to Check
%windir%\System32\winevt\Logs\AppxDeployment-*.etl%windir%\Panther\setupact.log
What This Error Actually Means
The error code
0x80180026 indicates a failure in the TPM (Trusted Platform Module) attestation process during Windows Autopilot self-deploying mode. This error is raised by the **Windows Provisioning Agent** (a component of the Autopilot deployment stack) when it cannot validate the device's firmware integrity via TPM measurements. Specifically, the error occurs when either the TPM chip is unresponsive (e.g., due to hardware failure or driver issues) or the PCR (Platform Configuration Register) values collected after a firmware update do not match the expected measurements stored in the Autopilot attestation database. The hexadecimal code
0x80180026 breaks down as follows:
-
0x8018: Namespace for Windows Autopilot provisioning errors.
-
0026: Specific error code for TPM attestation mismatches or communication failures.
This error directly impacts the device’s ability to complete self-deploying mode, as Autopilot relies on TPM attestation to ensure the device has not been tampered with and meets firmware security requirements.
---
Affected Versions and Scope
This error is explicitly tied to **Windows 11, version 23H2** (OS build 22621.x). It affects devices enrolled in Autopilot self-deploying mode where a recent firmware update (e.g., BIOS/UEFI, TPM firmware, or security patches) has altered PCR values without updating the Autopilot attestation records.
**Not affected**:
- Devices using Autopilot **user-driven** or **pre-provisioned** deployment modes.
- Windows 10 devices (21H2 or later) unless explicitly configured with TPM-based attestation policies.
- Devices where firmware updates are applied without changing PCR values (e.g., non-security-related updates).
The issue is most prevalent in environments with strict firmware update policies or devices managed via Intune with automatic firmware updates enabled.
---
Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are:
1. **Log file**:
%windir%\System32\winevt\Logs\AppxDeployment-*.etl
- Search for the exact line:
0x80180026 TPM Attestation Failure
2. **Log file**:
%windir%\Panther\setupact.log
- Look for entries containing
TPM attestation failed or
PCR values mismatch.
3. **Registry key**:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Autopilot
- Check for keys like
AttestationStatus or
TPMMeasurementHash to validate stored values.
**Event IDs**:
- **Event ID 1000** in the **Application** log: General Autopilot deployment failure.
- **Event ID 41038** in the **System** log: TPM-related communication errors (e.g., "The TPM chip is not responding").
Use the command
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to extract relevant logs programmatically.
---
Root Causes
1. Firmware Update Altered PCR Values
A recent firmware update (e.g., BIOS, TPM, or security patches) modified PCR values, but the Autopilot attestation database was not updated. This is common after updates that change secure boot policies or kernel integrity checks. To confirm, compare PCR values in
setupact.log with those stored in the registry under
HKEY_LOCAL_MACHINE\...\Autopilot.
2. TPM Communication Failure
The TPM chip is physically damaged, disabled in firmware, or its driver is malfunctioning. Check the **Device Manager** for TPM-related errors (e.g., "TPM 2.0 Security Device" with a yellow exclamation mark). Use
dsregcmd /status to verify TPM readiness.
3. Corrupted Autopilot Attestation Data
The registry key
HKEY_LOCAL_MACHINE\...\Autopilot contains invalid or outdated attestation data. This can occur if the device was reimaged without resetting Autopilot settings or if manual registry edits were performed.
---
Fix Procedure
- **Roll Back Firmware Updates**:
- Use
Get-WindowsUpdateLog to identify the problematic update.
- Revert via wusa.exe /uninstall /kb:XXXXXX or the device’s firmware recovery tool.
- **Reset TPM Attestation Data**:
Warning: This step may break existing Autopilot enrollment. Ensure the device is re-enrolled in Intune.
- Delete the registry key HKEY_LOCAL_MACHINE\...\Autopilot.
- Reboot and trigger Autopilot re-enrollment with Invoke-WindowsAutopilotPreProvisioning.
- **Enforce TPM Policy via OMA-URI**:
- In Intune, navigate to Devices > Windows > Windows enrollment.
- Configure the OMA-URI
./Device/Vendor/MSFT/TPM/GlobalPolicy/Enable with value 1.
- **Validate Fix with PowerShell**:
Get-AutopilotDevice | Where-Object serialNumber -eq $serial
dsregcmd /status | Select-String "TPM"
---
Error Code Variants
| Error Code |
Description |
Distinguishing Factor |
0x80180026 |
TPM attestation mismatch |
PCR values do not match expected measurements |
0x80180025 |
TPM not enabled or activated |
TPM chip is disabled in firmware or not initialized |
0x80180027 |
Network attestation failure |
Autopilot cannot reach Microsoft attestation endpoints |
---
Verification
After applying fixes, verify success by:
1. Checking
setupact.log for absence of
0x80180026.
2. Running
dsregcmd /status and confirming
TPMAttestation is
Success.
3. In the Intune admin center (
Devices > All devices), ensuring the device shows a healthy enrollment status.
---
Prevention
To prevent recurrence:
- **Policy Change**: Enforce firmware update approvals in Intune (
Devices > Windows > Update rings) to test PCR impact before deployment.
- **Baseline Configuration**: Use the registry key
HKEY_LOCAL_MACHINE\...\Autopilot to lock down attestation values after firmware updates.
-
Tip: Use Get-WinEvent with a scheduled task to monitor for 0x80180026 and trigger alerts.