Troubleshoot Autopilot deployment issues
When troubleshooting Windows Autopilot, it's important to verify the following key factors:
- Configuration: Has Microsoft Entra ID and Microsoft Intune (or an equivalent mobile device management (MDM) service) been configured according to the Windows Autopilot requirements?
- Network connectivity: Can the device access the services described in the Windows Autopilot networking requirements?
- Autopilot OOBE behavior: Are the expected Windows out-of-box experience (OOBE) screens displayed? Is the Microsoft Entra ID sign-in page customized with the organization’s branding as expected?
- Entra ID join issues: Was the device able to successfully join Microsoft Entra ID?
- MDM enrollment issues: Was the device able to enroll in Microsoft Intune (or another configured MDM service)?
Troubleshoot Autopilot OOBE issues
If the expected Autopilot behavior doesn't occur during OOBE, it can be helpful to verify whether the device received an Autopilot deployment profile and what configuration settings were applied.
Event Tracing for Windows (ETW) can capture detailed information from Windows Autopilot and related components. These trace files can then be analyzed using tools such as Windows Performance Analyzer.
After the device receives its Autopilot profile, configuration information is stored in the device registry at HKLM\SOFTWARE\Microsoft\Provisioning\Diagnostics\Autopilot.
Windows also records events related to Autopilot profile configuration and the OOBE process. These events can be viewed in Event Viewer by navigating to: Applications and Services Logs → Microsoft → Windows → Provisioning-Diagnostics-Provider → Autopilot
Some common events include:
| Event ID | Type | Description |
|---|---|---|
| 100 | Warning | "Autopilot policy [name] not found." This error is typically a temporary problem, while the device is waiting for a Windows Autopilot profile to be downloaded. |
| 171 | Error | "AutopilotManager failed to set TPM identity confirmed. HRESULT=[error code]." This message indicates an issue performing TPM attestation, needed to complete the self-deploying mode process. |
| 172 | Error | "AutopilotManager failed to set Autopilot profile as available. HRESULT=[error code]." This error is typically related to event ID 171. |
Windows Autopilot diagnostics
Administrators can run the Autopilot diagnostics script on the device using PowerShell:
Set-ExecutionPolicy Bypass
Install-Script Get-AutopilotDiagnostics -Force
Get-AutopilotDiagnostics -Online
After signing in with an account that has appropriate permissions, the script connects to the tenant using Microsoft Graph and retrieves information about deployment status, policies, and assigned applications
Troubleshoot Microsoft Entra ID join issues
The most common issue joining a device to Entra ID is related to Entra ID permissions. Ensure the correct configuration is in place to allow users to join devices to Entra ID. Errors can also happen if the user has exceeded the number of devices that they're allowed to join, as configured in Entra ID.
Typically displayed on a "Something went wrong" error page, the error code 801C0003 signifies that the attempt to join Entra ID was unsuccessful.
Troubleshoot Intune enrollment issues
See this article for assistance with Intune enrollment issues. Common issues include incorrect or missing licenses assigned to the user or too many devices enrolled for the user.
When encountering the error code 80180018, it's accompanied by an error page titled "Something went wrong." This specific error indicates a failed MDM enrollment process.