Error Details
| Fact | Value | Source |
|---|---|---|
| Exact error string | Something went wrong. Error code: 80180001 | Autopilot OOBE screen |
| Error code in event log | Event ID 115 (Autopilot CSP failed) | C:\Windows\System32\winevt\Logs\Microsoft-Windows-Provisioning-Diagnostics-Provider%4Admin.evtx |
| Registry key for TPM provisioning status | HKLM\SYSTEM\CurrentControlSet\Services\TPM\Parameters\DeviceIdentifier | Registry Editor |
| TPM service start value | 3 (Manual) | HKLM\SYSTEM\CurrentControlSet\Services\Tpm Start |
| PowerShell TPM check | Get-Tpm TpmPresent, TpmReady, TpmActivated, TpmOwned, ManagedAuthLevel | Windows PowerShell |
Log Files to Check
C:\Windows\System32\winevt\Logs\Microsoft-Windows-Provisioning-Diagnostics-Provider%4Admin.evtxC:\Users\administrator\AppData\Local\Temp\MdmDiagnostics
What This Error Actually Means
The error code 0x80180001, which translates to TPM_E_AUTHFAIL (Authorization Failure), is raised by the Trusted Platform Module (TPM) during the Windows Autopilot enrollment process when it cannot complete the attestation handshake with Microsoft's Intune service. This failure typically occurs due to issues related to the TPM’s previous ownership or configuration state, preventing it from authenticating correctly with Azure AD and Intune.Affected Versions and Scope
This error is commonly encountered in Windows 10 and Windows 11 devices enrolled via Autopilot. It affects both new device enrollments and re-enrollments of previously managed devices. The issue does not appear on systems running older versions of Windows that do not support TPM-based attestation or where the Autopilot feature has been disabled.Where To Look First: Logs and Event IDs
To diagnose this error, start by examining the following logs and event IDs:C:\Windows\System32\winevt\Logs\Microsoft-Windows-Provisioning-Diagnostics-Provider%4Admin.evtxEvent ID 115 (Autopilot CSP failed)inApplications and Services Logs > Microsoft > Windows > Provisioning-Diagnostics-Provider > AdminC:\Users\administrator\AppData\Local\Temp\MdmDiagnosticsfolder after runningMdmDiagnosticsTool.exe -area Autopilot;TPM -cab c:\temp\diag.cabHKLM\SYSTEM\CurrentControlSet\Services\TPM\Parameters\DeviceIdentifierHKLM\SYSTEM\CurrentControlSet\Services\Tpm Start value (must be 3 for Manual)
Root Causes
There are several root causes that can lead to this error:TPM Ownership Not Cleared
If a device has been previously enrolled and its TPM ownership was not cleared, the current enrollment attempt will fail with 0x80180001. This is because the existing TPM owner authorization value prevents the new attestation handshake from completing successfully.TPM Firmware Outdated
Outdated TPM firmware can cause failures during the attestation process, especially in devices using Intel Platform Trust Technology (PTT) or fTPM implementations. These issues are often resolved by updating the BIOS to a version that includes updated TPM firmware.NV Storage Full on TPM
If the Non-Volatile (NV) storage within the TPM is full due to previous failed provisioning attempts, it can prevent new enrollments from completing successfully. This issue requires clearing the TPM or freeing up NV space through system re-provisioning steps.Fix Procedure
To resolve this error, follow these steps:Clear TPM Ownership: Open an elevated PowerShell session and run
Clear-Tpm -Force. This command will clear the TPM ownership but may require a reboot.Check TPM Service Status: Ensure that the TPM service is set to start automatically. Use the following commands in an elevated PowerShell window:
Verify the status withSet-Service -Name Tpm -StartupType Manual Start-Service -Name TpmGet-Service -Name Tpm.Update TPM Firmware: Check for BIOS updates from your device manufacturer's support site. Apply any available firmware updates that include TPM improvements.
Clear Autopilot State in Intune: Navigate to the Intune admin center > Devices > Windows Autopilot > Devices and remove or re-register the problematic devices.
Error Code Variants
| Error Code | Description | Distinguishing Factors |
|---|---|---|
| 0x80180001 | TPM_E_AUTHFAIL (Authorization Failure) | Fails during attestation phase; TPM ownership issues. |
| 0x80180024 | TPM_E_DISABLED | TPM is disabled in BIOS or system configuration. |
| 0x80180036 | TPM_E_NO_ENDORSEMENT | Lack of endorsement key setup; TPM not initialized properly. |
Verification
After applying the fixes, verify that the issue has been resolved by:Checking
HKLM\SYSTEM\CurrentControlSet\Services\TPM\Parameters\DeviceIdentifierto ensure it reflects a new TPM state.Running
Get-Tpm | Select-Object TpmPresent, TpmReady, TpmActivated, TpmOwned, ManagedAuthLevelin PowerShell to confirm TPM readiness and authorization levels.Reviewing the Intune admin center > Devices > Windows Autopilot > Devices for successful enrollment status of affected devices.
Prevention
To prevent this error from recurring, implement the following measures:Create a baseline configuration that includes TPM firmware updates and ensures TPM service is set to Manual start type.
Implement an OMA-URI policy
.Device.Vendor.MSFT.TpmConfigurationin Intune to enforce TPM settings across all devices.Regularly review device enrollment logs and clear TPM ownership for devices that are re-enrolled or have undergone significant configuration changes.
dsregcmd /status in an elevated command prompt. This command provides a summary of the device's Azure AD enrollment status and can help identify TPM-related issues at a glance.