Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | Deployment profile not found - Device hardware hash not registered in Autopilot devices list or profile assignment group does not include device. | Windows Setup log file (setupact.log) | -> Indicates the root cause of the failure. |
| OS build range | Windows 11 23H2 | System Information tool or command line (winver) | -> Confirms the affected OS version. |
| Registry key involved | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\Autopilot | Registry Editor (regedit.exe) | -> Contains device hardware hash used for Autopilot enrollment. |
| Relevant service/endpoint URL | https://portal.azure.com/#blade/Microsoft_AAD_DeviceManagement blade/DevicesMenuBlade/deviceDetails/ | Azure Portal | -> Verify device registration and profile assignment in Azure AD. |
| Log line signature | Autopilot: Error 0x803C010B - Deployment profile not found. | Windows Setup log file (setupact.log) | -> Identifies the specific error in deployment logs. |
Log Files to Check
C:\Windows\Panther\Setupact.logC:\Windows\Temp\OOBE\Oobe.xml
What This Error Actually Means
The error code0x803C010B is a hexadecimal representation of a Windows Autopilot deployment failure. Breaking it down: 0x803C corresponds to the component responsible for Autopilot deployment, specifically the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider service. The trailing 010B (hex) translates to decimal 267, which maps to a specific error condition in the Autopilot enrollment pipeline. The error message explicitly states that the deployment profile could not be found, which typically indicates one of two root causes: (1) the device's hardware hash is missing from the Azure Autopilot device list, or (2) the device's assignment group in Intune does not match the profile's target group. This error is raised during the Out-of-Box Experience (OOBE) phase when the system attempts to fetch the deployment profile from Azure. The Autopilot component in the Windows Setup process (setupact.log) logs this failure, signaling a critical block in the enrollment workflow.
Affected Versions and Scope
This error is explicitly tied toWindows 11 23H2 (OS build 22621.x or 22623.x). It occurs in tenants using Azure Autopilot with either Windows 11 23H2 devices or mixed environments where older Windows 10 devices are enrolled. The error does **not** affect Windows 10 devices unless they are upgraded to 23H2 and retain the same hardware hash. Tenants using Windows 11 22H2 (build 22000.x) may experience similar errors but with different log signatures. The scope is limited to devices where the hardware hash was not properly registered in Azure or where the profile assignment group misalignment occurs. This error is not observed in scenarios using Windows Autopilot for Business with pre-provisioned devices (e.g., via Azure AD join without Autopilot).
Where To Look First: Logs and Event IDs
The primary log to investigate isC:\Windows\Panther\Setupact.log, where the exact line Autopilot: Error 0x803C010B - Deployment profile not found. appears. Additionally, check C:\Windows\Temp\OOBE\Oobe.xml for XML fragments indicating missing profile assignments. Use the following PowerShell command to extract relevant logs:
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 | Where-Object { $_.Message -match "0x803C010B" }.
Event IDs 4100 and 4101 in the Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin log often accompany this error. For registry validation, inspect HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\Autopilot for missing or incorrect DeploymentProfile values.
Root Causes
1. Missing Hardware Hash in Azure
The device's hardware hash is not registered in the Azure Autopilot device list. Verify this by querying Azure viaGet-AutopilotDevice | Where-Object serialNumber -eq $serial. If the device is absent, use Import-AutopilotDevice -CsvFilePath "C:\AutopilotDevices.csv" to register it.
2. Profile Assignment Group Mismatch
The Autopilot profile is assigned to a dynamic group in Intune that does not include the device. Confirm this by navigating toIntune admin center > Devices > Windows > Autopilot > Profiles and cross-checking the target group.
3. Registry Misconfiguration
TheDeploymentProfile registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\Autopilot is either missing or incorrectly set. This can occur after manual registry edits or failed deployments.
Fix Procedure
- Verify the device's hardware hash in Azure:
Get-AutopilotDevice | Where-Object serialNumber -eq $serial. If missing, import it usingImport-AutopilotDevice -CsvFilePath "C:\AutopilotDevices.csv". - Update the Autopilot profile assignment group in Intune:
Navigate to
Intune admin center > Devices > Windows > Autopilot > Profiles, select the profile, and ensure the target group includes the device. - Correct the registry if necessary:
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\Autopilot" -Name "DeploymentProfile" -Value "ProfileName". - Use OMA-URI to enforce profile assignment:
./Device/Vendor/MSFT/WindowsAutopilot/DeploymentProfile/ProfileName. - Force re-enrollment using PowerShell:
Invoke-MgGraphRequest -Method POST -Uri "https://graph.microsoft.com/v1.0/deviceManagement/managedDevices/{deviceID}/reEnroll".
Modifying the
DeploymentProfile registry key on an enrolled device may trigger a re-enrollment loop. Always back up the registry before editing.Error Code Variants
| Error Code | Description | Distinguishing Factor |
|---|---|---|
0x803C010A | Profile mismatch due to incorrect device group | Log line includes "Group mismatch" |
0x803C010C | Profile not assigned to device | Log line includes "Profile assignment missing" |
0x803C010B | Deployment profile not found | Log line includes "hardware hash not registered" |
Verification
After applying fixes, checkC:\Windows\Panther\Setupact.log for the line Autopilot: Successfully applied deployment profile "ProfileName". In the Azure portal (https://portal.azure.com/#blade/Microsoft_AAD_DeviceManagementBlade/DevicesMenuBlade/deviceDetails/), confirm the device's Enrollment Status is Success and the Assigned Profile matches the expected name. Run dsregcmd /status to verify Azure AD join status and profile assignment.
Prevention
Implement a policy to automate hardware hash registration usingGet-AutopilotDevice and Import-AutopilotDevice in a scheduled script. Enforce baseline configurations in Intune to ensure all Autopilot profiles are assigned to dynamic groups based on hardware hash or serial number. Regularly audit device enrollment status with Get-MgDeviceManagementManagedDevice -Filter "deviceEnrollmentType eq 'windowsAutoEnrollment'".
Use
Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" | Select-Object -First 10 to quickly identify recent Autopilot failures without parsing large log files.