Autopilot & Enrollmentdecimal -2147023436
Fix Intune Error 0x800705B4: A timeout (ERROR_TIMEOUT). In Autopilot it is typically TPM 2.0 attestation failing during self-deploying mode, or the ESP device phase timing out.
Open the log below first. It is the quickest way to confirm which of the causes applies before you change anything.
Microsoft-Windows-ModernDeployment-Diagnostics-Provider%4Autopilot.evtx
Folder: C:\Windows\System32\winevt\Logs\
Also check: Microsoft-Windows-DeviceManagement-Enterprise-Diagnostics-Provider%4Admin.evtx · Microsoft-Windows-User Device Registration%4Admin.evtx
Root causes
- The device does not have a physical TPM 2.0. Virtual machines, including Hyper-V virtual TPMs, and TPM 1.2 chips cannot use self-deploying mode.
- TPM attestation endpoints for the TPM vendor are blocked by a firewall or proxy.
- Specific TPM firmware has a known attestation problem, for example Infineon SLB9672 firmware 15.22 with an EK certificate.
- The ESP timeout is shorter than the time needed to install the required apps and policies.
- The Windows version is too old: self-deploying needs 1709 or later, and 1809 or later for hybrid join.
Step-by-step remediation
- On the device run Get-Tpm and confirm TpmPresent, TpmReady and a 2.0 specification version. A virtual machine cannot use self-deploying mode.
- Open the ModernDeployment-Diagnostics-Provider Autopilot log and note which phase timed out.
- Allow the TPM attestation URLs for your TPM vendor through the firewall and proxy, and bypass TLS inspection for them.
- Update the BIOS and TPM firmware from the OEM, particularly for the Infineon and Intel firmware TPM attestation issues.
- If the timeout is during the ESP, raise "Show an error when installation takes longer than specified number of minutes" and remove non-essential blocking apps.
- Delete the stale device record in Intune, reset the device and retry.
For the full diagnosis around this error, read Windows Autopilot Enrollment Status Page Stuck at 0% — Causes and Fixes.
Tighten the rollout around it
Enrollment and compliance errors usually trace back to rollout design and device permissions. See how the endpoint privilege management tools compare, and plan the next ring with a tested runbook.
Compare Intune endpoint privilege management toolsRelated Error Codes in This Category
Other Autopilot & Enrollment errors with their own runbooks.
- 0x80180014The MDM service refused enrollment: Windows (MDM) is blocked by an enrollment restriction, or the reused Autopilot device record is blocked.
- 0x80180013The user has reached the Intune device limit (15 by default), so enrollment of another device is refused.
- 0x80180026MDM enrollment was blocked because another management agent is present: automatic MDM enrollment collides with the legacy Intune PC client.
- 0x8018002BGroup Policy based automatic MDM enrollment failed, normally because the UPN is non-routable or the MDM user scope is None.
- 0x801C03EATPM attestation failed, so the device could not get a device token and failed to join Microsoft Entra ID.