AppStream 2.0 Default Web Browser Not Remembered On Deployed Fleet

Hello,

Thank you for contacting AWS Premium Support. My name is Lwazi and I will be assisting you with this case today.

You contacted us today as you have an issue with Default Web Browser Not Remembered On Deployed Fleet.

In order to update the default browser to Chrome, kindly attempt the following steps:

1. Open Image Builder in Administrator mode;
2. Create a folder in C drive called Temp;
3. Open Default Apps from system settings and set up the default browser to Chrome;
4. Export the custom default app association with dism.exe to Temp folder;
5. On PowerShell execute command:

• dism /online /export-defaultappassociations:"C:\Temp\IE-DefaultBrowser.xml"
• dism.exe /Online /Import-DefaultAppAssociations:C:\temp\IE-DefaultBrowser.xml

6. Once you have created an image from the image builder after making the above changes, attach it to a fleet. The settings for the Chrome should be retained on the fleet.

However, if it works with newly created user profiles but not with existing user profiles. Reset a user's application settings, you must find and delete the VHD and associated metadata file from the S3 bucket in your AWS account [1]. The reason for deleting the user vhdx is Persistent application settings are saved to a Virtual Hard Disk (VHD) file. This file is created the first time a user streams an application from a stack on which application settings persistence is enabled [2]. If the fleet associated with the stack is based on an image that contains default application and Windows settings, the default settings are used for the user's first streaming session.

References [1] https://docs.aws.amazon.com/appstream2/latest/developerguide/administer-app-settings-vhds.html#app-persistence-s3-reset [2] https://docs.aws.amazon.com/appstream2/latest/developerguide/how-it-works-app-settings-persistence.html