Troubleshoot Sysprep - Amazon Elastic Compute Cloud
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Troubleshoot Sysprep

If you experience problems or receive error messages during image preparations, review the following logs. Log location varies depending on whether you are running EC2Config, EC2Launch v1, or EC2Launch v2 with Sysprep.

  • %WINDIR%\Panther\Unattendgc (EC2Config, EC2Launch v1, and EC2Launch v2)

  • %WINDIR%\System32\Sysprep\Panther (EC2Config, EC2Launch v1, and EC2Launch v2)

  • C:\Program Files\Amazon\Ec2ConfigService\Logs\Ec2ConfigLog.txt (EC2Config only)

  • C:\ProgramData\Amazon\Ec2Config\Logs (EC2Config only)

  • C:\ProgramData\Amazon\EC2-Windows\Launch\Log\EC2Launch.log (EC2Launch v1 only)

  • %ProgramData%\Amazon\EC2Launch\log\agent.log (EC2Launch v2 only)

If you receive an error message during image preparation with Sysprep, the OS might not be reachable. To review the log files, you must stop the instance, attach its root volume to another healthy instance as a secondary volume, and then review the logs mentioned earlier on the secondary volume. For more information about the purpose of the log files by name, see Windows Setup-Related Log Files in the Microsoft documentation.

If you locate errors in the Unattendgc log file, use the Microsoft Error Lookup Tool to get more details about the error. The following issue reported in the Unattendgc log file is typically the result of one or more corrupted user profiles on the instance:

Error [Shell Unattend] _FindLatestProfile failed (0x80070003) [gle=0x00000003]
Error [Shell Unattend] CopyProfile failed (0x80070003) [gle=0x00000003]

There are two options for resolving this issue:

Option 1

Use Regedit on the instance to search for the following key. Verify that there are no profile registry keys for a deleted user.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\

Option 2

  1. Edit the relevant file, as follows:

    • Windows Server 2012 R2 and earlier – Edit the EC2Config answer file (C:\Program Files\Amazon\Ec2ConfigService\sysprep2008.xml).

    • Windows Server 2016 and 2019 – Edit the unattend.xml answer file (C:\ProgramData\Amazon\EC2-Windows\Launch\Sysprep\Unattend.xml).

    • Windows Server 2022 – Edit the unattend.xml answer file (C:\ProgramData\Amazon\EC2Launch\sysprep\unattend.xml).

  2. Change <CopyProfile>true</CopyProfile> to <CopyProfile>false</CopyProfile>.

  3. Run Sysprep again. Note that this configuration change will delete the built-in administrator user profile after Sysprep completes.