Problems with ActiveX registration on AppStream

This issue is likely related to how AppStream 2.0 handles file redirection during the app block creation process. When you create an app block, AppStream 2.0 redirects the installed files to the app block VHD, with only links to the actual files maintained at the original location.

Applications that rely on ActiveX controls can encounter problems because:

1. The ActiveX registration process is location-sensitive. When you register the ActiveX controls during image building, they're registered with specific file paths.

2. When the app block is deployed, the actual file locations may differ from where they were during registration, causing the "ActiveX not registered" error.

To resolve this issue:

• Consider using custom packaging methods for your app block instead of the standard AppStream 2.0 packaging if your application performs location-based checks.

• Ensure your application launch script includes the necessary ActiveX registration commands using the 32-bit version of regsvr32, pointing to the correct location where the files will be at runtime.

• If possible, modify your application to use relative paths for ActiveX controls rather than absolute paths.

• Check the error log file at C:\AppStream\AppBlocks\errorLog after a failed attempt for specific error messages that might provide more details about the registration failure.

If the issue persists, you may need to contact AWS Support for assistance with this specific application packaging scenario.
Sources
Unsupported Applications - Amazon AppStream 2.0