Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Device registration quota exceeded — tenant Autopilot device limit reached or duplicate hardware hash in tenant | WindowsAutopilot.diagcab log file | -> |
| OS build range affected | Windows 11 23H2 and later | Microsoft Learn documentation | -> |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost\AutoPilotState | Registry Editor (regedit) | -> |
| Relevant service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_DeviceManagementBlade/DevicesMenu | Azure Active Directory admin center | -> |
| Log line signature | [Autopilot] Device registration failed with error code 0x801C02F2. | WindowsAutopilot.diagcab log file | -> |
Log Files to Check
C:\Windows\System32\winevt\Logs\WindowsAutopilot.diagcabC:\ProgramData\Microsoft\IntuneManagementExtension\LogFiles\IntuneManagementExtension.log
What This Error Actually Means
The error code0x801C02F2 is a hexadecimal representation of a Windows Autopilot registration failure. Breaking it down: 0x801C corresponds to the Microsoft Windows Error Facility, while 02F2 (decimal 754) maps to a specific error within the Device Management subsystem. This error is raised by the **CloudExperienceHost** component during the Autopilot device registration process. The error string "Device registration quota exceeded — tenant Autopilot device limit reached or duplicate hardware hash in tenant" confirms the root issue: either the tenant's licensed Autopilot device limit has been exhausted, or the device's hardware hash already exists in the tenant's directory. This prevents the device from being enrolled into Autopilot, blocking out-of-box experience (OOBE) customization.
Affected Versions and Scope
This error affects **Windows 11 23H2 and later builds** (including 24H2) where Autopilot is configured. It is not observed in Windows 10 or earlier Windows 11 builds (e.g., 22H2) due to differences in the Autopilot registration workflow. The issue is specific to tenants using **Microsoft 365 Business Premium**, **Microsoft 365 E3/E5**, or **Windows 10/11 Enterprise E3/E5** licenses that enforce device quotas. Tenants with unlimited Autopilot licenses (e.g., through volume licensing agreements) are unaffected. Additionally, the error occurs only when the device's hardware hash is already registered in the tenant or when the tenant's license limit is reached.Where To Look First: Logs and Event IDs
The primary log to analyze isC:\Windows\System32\winevt\Logs\WindowsAutopilot.diagcab, which contains structured diagnostic data. Use the Get-WinEvent cmdlet to extract relevant entries:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50
Look for the exact log line: [Autopilot] Device registration failed with error code 0x801C02F2.
Secondary logs include C:\ProgramData\Microsoft\IntuneManagementExtension\LogFiles\IntuneManagementExtension.log, which may show enrollment failures tied to Autopilot. Event IDs to correlate are:
- 1001: Autopilot registration initiated.
- 1009: Device registration quota exceeded or duplicate hardware hash detected.
Root Causes
1. Tenant Autopilot Device Limit Reached
Licensing restrictions cap the number of Autopilot-registered devices. Check the tenant's license count via the Azure portal. Use PowerShell to list enrolled devices:Get-AutopilotDevice | Select-Object deviceName, serialNumber, lastContactedDateTime
If the count matches the licensed limit, new devices will fail with 0x801C02F2.
2. Duplicate Hardware Hash in Tenant
A hardware hash collision occurs when a device's hash is already registered. This can happen if a device is reimaged and re-enrolled without removing the old entry. Validate duplicates by querying the registry:Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost\AutoPilotState" | Select-Object HardwareHash
Compare this hash with existing Autopilot devices using:
Get-AutopilotDevice | Where-Object hardwareHash -eq $hash
3. Corrupted AutopilotState Registry Key
Rarely, theAutoPilotState registry key may become corrupted, causing false duplicate claims. This is identifiable if the hardware hash in the registry does not match the device's actual hash.
Fix Procedure
- Delete duplicate Autopilot entries in the registry:
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudExperienceHost\AutoPilotState" -Name "HardwareHash" - Remove the conflicting device from Autopilot via PowerShell:
Remove-AutopilotDevice -DeviceId $deviceId - Free up license slots by retiring old devices in the Azure portal:
- Navigate to
https://portal.azure.com/#blade/Microsoft_AAD_DeviceManagementBlade/DevicesMenu - Select Devices > All devices, filter by
DeviceEnrollmentType eq 'windowsAutoEnrollment', and delete inactive devices.
- Navigate to
- Re-enroll the device by triggering a new Autopilot profile deployment using an OMA-URI:
./Device/Vendor/MSFT/DeviceManagement/Enrollment/ForceEnrollment
Deleting the
HardwareHash registry key will reset the device's Autopilot state. Avoid this on already enrolled devices to prevent re-enrollment loops.Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x801C02F2 | Quota exceeded or duplicate hash | Logs show "Device registration quota exceeded" |
0x800B0109 | Certificate validation failure | Occurs during Intune enrollment, not Autopilot |
0x801C02F1 | Autopilot profile not assigned | Device lacks a valid Autopilot profile in Intune |
Verification
After resolving the issue, verify success by checking theWindowsAutopilot.diagcab log for:
[Autopilot] Device registration succeeded with status 0x0
Confirm in the Azure portal that the device appears under Intune admin center > Devices > Windows > All devices with an enrollment status of "Enrolled". Use dsregcmd /status to ensure the device is Azure AD joined and Autopilot-aware.
Prevention
To prevent recurrence: 1. Monitor license usage with:Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'"
2. Implement a PowerShell script to audit duplicate hardware hashes monthly:
Get-AutopilotDevice | Group-Object hardwareHash | Where-Object Count -gt 1
3. Enforce a device retirement policy in Intune to automatically remove inactive devices after 90 days.
Use
Get-WinEvent with a filter for ProviderName -eq "CloudExperienceHost" to proactively detect Autopilot issues before user complaints arise.