From fc74f6c409c8609bb18a807bbef187d85e07628d Mon Sep 17 00:00:00 2001 From: Rebecca Agiewich Date: Thu, 17 Oct 2019 12:54:09 -0700 Subject: [PATCH] fixed spelling issue --- windows/deployment/windows-autopilot/known-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 9291def4d2..c1f9331822 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -54,7 +54,7 @@ This happens because Windows 10, version 1903 deletes the AutopilotConfiguration Windows Autopilot self-deploying mode fails with an error code:
0x800705B4This is a general error indicating a timeout. A common cause of this error in self-deploying mode is that the device is not TPM 2.0 capable (ex: a virtual machine). Devices that are not TPM 2.0 capable cannot be used with self-deploying mode. -
0x801c03eaThis error indictes that TPM attestation failed, causing a failure to join Azure Active Directory with a device token. +
0x801c03eaThis error indicates that TPM attestation failed, causing a failure to join Azure Active Directory with a device token.
0xc1036501The device cannot do an automatic MDM enrollment because there are multiple MDM configurations in Azure AD. See Inside Windows Autopilot self-deploying mode.
White glove gives a red screen and the Microsoft-Windows-User Device Registration/Admin event log displays HResult error code 0x801C03F3This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.