- Newest
- Most votes
- Most comments
The error you're encountering when trying to expand the Profile.vhdx file is not uncommon, and there are a few steps you can take to address this issue:
-
First, ensure that you're using the correct command syntax. Instead of 'expand vdisk maximum=5000', you should use the 'extend' command. The correct sequence of commands should be:
diskpart select vdisk file="C:\path\to\application\settings\Profile.vhdx" attach vdisk extend
-
If you're still encountering issues after using the correct command, it's possible that the VHD file is corrupted or there's not enough free space on your disk to expand the VHD.
-
As an alternative approach, since you're working on the L3 workshop environment, you might consider using an EC2 Windows instance to modify the VHDX file. This method can sometimes be more reliable:
- Create a Windows EC2 instance
- Download the Profile.vhdx file from your S3 bucket to this EC2 instance
- Use the diskpart commands on the EC2 instance to modify the VHDX file
- Upload the modified VHDX file back to your S3 bucket
-
If you continue to face issues, it may be worth reaching out to the L3 workshop support team at aws-blu-age-l3-certification-workshop@amazon.com. They might be aware of specific issues related to the workshop environment and could provide more targeted assistance.
Remember to properly close your AppStream session after making changes to ensure that your modified Profile.vhdx file syncs correctly with the S3 bucket.
Sources
Increase the Size of the Application Settings VHD - Amazon AppStream 2.0
Increase the size of the Application Settings VHDX on MacOS | AWS re:Post
Blu Age L3 Refactorings (set up environment) Profile.vhdx dont found | AWS re:Post
Relevant content
- asked 3 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago