Skip to content

AWS WorkSpace Personal - Image Creation fails at 45% (Copying profile) - Image Checker passed, how to capture logs during rollback?

0

Hello everyone,

I am experiencing a recurring issue when trying to create a custom image from an existing AWS WorkSpace (Windows Server 2016 Datacenter / Windows 10 desktop experience). The image creation process consistently fails exactly at the 45% mark ("Copying WorkSpace profile"). After a while, the process times out, and AWS automatically rolls back the WorkSpace to its original state.

**Validations and Troubleshooting performed so far: ** Image Checker Tool: Ran the official AWS WorkSpaces Image Checker and it completes with a 100% success rate (no issues detected, no pending reboots, profile size validated). Profile Size & File Count: We verified the profile size using robocopy /L. The profile is well under the 10GB limit (approx. 670 MB) and has less than 4,000 files. **Cache & Residual Cleanups: **We manually purged paths that typically cause issues during profile copying, including:

  • AppData\Local\Microsoft\Windows\WebCache\
  • AppData\Local\TileDataLayer\Database\
  • Orphaned OneDrive logs and Temp folders. **File Locks: **Before triggering the image creation from the AWS Console, we forcefully stopped explorer.exe and related background services to ensure no system databases (like vedatamodel.edb or WebCacheLock.dat) were locked.

The Problem: Because WorkSpaces is a managed service, when the imaging fails, AWS automatically restores the instance from a snapshot. This rollback wipes out any logs generated during the actual imaging phase (such as C:\Windows\System32\Sysprep\Panther or any other backend logs).

Since we don't have hard evidence of what exact file, service, or process is timing out the copy phase, we are flying blind.

My questions are:

Is there any way, workaround, or AWS service to capture, monitor, or stream the logs during the "Suspended/Imaging" state before the automatic rollback destroys them? Are there any other hidden logs, EC2Launch logs, or local validations we can check prior to launching the image, considering the Image Checker gives us a false positive (all green)?

Any guidance on how to debug this "black box" behavior would be greatly appreciated!

asked 2 months ago187 views

1 Answer
0

When image creation fails during the profile copying phase despite the Image Checker passing, there are several additional areas to investigate that may not be caught by the Image Checker:

First, verify that the WorkSpace is not assigned to a user within a Domain Guests group. You can check for domain accounts by running this PowerShell command: Get-WmiObject -Class Win32_Service | Where-Object { $_.StartName -like "$env:USERDOMAIN" }

For Windows 7 WorkSpaces specifically, ensure that all folder paths within the user profile are less than 261 characters, as long profile paths can cause image creation errors. Additionally, verify that the system and all application packages have full permissions on the profile folder.

Even if files appear unlocked, some files in the user profile may still be locked by a process or in use during image creation, which can cause the profile copying to fail. This can happen even after stopping explorer.exe, as other background processes may maintain locks.

Group Policy Objects can also interfere with image creation. Some GPOs restrict access to the RDP certificate thumbprint when requested by the EC2Config service or EC2Launch scripts during Windows instance configuration. Before attempting to create an image, try moving the WorkSpace to a new organizational unit with blocked inheritance and no GPOs applied.

For Windows Remote Management, ensure the WinRM service is configured to start automatically by opening services.msc, locating Windows Remote Management (WS-Management), and setting its Startup type to Automatic.

Regarding log capture during the imaging process, the managed nature of WorkSpaces means that direct access to logs during the suspended/imaging state is limited. Your best approach is to thoroughly investigate these additional potential issues before initiating image creation, as the automatic rollback will indeed remove any logs generated during the failed imaging attempt.
Sources
Create a custom WorkSpaces image and bundle for WorkSpaces Personal - Amazon WorkSpaces
Create a custom image and bundle for WorkSpaces Pools - Amazon WorkSpaces

answered 2 months ago

AWS
SUPPORT ENGINEER

reviewed 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.