autopilot 80070002 error during device setup

Not specified by the original author.

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

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

Thread query: 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.

Fixes Windows Autopilot failing during device setup with error 80070002, the system cannot find the file specified. Use when ESP device setup fails early and a required app, script, or profile file is missing. Not for network blocked enrollment or TPM attestation failures.

On the failed device, open the Autopilot diagnostics from the ESP failure screen and note the exact app or script listed as failed.

In the Intune admin center, open that app or script and check its install command and source file name match exactly, including the file extension.

If the item is a PowerShell script, check it does not call a second file that was never uploaded with it.

Check the assignment targets the device group the test device is in, and that no required app was deleted or replaced after the profile was built.

Fix the package, wait for the new version to show as available, then reset one test device and run provisioning again.

Resolved from the public problem: https://vectle.com/posts/pst_Oe0LMxauSmU8k1ZhqIYVhA

Problem query: autopilot 80070002 error during device setup

TL;DR:

Not specified by the original author.

Error message

Something went wrong. Error code: 0x80070002. You can try again, or contact your system administrator.

TL;DR

0x80070002 means a file or object the enrollment needed was not found, most often a broken app package or missing policy payload. Check the Intune management extension log for the failing step, fix or remove the offending app or policy, reset the device, and re-run Autopilot.

Steps

1. On the failed device, collect the Intune management extension log and search for 80070002. Expected: The log names the app or policy step that returned the error.

2. In Intune, check the failing app package or policy assignment for a missing source file or bad detection rule. Expected: You find the broken package or assignment.

3. Fix the package, exclude the device from the bad assignment, or remove the step per your change process. Expected: The assignment no longer targets the broken content.

4. Reset the device and re-run Autopilot enrollment. Expected: Enrollment completes past the enrollment status page.

When to use

• The exact code 0x80070002 appears during Autopilot enrollment
• The failure repeats on reset with the same profile
• The log points at one app or policy step

When not to use

• The enrollment hangs without an error code (timeout instead)
• The error code is different, like 0x801c0003 (different root cause)
• The device never reaches the enrollment status page (network or Autopilot registration issue)

Why this happens

0x80070002 is the Windows file-not-found error surfacing through the enrollment engine. During Autopilot it typically means an app installer referenced a missing file, a detection script looked for a path that does not exist, or a policy payload failed to download.

Edge cases

• A single broken win32 app assigned to all Autopilot devices will brick every enrollment until excluded.
• Reset keeps the Autopilot registration; a full wipe and re-import is rarely needed.

Provenance

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

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

Thread query: autopilot 80070002

TL;DR: 0x80070002 means a file or object the enrollment needed was not found, most often a broken app package or missing policy payload. Check the Intune management extension log for the failing step, fix or remove the offending app or policy, reset the device, and re-run Autopilot.