Windows-itpro-docs: VM TPM Error code

[lanatmwan]

The documentation indicates you will get a 0x800705B4 timeout error if you try self deployment to a VM due to the unsupported hyper-v TPM. I am not sure if that is an error displayed somewhere, but it is not the error I experienced. During the OOBE setup on a VM that I had targeted for self deployment I got a 0x801c03ea error during the "Device preparation" phase.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6867cc8c-868d-d472-8aa5-1ed5b94ced2c
• Version Independent ID: 6822e12d-7474-9e49-1e8b-88f7eec3b22c
• Content: Windows Autopilot Self-Deploying mode
• Content Source: windows/deployment/windows-autopilot/self-deploying.md
• Product: w10
• Technology: windows
• GitHub Login: @greg-lindsay
• Microsoft Alias: greglin

[e0i]

@officedocsbot assign @e0i

[e0i]

@lanatmwan

The issue has been noted and the document will be revised in the light of your feedback.

Thank you.

[illfated]

@lanatmwan : You have closed the issue, but nothing has been done to resolve the issue yet.
Please consider reopening the issue ticket so we can follow up on this issue.

[greg-lindsay]

Hi, the error code mentioned is not specific to a VM and the note is correct as written. However, I could add some more detail here about other codes.

See https://www.petervanderwoude.nl/post/windows-autopilot-self-deploying-mode/

Error | Description
-- | --
0x800705B4 | This error means that the device is either a virtual machine, or does not have TPM 2.0, and is not capable of running Autopilot self-deploying.
0x801c03ea | This error means that the device is TPM 2.0 capable, but that the TPM still needs to be upgraded from 1.2 to 2.0.
0xc1036501 | This error means that the device cannot do an automatic MDM enrollment, because there are multiple MDM configurations in Azure AD.

[greg-lindsay]

I'm closing the issue for now. I will update the article to add more codes and describe the other reasons.

[illfated]

Thank you for the follow-up and comments. Appreciated.

[greg-lindsay]

Update: The article linked above actually turns out to be a little off. I've added these three codes to our documentation with explanations. The first code (0x800705B4) is more accurately a timeout that can be caused by many issues, one of which is that the device does not have TPM 2.0.

The second code (0x801c03ea) - which is what this post asked about - means that the device couldn't join Azure Active Directory using a device token because TPM attestation failed. One possible cause might be that the device is using TPM 1.2 rather than 2.0.

The third code (0xc1036501) is correct as written above. It is caused by multiple MDM configurations.

[illfated]

👍 Thank you for the update. Looks very useful (although not directly affecting my line of work).