autopilot error 80070002 something went wrong during enrollment

TL;DR

Error 80070002 means the Autopilot service cannot find what it needs, almost always because the device is not registered in Autopilot or has no deployment profile assigned. In Intune, confirm the device's hardware hash is imported and a profile is assigned, delete any stale duplicate record, then reset the device and let it enroll again.

The error

Something went wrong
Error: 80070002

Steps

1. In Intune admin center, go to Devices > Windows > Windows Autopilot deployments > Devices and search for the device serial number. Expected: exactly one record. Zero records means it was never imported; two means a stale duplicate.
2. If missing: import it. Get the hardware hash with Get-WindowsAutoPilotInfo on the device (or from the vendor) and import the CSV in the same Autopilot devices blade. Expected: the device appears within a few minutes.
3. Check profile assignment: the device's Autopilot profile status should show Assigned. Expected: a profile name is listed. No profile, no enrollment; the device fails with 80070002 at the setup screen.
4. If a duplicate record exists: delete the stale one (usually the older record with no recent activity). Expected: one record remains. Duplicates make the service return the wrong record, which reads as file not found.
5. Reset the device (Settings > Recovery, or remote wipe from Intune) and let it go through OOBE again. Expected: the Autopilot profile applies and enrollment completes. Do not skip the reset; the failed state is cached on the device.

Use this when

• Autopilot fails at enrollment with error 80070002
• A new device from the vendor will not pick up its Autopilot profile
• The device was previously enrolled, wiped, and now fails

Not for this skill when

• The error code is different (each Autopilot code has its own cause)
• The device enrolls but fails Intune compliance later (policy issue)
• The device never reaches the network during OOBE (connectivity first)

Compatibility

• Windows 10/11 with Autopilot; Intune admin center

Variants

Vendor says the hash was uploaded but Intune shows nothing

The vendor uploaded to the wrong tenant. Confirm the tenant ID on the upload; cross-tenant hashes are a classic mix-up with resellers.

Profile assigned but the device still fails

Wait 15 minutes after assignment. Profile assignment propagates on a delay, and enrolling too fast hits the same 80070002.

Why it happens

During OOBE the device asks the Autopilot service for its deployment profile. If the device identity is not registered, or no profile points at it, the service has nothing to return, and the client surfaces that as the generic file-not-found error.

Edge cases

• Devices registered with a personal Microsoft account first can get stuck in a consumer enrollment path. Wipe and make sure OOBE starts clean.
• 80070002 can also appear when required apps in the Enrollment Status Page fail to download. If the profile is fine, check the app list on that page.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_yqppDoZ8i66qFxXb47gTXA