Why can't I create a WorkSpaces BYOL image?
"I tried to create an Amazon WorkSpaces bring your own license (BYOL) image, but it failed. What can I do to fix this issue?"
"I tried to create an Amazon WorkSpaces bring your own license (BYOL) image, but it failed. What can I do to fix this issue?ResolutionFollow these steps to resolve a WorkSpaces BYOL image validation failure:1.    Connect to the virtual machine (VM) in the on-premises environment. Download and run the BYOL Checker PowerShell script. The BYOL Checker script verifies that the image you want to import meets all the requirements for a successful import. The script also provides a detailed report of any issues that must be corrected before image creation.Important: All BYOL Checker script tests must pass for WorkSpaces image validation to succeed.The BYOL Checker script generates two log files: BYOLPrevalidationlogYYYY-MM-DD_HHmmss.txt and ImageInfo.text. These files are located in the directory that contains the BYOL Checker script files. Review the log files for errors.If issues persist after running the BYOL Checker script and reviewing the log files, then perform the following steps.2.    If your imported BYOL image has a firewall turned on, verify in the VM that the firewall isn't blocking any necessary ports. Certain ports are required for downloading scripts used for image creation.3.    Verify that the applications installed on your WorkSpace are compatible with Sysprep. Run the following PowerShell command to list all the AppX packages installed:Get-AppxPackage -AllUsers | Format-List -Property PackageFullName,PackageUserInformationIf image creation fails at the Sysprep stage, see the article about Sysprep failures on the Microsoft website.4.    Make sure that the disk isn't encrypted. Image creation fails if the disk used for importing a VM is encrypted.Related informationBring Your Own Windows desktop licensesHow do I troubleshoot WorkSpaces image creation issues?Follow"