Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | TPM attestation failed during Autopilot provisioning — TPM 2.0 not responding or firmware update required | Windows Event Logs | -> |
| Affected build range | Windows 11 23H2 | Microsoft Documentation | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters | Windows Registry | -> |
| Relevant service/endpoint URL | https://aka.ms/tpmfwupdate | Microsoft Support | -> |
| Log line signature | AutopilotProvisioning-Error-TPMAttestationFailed | Autopilot Provisioning Logs | -> |
Log Files to Check
C:\Windows\Logs\Autopilot\AutopilotProvisioning.logC:\Windows\System32\winevt\Logs\Microsoft-Windows-AutopilotProvisioning%4Operational.evtx
What This Error Actually Means
The error code
0x801C001F is a hexadecimal representation of a Windows Autopilot provisioning failure tied to TPM (Trusted Platform Module) attestation. Breaking down the code:
0x801C indicates a Windows Device Management (MDM) error category, while
001F maps to a specific TPM-related failure. This error is raised by the
AutopilotProvisioning service during the device attestation phase, which validates the device's hardware integrity before enrollment. The root issue is that the TPM 2.0 chip is either unresponsive (due to power/communication issues) or requires a firmware update to meet Autopilot's security requirements. This error is distinct from generic TPM errors because it explicitly ties to Autopilot's attestation workflow, not general TPM misconfigurations.
Affected Versions and Scope
This error is confirmed to affect **Windows 11 23H2** (build 22000.2187 or later) devices enrolled via Windows Autopilot. It occurs when the device's firmware lacks the latest TPM 2.0 compatibility patches required by Microsoft's attestation service. Devices running **Windows 11 22H2** or earlier are not impacted, as they use different attestation protocols. Additionally, devices with **TPM 1.2** hardware are excluded from this error, as Autopilot 23H2 enforces TPM 2.0 as a mandatory requirement. Tenants using **Intune-managed Autopilot** with Azure AD hybrid join configurations are most likely to encounter this error, particularly in environments where firmware updates are delayed or blocked by group policies.
Where To Look First: Logs and Event IDs
The primary diagnostic artifacts are located in two log files:
C:\Windows\Logs\Autopilot\AutopilotProvisioning.log
and
C:\Windows\System32\winevt\Logs\Microsoft-Windows-AutopilotProvisioning%4Operational.evtx.
Use
findstr to search for the signature:
AutopilotProvisioning-Error-TPMAttestationFailed.
In the Event Viewer, filter for **Event ID 4101** (TPM attestation failure) and **Event ID 4102** (firmware update required). The registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters may also show misconfigurations if the
DisableTpmAttestation value is set to 1. To inspect logs programmatically, use:
Get-WinEvent -LogName "Microsoft-Windows-AutopilotProvisioning/Operational" | Where-Object { $_.Message -match "0x801C001F" }.
Root Causes
1. Outdated TPM Firmware
The most common cause is a firmware version incompatible with 23H2's attestation requirements. Check the device manufacturer's firmware update portal (e.g., Dell, HP, Lenovo) for TPM-specific patches. Use
tpm.msc to verify the TPM firmware version.
2. Registry Misconfiguration
A non-default value in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters\DisableTpmAttestation can block attestation. This key is unrelated to networking but is mistakenly modified in some custom scripts.
3. BIOS/UEFI TPM Disable
If TPM is disabled in firmware settings, the chip will not respond. Use
msinfo32 to check the "Trusted Platform Module (TPM)" status. If it shows "Not Activated," reboot into BIOS and enable TPM 2.0.
4. Communication Failure with TPM Service
The
TPM Base Services (TPMBS) might be stopped or misconfigured. Use
Get-Service TPM to verify the service state. A
Stopped status indicates a deeper system integrity issue.
Fix Procedure
- **Apply Firmware Update via Microsoft Endpoint Manager**
Use the
https://aka.ms/tpmfwupdate endpoint to fetch the latest firmware. Deploy it via Intune using a Windows Update for Business policy:
Intune admin center > Devices > Windows > Windows Update > Deployment Settings.
- **Correct Registry Key**
If
DisableTpmAttestation is set to 1, reset it:
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters" -Name "DisableTpmAttestation" -Value 0.
Modifying this key on enrolled devices can trigger re-enrollment. Test in a lab first.
- **Enable TPM in BIOS**
Use a PowerShell script to reboot the device into UEFI settings:
Restart-Computer -Force -Uefi. Navigate to Security > TPM and enable it.
- **Verify TPM Service**
Ensure the TPM service is running:
Start-Service TPM and set startup type:
Set-Service -Name TPM -StartupType Automatic.
- **Re-trigger Autopilot**
Use OMA-URI to force re-provisioning:
./Device/Vendor/MSFT/Provisioning/ReEnroll with value 1. Deploy via Intune:
Intune admin center > Devices > Configuration profiles > Create profile > Custom > OMA-URI.
Error Code Variants
| Error Code | Description | Distinguishing Factor |
0x801C001F | TPM attestation failure | TPM 2.0 firmware mismatch |
0x801C0020 | TPM attestation timeout | Service communication delay |
0x801C001E | TPM attestation policy mismatch | Conditional Access policy conflict |
Verification
After applying fixes, check
AutopilotProvisioning.log for the line:
TPM attestation succeeded with firmware version X.X.X.
In Intune, verify the device status under
Intune admin center > Devices > All devices > Windows > [Device] > Device details. The
Enrollment status should show "Succeeded." Use
dsregcmd /status to confirm
TPMAttestation is
Enabled.
Prevention
To prevent recurrence, create a **device compliance policy** in Intune that enforces TPM firmware updates:
Intune admin center > Compliance > Device compliance > Create policy > Windows 10/11 > TPM. Set
Minimum firmware version to match Microsoft's latest recommendation. Additionally, deploy a **baseline profile** to lock the
DisableTpmAttestation registry key:
Intune admin center > Devices > Configuration profiles > Create profile > Baseline > Windows 10/11.
Use Get-AutopilotDevice | Where-Object { $_.errorDescription -match "0x801C001F" } to bulk-identify affected devices.