Autopilot VM Stuck at Preparing Device for Mobile Management

You spin up a Hyper-V VM to test a Windows Autopilot profile, sign in during OOBE, and setup fails with Preparing your device for mobile management. The same profile works on physical hardware.

Microsoft documents this one. The Windows Autopilot known issues page says that when you use Windows Autopilot on a virtual machine, this error might occur, and gives a single fix: “make sure the virtual machine is configured with a minimum of 2 processors and 4 GB of memory.”

I haven’t reproduced this on a live tenant for this article. Everything below comes from Microsoft Learn, linked inline, and I haven’t run the commands against a real VM.

Fix: give the VM 2 processors and 4 GB of memory

Raise the VM’s virtual processor count and memory. On the Hyper-V host, the Hyper-V PowerShell module has Set-VMProcessor and Set-VMMemory:

# Run on the Hyper-V host. Replace AutopilotVM with your VM name.
Set-VMProcessor -VMName AutopilotVM -Count 2
Set-VMMemory -VMName AutopilotVM -StartupBytes 4GB

Microsoft’s minimum is 2 processors and 4 GB. Going above it is fine; going below it is the documented cause.

Then run the deployment again. A VM that already got partway through enrollment is a half-provisioned device, so a clean rerun (reset the VM or rebuild it) tells you more than retrying on the same state.

Check the deployment mode before you blame the VM size

A VM only works for some Autopilot flows. Microsoft is explicit about the other two:

• Self-deploying mode: “If a self-deploying mode deployment is attempted on a device that doesn’t have support for TPM 2.0 or on a virtual machine, the process fails when verifying the device with an 0x800705B4 timeout error. This limitation includes Hyper-V virtual TPMs.” (Windows Autopilot self-deploying mode)
• Pre-provisioning: the requirements list physical devices that support TPM 2.0 and device attestation, and say “Virtual machines aren’t supported.” (Windows Autopilot for pre-provisioned deployment)

So adding a virtual TPM to a Generation 2 VM, which Hyper-V supports (Hyper-V Generation 2 virtual machine security features), doesn’t make it a valid test for self-deploying mode. If you see 0x800705B4 on a VM, that’s the securing your hardware 0x800705b4 failure, and the answer is a physical device.

What not to do

• Changing the Autopilot profile or Intune policies first. The known issue names the VM’s processor and memory as the fix. Rule that out before touching tenant config.
• Testing pre-provisioning or self-deploying on a VM. Microsoft doesn’t support either there, so a failure tells you nothing about your production config.

For the wider test flow, see Autopilot part 3: testing and troubleshooting.

Get the ESP Triage Checklist

Stuck on the Enrollment Status Page next? Get the free ESP Triage Checklist: two pages of read-only checks for which ESP phase failed, whether the app is tracked, and which logs and registry keys to read.

Get the Deployment Doctor

Kit 1 founding presale is open: $39 (regular $49). The Autopilot + Device Prep Deployment Doctor checks your tenant, read-only, for the config that breaks ESP and Device Preparation. You pay now and get the files by Tuesday, December 1, 2026, sooner if they’re ready. Full refund any time before delivery, then 14 days after delivery. The founding price runs until Friday, December 4, 11:59 PM MT.

Want to look first? The free, read-only beta scripts are on GitHub: autopilot-deployment-doctor-beta. Its README says they haven’t been run against a live tenant.

FAQ

Why does Autopilot fail at Preparing your device for mobile management on a VM?

Microsoft lists it as a known issue for Windows Autopilot on virtual machines. The documented fix is to configure the VM with a minimum of 2 processors and 4 GB of memory.

Can I test Windows Autopilot self-deploying mode on a Hyper-V VM?

No. Microsoft says self-deploying mode on a virtual machine fails with an 0x800705B4 timeout error when verifying the device, and that this includes Hyper-V virtual TPMs.

Does pre-provisioning work on a virtual machine?

No. Microsoft’s pre-provisioning requirements call for physical devices that support TPM 2.0 and device attestation, and state that virtual machines aren’t supported.

Sources

All retrieved 2026-10-22.

• Windows Autopilot known issues, Microsoft Learn: the VM error and the 2 processor, 4 GB fix.
• Windows Autopilot self-deploying mode, Microsoft Learn: VMs and Hyper-V virtual TPMs fail with 0x800705B4.
• Windows Autopilot for pre-provisioned deployment, Microsoft Learn: VMs not supported.
• Hyper-V Generation 2 virtual machine security features, Microsoft Learn: vTPM on Generation 2 VMs.
• Set-VMProcessor and Set-VMMemory, Microsoft Learn: -Count and -StartupBytes parameters.