diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index c1f9331822..db8c0256dd 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -25,12 +25,20 @@ ms.topic: article + + +
IssueMore information + +
Windows Autopilot device provisioning can fail with TPM attestation errors or ESP timeouts on devices where the real-time clock is off by a significant amount of time (e.g. several minutes or more).To fix this issue:
  1. Boot the device to the start of the out-of-box experience (OOBE). +
  2. Establish a network connection (wired or wireless). +
  3. Run the command w32tm /resync /force to sync the time with the default time server (time.windows.com).
+
Windows Autopilot for existing devices does not work for Windows 10, version 1903; you see screens that you've disabled in your Windows Autopilot profile, such as the Windows 10 License Agreement screen.
 
This happens because Windows 10, version 1903 deletes the AutopilotConfigurationFile.json file.
To fix this issue:
  1. Edit the Configuration Manager task sequence and disable the Prepare Windows for Capture step.
  2. Add a new Run command line step that runs c:\windows\system32\sysprep\sysprep.exe /oobe /reboot.
-More information +More information
TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK certificate. (An additional validation added in Windows 10 1903 to check that the TPM EK certs had the proper attributes according to the TCG specifications uncovered that a number of them don’t, so that validation will be removed). Download and install the KB4517211 update.
The following known issues are resolved by installing the August 30, 2019 KB4512941 update (OS Build 18362.329):