Autopilot reports Securing your hardware (Failed: 0x800705b4), followed by Joining your
organization's network (Previous step failed) and Registering your device for mobile management
(Previous step failed). 0x800705b4 is the generic Windows timeout HRESULT — the attestation
step waited for a hardware TPM that could satisfy self-deploying mode and never got one.
0x800705B4
Securing your hardware failed in Autopilot
What it means
Common causes
The device does not have a physical TPM 2.0 chip. Virtual TPMs — including Hyper-V VMs — and TPM 1.2 chips do not work with self-deploying mode.
The device is not running a supported build: Windows 10 1709 or later, or Windows 10 1809 or later where Microsoft Entra hybrid join is used.
How to fix it
Confirm the device has a physical, discrete or firmware TPM 2.0 (
tpm.mscorGet-Tpm). Self-deploying and pre-provisioning modes both depend on TPM attestation.Use user-driven Autopilot instead of self-deploying mode on hardware that cannot attest — user-driven mode has no TPM attestation requirement.
Update the device to a supported Windows build before provisioning.
For lab work, remember that Hyper-V virtual TPMs are explicitly not supported here — test self-deploying mode on physical hardware.