From 25a1b7ceaebb3a0d137396458f42b9720651e1e6 Mon Sep 17 00:00:00 2001 From: Matthew Haughton <3flex@users.noreply.github.com> Date: Wed, 19 Feb 2020 14:00:59 +1100 Subject: [PATCH] Advise that issue affecting 1903 also affects 1909 "Prepare Windows for Capture" step fails on 1909 as well, deleting the AutopilotConfigurationFile.json because the /generalize switch is applied to sysprep command which deletes the file. --- windows/deployment/windows-autopilot/known-issues.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 5be64cc194..12f4bedfef 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -32,9 +32,9 @@ ms.topic: article
  • 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. +Windows Autopilot for existing devices does not work for Windows 10, version 1903 or 1909; 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. +This happens because Windows 10, version 1903 and 1909 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