0x801C03EA

Registering your device for mobile management failed

Last reviewed 2026-08-05 by the Just Software engineering team ยท also seen as 801c03ea, registering your device for mobile management failed 3, failed: 3, 0x801c03ea

What it means

Autopilot shows Registering your device for mobile management (Failed: 3, 0x801C03EA). The documented cause is a TPM that supports version 2.0 but is still running 1.2 firmware and has not been upgraded. A second, entirely separate cause produces the same error: the device sits in two assigned groups, each of which has a different Autopilot profile, so provisioning cannot decide which profile applies.

Common causes

  1. The device has a TPM chip capable of version 2.0 that has not yet been upgraded to 2.0 firmware.

  2. The same device is a member of two groups, each assigned a different Autopilot deployment profile.

How to fix it

  1. Upgrade the TPM firmware to version 2.0 using the OEM's tool, then re-run Autopilot. Vendors ship this as a firmware or BIOS update.

  2. If the TPM is already 2.0, check group membership: find every group containing the device and confirm only one Autopilot profile reaches it. Remove the assignment that shouldn't apply.

Frequently asked

How do I check the TPM version on the device?
Run tpm.msc — the Specification Version under TPM Manufacturer Information shows 1.2 or 2.0. Get-Tpm in PowerShell reports the same, and dsregcmd /status shows whether the device key ended up TPM-protected.
An unhandled error has occurred. Reload ๐Ÿ—™