Error Details
| Fact | Value | Source | Note |
|---|
| Exact error code | 0x801C0033 | Autopilot deployment logs | Indicates device identity resolution failure |
| Affected OS build | Windows 11 22H2 (19045.x) | Windows Update release notes | Also observed in 23H2 pre-release builds |
| Registry key | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot\DeviceId | Windows Registry | Stores Autopilot device identifier |
| AAD Join endpoint | https://aadjoin.microsoft.com | Azure AD Join service | Fails to resolve device object |
| Log signature | Device not found in on-premises AD or sync not completed | Setupact.log | Correlate with error timestamp |
Log Files to Check
C:\Windows\Logs\Autopilot\AutopilotDiag.logC:\Windows\Logs\Setup\Setupact.log
What This Error Actually Means
The error code
0x801C0033 is a hexadecimal representation of a Windows Autopilot-specific failure during Hybrid Azure AD (Azure AD) join. This error is raised by the **Azure AD Join service** (
aadjoin.microsoft.com), which acts as a bridge between on-premises Active Directory (AD) and Azure AD. The error indicates that the device attempting to join Azure AD could not be validated against the on-premises AD directory, or the synchronization process between on-premises AD and Azure AD has not completed. The root cause is typically a mismatch between the device's identity in the registry (
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot\DeviceId) and the synchronized state in Azure AD. This error is distinct from general AAD join failures and specifically points to directory synchronization or identity resolution issues.
Affected Versions and Scope
This error affects **Windows 11 22H2 (OS build 19045.x)** deployments using **Hybrid Azure AD join** with on-premises AD and Azure AD Connect. It is not observed in **cloud-only Azure AD join** scenarios or in older OS builds like Windows 10 21H2. The issue is most common in environments where devices are enrolled in Autopilot but their on-premises AD records are either missing, outdated, or not yet synchronized with Azure AD. Tenants using **Azure AD Device Writeback** or **Azure AD Hybrid Join (Legacy)** are particularly vulnerable. The error does not occur in pure cloud-based enrollment workflows (e.g., using a Microsoft account or cloud-only Azure AD join).
Where To Look First: Logs and Event IDs
The primary logs to analyze are:
-
C:\Windows\Logs\Autopilot\AutopilotDiag.log: Look for lines containing
"Device not found in on-premises AD or sync not completed".
-
C:\Windows\Logs\Setup\Setupact.log: Search for
"AAD join failed with error 0x801C0033".
- Windows Event Viewer: Check the **Setup** log for Event ID
1001 and the **Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin** log for Event ID
1100.
Use PowerShell to extract relevant logs:
Get-WinEvent -LogName "Setup" | Where-Object { $_.Message -match "0x801C0033" }
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50
Root Causes
1. Device Not Found in On-Premises AD
The device's identity (derived from
DeviceId in the registry) does not exist in the on-premises AD. Verify using:
Get-ADComputer -Filter { Name -eq (Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot\DeviceId).DeviceId }
2. Azure AD Sync Not Completed
Azure AD Connect has not synchronized the device object from on-premises AD to Azure AD. Check sync status with:
Get-AzureADDevice -SearchString "DeviceName"
3. Incorrect DeviceId in Registry
The
DeviceId registry key may be corrupted or manually modified. Validate against the physical device's serial number or hardware hash.
4. AAD Join Endpoint Throttling
The
aadjoin.microsoft.com endpoint may be rate-limited. Test connectivity with:
Test-NetConnection aadjoin.microsoft.com -Port 443
Fix Procedure
- **Verify Device in On-Premises AD**:
Get-ADComputer -Filter { Name -eq (Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot\DeviceId).DeviceId }
If missing, create the device object in AD using New-ADComputer.
- **Force Azure AD Sync**:
Start-ADSyncSyncCycle -PolicyType Delta
Confirm synchronization in Azure AD with:
Get-AzureADDevice -SearchString "DeviceName"
- **Correct Registry DeviceId** (if invalid):
Set-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot -Name DeviceId -Value "CorrectDeviceName"
Modifying the DeviceId registry key can break existing Autopilot enrollment. Always back up the registry before editing.
- **Reconfigure Hybrid Join Policy in Intune**:
Navigate to **Intune admin center > Devices > Enrollment > Windows enrollment > Hybrid Azure AD join**. Ensure the policy includes the correct device group and synchronization settings.
- **Use OMA-URI to Reset DeviceId**:
Deploy an OMA-URI configuration profile in Intune with:
./Device/Vendor/MSFT/Registry/Machine/Software/Microsoft/Windows/CurrentVersion/Autopilot/DeviceId
Set the value to the correct device name.
Error Code Variants
| Error Code | Description | Differentiator |
0x801C0033 | Device not found in on-premises AD or sync not completed | Registry DeviceId mismatch |
0x801C0032 | Azure AD join failed due to invalid credentials | Credentials mismatch in Setupact.log |
0x801C0034 | AAD join endpoint unavailable | Network/firewall issues to aadjoin.microsoft.com |
Verification
After applying fixes, verify success by:
1. Checking
AutopilotDiag.log for
"AAD join succeeded".
2. Confirming the device appears in **Entra ID > Devices > All devices** with status "Hybrid Azure AD joined".
3. Running
dsregcmd /status and ensuring
AzureADJoin is marked "True".
Prevention
To prevent recurrence:
- Enforce a **pre-enrollment validation policy** in Intune to verify device existence in on-premises AD before Autopilot deployment.
- Schedule **Azure AD Connect sync cycles** during off-peak hours to avoid delays.
- Use a **device baseline policy** in Intune to audit the
DeviceId registry key and trigger alerts for mismatches.
Use dsregcmd /status as a quick diagnostic tool to check Azure AD join status without parsing logs.