Autopilot failure:registering your device for mobile management （failed:3, 0x801C03EA)

Question

As title, recently when we enrolled device, Autopilot hang and finally failed at Device preparation.

Any suggestions for such kind of error?

Thanks in advance.

Answer 1

This error seems to indicate that the device has a TPM chip that supports version 2.0, but hasn't yet been upgraded to version 2.0.
Please upgrade the TPM chip to version 2.0.
If the issue persists, check whether the same device is in two assigned groups, with each group being assigned a different Autopilot profile. If it is in two groups, determine which Autopilot profile should be applied to the device, and then remove the other profile's assignment.
For more information about how to deploy a Windows device in kiosk mode with Autopilot, see Deploying a kiosk using Windows Autopilot.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

What type of TPM is on the device? This error is a TPM issue.

In particular:
This error indicates that TPM attestation failed, causing a failure to join Azure Active Directory with a device token.
The device has a TPM chip that supports version 2.0, but hasn't yet been upgraded to version 2.0

Answer 3

Hi all,

I have facing the error 0x801c03f3 when try to rejoin the device in autopilot program (INTUNE-Hybrid environment).

When it happened after I changed the motherboard of (dell 5420) laptop for your information dell (5420) laptop had TPM 2.0 version.

And I had the temporary solution -- After receiving the (0x801c03f3) error in INTUNE (Autopilot program) delete the device in INTUNE entire Tenant and re-add the laptop's by using same HWID for one more time.

If anyone know the root cause for this issue, please share the details.