Share via

Windows Autopilot deployment failing with immediate error code 0x80070032 during profile download

John Doe 20 Reputation points
2026-06-11T11:34:24.3733333+00:00

Hi,

we are provisioning a batch of desktop stations via Windows Autopilot. The workstations boot to the OOBE welcome screen, connect to the local office network via Ethernet, but when clicking advance, they throw an immediate error code 0x80070032, stating the request configuration profile is unsupported.

Thanks

John,

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 23,805 Reputation points Independent Advisor
    2026-06-11T12:28:31.2333333+00:00

    Hi John,

    That error shows up because the computer is trying to download a setup profile during the first Windows screen, but the profile assigned in Intune doesn’t match what the system supports. In simple terms, the device is registered in Autopilot, but the profile is either the wrong type or outdated, so Windows refuses to apply it.

    To fix it, you need to check in Intune that each device has the right profile assigned (for example, “user‑driven” or “self‑deploying” depending on how you want them set up), remove any duplicate or old records, and make sure the computer has full internet access during setup. Once the profile is corrected and synced, restarting the device should let the installation continue without the error.

    Domic V.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-11T11:34:38.8233333+00:00

    Error 0x80070032 with a message that the requested configuration profile is unsupported indicates a failure very early in the Autopilot flow, while the device is attempting to retrieve or process its Autopilot profile during OOBE.

    Use the following checks and steps, in order:

    1. Confirm Autopilot profile assignment
    • Verify that the device’s hardware hash/Autopilot record is present in the tenant and that it is assigned to a valid Windows Autopilot deployment profile.
    • Make sure the profile hasn’t been deleted or unassigned. If a previously assigned profile was removed, reassign a valid profile and retry enrollment.
    • If the device shows as registered but with no profile, assign one and reboot the device so it can download the profile again.
    1. Check for “no profile” or registration errors in Autopilot logs On the failing device during OOBE:
    • Press Shift+F10 to open a command prompt.
    • Run eventvwr.msc and navigate to Applications and Services Logs → Microsoft → Windows → Provisioning-Diagnostics-Provider → Autopilot.
    • Look for errors such as:
      • Event ID 807 – ZtdDeviceIsNotRegistered: The device’s hardware hash isn’t properly uploaded or associated with the tenant.
      • Event ID 809 – ZtdDeviceHasNoAssignedProfile – Assigned profile does not exist.: The profile that was assigned was deleted.
      • Event ID 815 – ZtdDeviceHasNoAssignedProfile – No profile assigned to the device, and no default profile found in the tenant.
    • If any of these appear, correct the corresponding condition in Intune/Autopilot (upload or reupload the device, assign a valid profile, or configure a default profile) and then reset/retry the device.
    1. Validate that the profile is actually being downloaded In the same Autopilot event log, confirm that the normal profile-download sequence occurs:
    • Event ID 160 – AutopilotRetrieveSettings beginning acquisition.
    • Event ID 164 – AutopilotManager determined Internet is available to attempt policy download.
    • Event ID 161 – AutopilotManager retrieve settings succeeded.
    • Event ID 153 – state changed from ProfileState_Unknown to ProfileState_Available. If these events are missing and instead only errors appear, the device is not successfully retrieving a usable profile.
    1. Verify tenant match and profile state in the registry Still from Shift+F10:
    • Run regedit and browse to HKLM\SOFTWARE\Microsoft\Provisioning\Diagnostics\Autopilot.
    • Check these values:
      • CloudAssignedTenantDomain / CloudAssignedTenantId: Confirm they match the tenant where the device is registered.
      • IsAutopilotDisabled: If set to 1, the device is effectively not registered or the profile couldn’t be downloaded (network/firewall/timeouts). Ensure registration and connectivity, then reset and retry.
      • TenantMatched: Should be 1 when the user’s tenant matches the device’s registered tenant; 0 indicates a mismatch that will cause errors. If tenant IDs or domains don’t match, correct the registration in Autopilot (re-register the device in the correct tenant) and then reset the device.
    1. Confirm network and Autopilot service reachability
    • Ensure the device has full internet access from OOBE (no captive portal, no proxy that blocks Autopilot/Entra/Intune endpoints, and no restrictive firewall).
    • If network issues are suspected, fix them, then reboot from OOBE using shutdown.exe /r /t 0 so the device can attempt to download the profile again.
    1. If pre-provisioning is used, capture diagnostics and retry/reset If using pre-provisioning (technician flow):
    • When the error screen appears, export diagnostics (Windows 10: View diagnostics; Windows 11: CTRL+SHIFT+D → Export Logs).
    • If the issue is something transient like network, fix it and select Retry.
    • If the issue requires changing Autopilot registration or profile assignment, select Reset so the device restarts the Autopilot process after the changes.

    If, after confirming registration, profile assignment, tenant match, and network connectivity, the Autopilot event log still shows profile-related errors (807/809/815 or similar) for these devices, re-registering the devices’ hardware hashes and assigning a fresh Autopilot profile, then resetting the devices, is typically required.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.