AppStream not loading profile and d: drive

The issue you're experiencing with AppStream not loading your profile and the D: drive not being mapped is a common problem, especially with the Blu Age L3 Workshop environment. This can happen due to various reasons, including expired streaming URLs or issues with data synchronization. Here are some steps you can try to resolve the issue:

1. Ensure you're using the correct User ID when creating a new streaming URL. For the Blu Age L3 Workshop, the User ID should be "BluAge-L3-Workshop-User". Using a different User ID can result in a new, clean session without your previous work.

2. Check if your original streaming URL has expired. If it has, you'll need to create a new one with the exact same User ID as before.

3. Verify that the persistent storage feature is properly enabled for your AppStream 2.0 fleet. This is crucial for maintaining access to your work on the D: drive.

4. If the D: drive is still not visible after creating a new streaming URL, it's possible that there was an issue with data synchronization to the S3 bucket. In this case, you may need to check the S3 bucket where your profile data is stored.

5. Look for a bucket with a name starting with "appstream2-app-settings-" in your S3 console. Navigate to the appropriate folder structure within this bucket (usually under Windows/version/Server-2019/BluAge-L3-Workshop-Stack/custom/).

6. If you see multiple profile files (Profile.vhdx) in this location, keep only the largest one and delete the others. This can sometimes resolve profile loading issues.

7. After making these changes, try creating a new streaming URL again and launching a new session.

If these steps don't resolve the issue, you may need to contact AWS support or the Blu Age L3 Workshop support team for further assistance, as there might be specific configurations or limitations in your AppStream 2.0 environment causing this problem.

Remember that in AppStream 2.0, only data stored in the D:/PhotonUser directory is persisted between sessions. If you've been working outside this directory, that data may not be recoverable.
Sources
APPSTREAM 2.0 Error loading user settings and accessing D: Drive | AWS re:Post
Appstream: Original Appstream link is expired after 7 days, Application Persistent storage is active, New appstream link doesnt show the workspace in D:\ and configuration is reset. | AWS re:Post
AWS BluAge AppStream - workspace folder disappeared due to streaming URL expired | AWS re:Post
Blu Age L3 Refactorings (set up environment) Profile.vhdx dont found | AWS re:Post