Home › Windows Autopilot › 0x801C03F3

Windows Autopilot · 0x801C03F3 · Windows 11 22H2

Windows Autopilot Error 0x801C03F3 on Windows 11 22H2: Device Not Found

Device not found in Autopilot due to pending hardware hash import or group assignment mismatch. Verify hash import status and device group assignments in Intune.

Error Details

FactValueSourceNote
Exact error code0x801C03F3AutopilotSetup.logWindows 11 22H2 specific
Affected OS buildWindows 11 22H2 (22621.x)System PropertiesAll versions
Registry keyHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AutopilotRegistry EditorCheck HashImportStatus
Service endpointhttps://autopilot.microsoft.comIntune PortalDevice registration endpoint
Log signatureDevice not found in Autopilot serviceAutopilotSetup.logCorrelate with hash ID

Log Files to Check

What This Error Actually Means

The error code 0x801C03F3 is a hexadecimal representation of a Windows Autopilot enrollment failure. Breaking it down, the prefix 0x801C indicates a Microsoft-specific error category, while 03F3 maps to a specific failure within the Autopilot service. This error is raised by the **Autopilot setup component** during device enrollment, specifically when the device's hardware hash or serial number cannot be matched to an entry in the Autopilot service. The log line Device not found in Autopilot service in C:\Windows\Logs\Autopilot\AutopilotSetup.log confirms this mismatch. The root issue is either a missing hardware hash in the Autopilot tenant database or an incorrect device group assignment in Intune, preventing the device from being recognized for provisioning. ---

Affected Versions and Scope

This error is specific to **Windows 11 22H2 (OS build 22621.x)** and occurs when devices are enrolled in tenants where hardware hashes were not pre-imported or device group assignments are misconfigured. It affects environments using **Windows Autopilot with self-deploying or user-driven enrollment** but does **not** occur in **Azure AD hybrid join scenarios** or when using **Windows AutoPilot with Azure AD hybrid Azure AD joined devices**. The issue is also observed in tenants where the https://autopilot.microsoft.com endpoint is blocked or misconfigured in proxy/firewall rules. It does **not** affect Windows 10 21H2 or later builds of Windows 11 (e.g., 23H2) due to improvements in hardware hash validation workflows. ---

Where To Look First: Logs and Event IDs

The primary diagnostic artifact is C:\Windows\Logs\Autopilot\AutopilotSetup.log. Use Findstr "Device not found" C:\Windows\Logs\Autopilot\AutopilotSetup.log to locate the exact failure line. Cross-reference with C:\Windows\Logs\SetupDiag\SetupDiag.log for hardware inventory discrepancies. Key Event IDs to monitor in the **Event Viewer** under Applications and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin: - 10000: "Autopilot device not found in tenant database." - 10001: "Autopilot group assignment mismatch detected." Use Get-WinEvent -LogName "Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider/Admin" -MaxEvents 50 to automate retrieval of these events. ---

Root Causes

1. Missing Hardware Hash in Autopilot Tenant

If the device's hardware hash was not imported via the Import-AutopilotDevice cmdlet or Intune portal, the Autopilot service cannot identify the device. Verify by checking HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot for the HardwareHash value. An empty or missing key confirms this root cause.

2. Incorrect Device Group Assignment

The device may be assigned to a non-existent or misconfigured Autopilot group in Intune. Navigate to **Intune admin center > Devices > Windows > Autopilot > All devices** to verify group membership. If the device is listed under "Pending" or "No group," this is the cause.

3. Tenant Configuration Mismatch

A mismatch between the device's Azure AD tenant and the Autopilot tenant (e.g., due to multi-tenant scenarios or incorrect domain registration) can trigger this error. Validate tenant alignment using dsregcmd /status and cross-check the RegisteredOwner field in the registry. ---

Fix Procedure

  1. **Re-import Hardware Hash**: Import-AutopilotDevice -CsvFilePath "C:\AutopilotDevices.csv" with the device's serial number and hardware hash. Ensure the CSV includes SerialNumber,HardwareHash,GroupTag columns.
  2. **Assign Device to Correct Group**: In **Intune admin center > Devices > Windows > Autopilot > All devices**, select the device, and assign it to a valid group. Use Set-AutopilotDevice -DeviceId "device-serial" -GroupTag "Engineering-Group" via PowerShell.
  3. **Verify Registry Configuration**: Ensure HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot contains valid HardwareHash and GroupTag values. Use reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Autopilot to validate.
  4. **OMA-URI Policy for Group Assignment**: Deploy a configuration profile with OMA-URI ./Device/Vendor/MSFT/WindowsAutopilot/GroupTag and value "Engineering-Group" via **Intune admin center > Devices > Configuration profiles > Create profile**.
  5. Modifying the HardwareHash registry key on an enrolled device may force re-enrollment, causing data loss. Always back up the registry before editing.
---

Error Code Variants

Error CodeDescriptionDistinguishing Factor
0x801C03F3Device not found in AutopilotHardware hash/group mismatch
0x801C03F4Autopilot service unavailableTransient network or endpoint issue
0x801C03F2Invalid device licenseWindows 10/11 license mismatch
---

Verification

After applying fixes, check AutopilotSetup.log for the line Autopilot device successfully enrolled. In the **Intune admin center > Devices > Windows > Autopilot**, the device should transition from "Pending" to "Assigned." Run Get-AutopilotDevice | Where-Object serialNumber -eq "device-serial" to confirm the device is listed with the correct group tag.
Use dsregcmd /status to instantly verify Autopilot enrollment status without parsing logs. Look for AutopilotGroupTag in the output.
---

Prevention

Implement a **device baseline policy** in Intune to enforce hardware hash validation at enrollment. Use Get-MgDeviceManagementDeviceCompliancePolicy to create a policy requiring HardwareHash presence. Automate hash imports via a scheduled task running Import-AutopilotDevice on CSV updates. Monitor **Intune admin center > Reports > Device compliance** to catch misconfigurations early.

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.