Home › Windows Autopilot › 0x803C010B

Windows Autopilot · 0x803C010B · Windows 11 23H2

Windows Autopilot Error 0x803C010B - Windows 11 23H2 Deployment Failure

The error occurs when the device's hardware hash isn't registered in Azure AD or Intune. Ensure the device is enrolled and assigned to the correct profile.

Error Details

FactValueSourceNote
Exact error stringDeployment 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 rangeWindows 11 23H2System Information tool or command line (winver)-> Confirms the affected OS version.
Registry key involvedHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\AutopilotRegistry Editor (regedit.exe)-> Contains device hardware hash used for Autopilot enrollment.
Relevant service/endpoint URLhttps://portal.azure.com/#blade/Microsoft_AAD_DeviceManagement blade/DevicesMenuBlade/deviceDetails/Azure Portal-> Verify device registration and profile assignment in Azure AD.
Log line signatureAutopilot: Error 0x803C010B - Deployment profile not found.Windows Setup log file (setupact.log)-> Identifies the specific error in deployment logs.

Log Files to Check

What This Error Actually Means

The error code 0x803C010B 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 to Windows 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 is C:\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 via Get-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 to Intune admin center > Devices > Windows > Autopilot > Profiles and cross-checking the target group.

3. Registry Misconfiguration

The DeploymentProfile 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

  1. Verify the device's hardware hash in Azure: Get-AutopilotDevice | Where-Object serialNumber -eq $serial. If missing, import it using Import-AutopilotDevice -CsvFilePath "C:\AutopilotDevices.csv".
  2. 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.
  3. Correct the registry if necessary: Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\Autopilot" -Name "DeploymentProfile" -Value "ProfileName".
  4. Use OMA-URI to enforce profile assignment: ./Device/Vendor/MSFT/WindowsAutopilot/DeploymentProfile/ProfileName.
  5. 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 CodeDescriptionDistinguishing Factor
0x803C010AProfile mismatch due to incorrect device groupLog line includes "Group mismatch"
0x803C010CProfile not assigned to deviceLog line includes "Profile assignment missing"
0x803C010BDeployment profile not foundLog line includes "hardware hash not registered"

Verification

After applying fixes, check C:\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 using Get-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.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.