Error 0x800705b4 during Securing your hardware is a timeout, but the screen location makes the likely causes narrower than a generic Windows timeout. Microsoft documents this failure in Windows Autopilot self-deploying scenarios when the device does not meet the physical TPM 2.0 requirement. Virtual TPMs and TPM 1.2 do not satisfy self-deploying mode.
Before deleting device records or repeating provisioning, confirm the deployment mode and hardware eligibility. A user-driven Autopilot profile has different requirements, so the profile assignment is as important as the error code.
Triage at the device
Confirm the TPM is physical and ready
From Windows or the technician environment, run tpm.msc or use Windows Security > Device security > Security processor details when available. Record the specification version, manufacturer, and readiness state. Self-deploying mode requires a physical TPM 2.0; a Hyper-V virtual machine is not a valid test for this path.
Check the device manufacturer’s support site for current BIOS and TPM firmware. Microsoft lists known TPM vulnerabilities as a reason some attestation attempts fail and recommends updating TPM firmware for the affected cases. Follow the vendor’s prerequisites, including power and BitLocker recovery-key precautions.
Verify the Windows and profile combination
Microsoft’s enrollment error guidance requires Windows 10 build 1709 or later for the documented self-deploying case, and build 1809 or later when Microsoft Entra hybrid join is used. In a current deployment, use a supported Windows release and confirm the device received the intended Autopilot profile rather than a conflicting assignment.
If the device has already reached Intune but reports unexpected health, the device-status interpretation guide can help separate reporting delay from provisioning failure. The Securing your hardware timeout still needs TPM and Autopilot evidence first.
A technician recovery playbook
- Stop repeated resets and record the exact error screen, serial number, hardware hash identity, and UTC time.
- Confirm the assigned Autopilot profile and whether it uses self-deploying or pre-provisioning mode.
- Verify physical TPM 2.0 readiness and update BIOS or TPM firmware through the OEM process if required.
- Confirm the device has stable access to Microsoft’s documented Autopilot network endpoints, with TLS inspection exceptions where required by policy.
- Retry once after the hardware and network checks.
- If Microsoft’s known-issue guidance matches a stale object scenario, remove the exact device from Microsoft Entra ID, Intune, and Windows Autopilot, then re-register it.

The deletion step is not a universal first fix. Device records can carry assignments and lifecycle history. Resolve the serial number and Autopilot identity precisely, export required recovery information, and follow the organization’s de-registration procedure before removal.
Separate hardware ineligibility from attestation trouble
Hardware ineligibility
A VM, TPM 1.2 device, disabled TPM, or unsupported Windows configuration cannot be made compatible by waiting longer. Change the deployment mode or hardware plan. If self-deploying mode is not mandatory, an administrator can evaluate a user-driven profile that fits the organization’s security requirements.
Attestation or network timeout
A physical TPM 2.0 device can still time out when firmware, certificates, device identity, or required endpoint connectivity interfere with attestation. Compare another identical model on the same network and the same device on an approved alternate network. Change one variable per attempt.
Microsoft’s Autopilot known-issues page is time-sensitive. Review it for current TPM attestation codes and remediation before using an older forum workaround. Error 0x800705b4 is general, so correlate it with the Securing your hardware stage and logs rather than the number alone.
Gather logs before the next wipe
Collect Autopilot diagnostics and event logs while the failure can still be correlated. Useful records include the device serial number, manufacturer and model, BIOS version, TPM manufacturer/version, assigned profile, network, attempt time, and relevant Microsoft-Windows-User Device Registration/Admin events.
On a managed Windows build, confirm updates and OEM firmware are current. The Windows update control walkthrough is useful background for a normally enrolled endpoint, but provisioning teams should use their approved imaging and firmware process instead of changing update policy at OOBE.
If identical hardware succeeds elsewhere, focus on network and device identity. If every unit of one model fails while other models succeed, prioritize OEM firmware and TPM capability. If one reused device fails after earlier deployments, stale Intune, Entra, or Autopilot records become more plausible.
Keep retries limited and labeled. Repeated attestation attempts without a changed condition can consume technician time while making the incident timeline harder to read. Record what changed between attempts—firmware, network, profile, or device registration—and the exact result. When an OEM escalation is needed, that sequence helps the vendor compare the TPM state with a known-good unit instead of asking the deployment team to reproduce the same timeout again.
Autopilot timeout questions
Can I use self-deploying mode on a Hyper-V virtual machine?
No. Microsoft’s troubleshooting guidance states that virtual TPMs do not meet the physical TPM 2.0 requirement for self-deploying mode. Use an appropriate supported deployment path for virtual testing.
Does 0x800705b4 always mean the TPM is defective?
No. It is a timeout code. At Securing your hardware, TPM capability is a common cause, but firmware, attestation, connectivity, profile, and stale device identity can also matter. Verify evidence before replacing hardware.
Should I delete the Autopilot device immediately?
Not before confirming the exact identity and preserving required records. Microsoft documents removal and re-registration for some matched scenarios, but deletion is disruptive and can affect assignments. Use it after hardware, firmware, profile, and network checks or when current known-issue guidance points there.
Why does a user-driven profile work on the same device?
User-driven and self-deploying modes use different enrollment paths and requirements. Success in user-driven mode can indicate that general network and tenant access work while the TPM-based self-deploying path is ineligible or failing attestation.
Choose the fix that matches the failed stage
Treat the screen text, deployment mode, and TPM evidence as one incident. Prove physical TPM 2.0 support, use current firmware, validate Autopilot connectivity and profile assignment, and collect logs before destructive cleanup. If the hardware cannot meet self-deploying requirements, change the deployment design rather than sending the device through the same timeout again.