You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Sparse VHD support is currently disabled due to potential data corruption. #13075
I noticed this issue was closed, but the problem wasn't fully addressed. The key is that --set-sparse requires a boolean value (true or false) but the prompt omits that.
I actually ran this command many times but ran into this today: I manually added true but had a typo in --allow-unsafe, which led me to search and find this issue. To prevent this confusion for others, I submitted a PR that properly adds the boolean value to the prompt.
Activity
github-actions commentedon Jun 9, 2025
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.
Diagnostic information
OneBlue commentedon Jun 9, 2025
jiaoyuan (@imjiaoyuan): The second command line is missing the
trueafter the--set-sparse. This is the command line you need:imjiaoyuan commentedon Jun 10, 2025
Blue (@OneBlue) Thank you for your answer, I made a stupid mistake!
junhaoliao commentedon Sep 23, 2025
Hi Blue (@OneBlue)
I noticed this issue was closed, but the problem wasn't fully addressed. The key is that
--set-sparserequires a boolean value (trueorfalse) but the prompt omits that.I actually ran this command many times but ran into this today: I manually added
truebut had a typo in--allow-unsafe, which led me to search and find this issue. To prevent this confusion for others, I submitted a PR that properly adds the boolean value to the prompt.You can see the PR here: #13512
docs(wsl): annotate memory-reclaim + sparse-VHD keys; add disk-reclai…