DEV Community

Cover image for Windows Autopilot: The 7 Most Common Deployment Failures (And Exactly How to Fix Them)
Exactey
Exactey

Posted on

Windows Autopilot: The 7 Most Common Deployment Failures (And Exactly How to Fix Them)

If you've deployed Windows Autopilot more than twice, you've hit at least one of these. The same seven failures keep showing up across every environment. Not edge cases — the same errors, over and over.
This post covers each one with the exact cause and fix.

Error 1: 0x800705B4 — "Preparing device for mobile management failed"
Nine times out of ten: TPM.
Check in this order:

Run tpm.msc on the device. Specification Version must show 2.0 — if it shows 1.2, the device is not supported for Self-Deploying mode.
Open BIOS/UEFI → Security → TPM → must be set to Enabled. Not just present. Actually enabled.
If TPM shows 2.0 but error persists → Clear TPM in BIOS, then retry. This fixes corrupted TPM state from previous enrollment attempts.
Open CMD via Shift+F10 during OOBE and run: Test-NetConnection -ComputerName login.microsoftonline.com -Port 443
Check Event Viewer: Microsoft-Windows-ModernDeployment-Diagnostics-Provider → Autopilot

Note: Hyper-V virtual TPMs are NOT supported for Autopilot Self-Deploying mode. If you're testing on a VM, this error is expected and cannot be fixed.

Error 2: 0x80180014 — Re-enrollment after reset fails
After a first Self-Deploying or Pre-Provisioning deployment, Intune blocks re-enrollment of the same device.
Fix:

Intune Admin Center → Devices → All Devices → find the device → Delete
Redeploy — it will now enroll fresh

If caused by a malformed Hardware Hash CSV: never open the CSV in Excel. Excel corrupts the binary hash format silently. Re-collect with PowerShell: Get-WindowsAutopilotInfo -OutputFile C:\hash.csv

Error 3: No company branding on OOBE — standard Windows setup appears
The Autopilot profile was not received by the device.
Root causes in order of likelihood:

Device is not registered in the Autopilot service at all
Profile is not assigned to a group the device belongs to
No network connection at first boot
Group sync has not completed after device import

The dynamic group rule must be: (device.devicePhysicalIds -any (_ -eq "[ZTDId]"))
Quick test: after connecting to network during OOBE, wait 60 seconds. If the sign-in page shows your company name and logo, the profile was received. If it shows the generic Microsoft logo, the profile was not received.

Error 4: 0x80180005 — "ZTD Profile was not assigned to ZTD Device"
Commonly seen during Pre-Provisioning (White Glove) mode in the technician phase.
Fix:

Delete all objects for this device in Intune, Entra ID, and local AD if Hybrid
Re-register the device with a fresh Hardware Hash
Verify the profile is assigned to the dynamic device group
Wait 15 minutes for sync to complete before retrying

Error 5: ESP stuck or timing out
Common causes: a Win32 app failing to install, ESP timeout too low for your app payload (60 minutes default is often not enough), or slow internet during large app downloads.
Diagnose with: Get-AutopilotDiagnostics (install from PowerShell Gallery first)
Fixes:

Increase ESP timeout to 90-120 minutes: Intune → Windows Enrollment → ESP
Check app configuration in Intune: correct requirements? All dependencies present?
Temporarily disable ESP to isolate whether the issue is app-related

Error 6: 0x8007052E — "Registering your device for mobile management failed"
Authentication failure during enrollment.
Common causes: incorrect credentials during OOBE, a Conditional Access policy blocking the unenrolled device, or firewall blocking Microsoft endpoints.
Fix:

Check Entra ID Sign-in logs: Entra Admin Center → Monitoring → Sign-ins → find the failed event → Conditional Access tab
If a CA policy is blocking: temporarily exclude the device or user during enrollment
Verify all Autopilot network endpoints are reachable on port 443

I put together a complete PDF guide covering all errors in full detail, a complete 8-step deployment walkthrough, recommended profile settings, and a 24-item checklist — all sourced directly from official Microsoft documentation.
Get it here: https://exactey.gumroad.com/l/windows-autopilot-setup-guide
Questions? Drop them in the comments — happy to help.

Top comments (1)

Collapse
 
exactey profile image
Exactey

Quick note — making the full PDF guide free for the next
24 hours for anyone who wants it. Just grabbing it is enough,
but if it helps you I'd really appreciate a short review on
the page. Link in the article.