jamesstringer90 / jamesstringer90/appsandbox
"HDD (GB)" column doesn't reflect current vhdx disk size
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 704
- Forks
- 75
- Avg merge
- 9m
- Merged PRs (30d)
- 6
Description
I created a new App Sandbox VM with a 32GB drive, and then once it was created and working, I stopped the VM, and moved the C:\ProgramData\AppSandbox\myvm\ folder to a drive with more space, and then used mklink to create a symbolic link to the folder so App Sandbox would still find it.
I tested the VM, and it still worked fine, so next I expanded the vhdx to 600GB, then booted the VM again and expanded the partition to fill the new space.
So now my VM reports C: is a 600GB drive, but the App Sandbox UI still shows 32GB.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report by creating a 32GB VM, expanding its VHDX and partition to 600GB, then inspect how the App Sandbox UI determines and displays the HDD (GB) value. Trace that size calculation and update it so the displayed value reflects the current virtual disk size; verify the UI reports 600GB after the expansion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100