Skip to content

Give up exactly what was asked, and put the Dev Drive where it was freed #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ALERTua merged 2 commits into from
Aug 26, 2026
Merged

Give up exactly what was asked, and put the Dev Drive where it was freed #97

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
938989f
fix: give up exactly what was asked, and put the drive where it was f…
ALERTua Aug 26, 2026
af53fa7
fix: align the new partition's start, and stop promising a drive befo…
ALERTua Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,9 @@ Everything above produces one screen, and nothing on disk has changed when it ap
===============================================================================

* Shrink Drive D (ALERT) by 199 GB to free up space
* Create 199 GB Dev Drive on Disk 1 (CT4000P3PSSD8) using ReFS
* Create 249 GB Dev Drive on Disk 1 (CT4000P3PSSD8) using ReFS
50 GB of unallocated space already sits next to drive D and will be taken
as well, so the Dev Drive comes out 249 GB rather than the 199 GB being freed.
* Name the Dev Drive Projects
* Skip BitLocker encryption
* Enable ReFS deduplication and ZSTD compression, level 2
Expand Down Expand Up @@ -196,6 +198,7 @@ In compress-only mode there is no weekly maintenance job and no duration or CPU
## Troubleshooting

- **Windows will not shrink the volume far enough.** Shrinking stops at the last written file block, so fragmentation limits it regardless of free space. The script shows the real limit Windows reports and suggests a third-party tool where that is not enough
- **Shrink mode takes the whole free run behind the drive, and says so before you agree.** The volume gives up exactly the amount you asked to free, and the Dev Drive then fills everything unallocated immediately behind it - the space just freed plus anything already sitting there. The plan names the resulting size and where the extra came from - or, on the rare drive whose limits Windows will not report, says the size shown is only a floor. Unallocated space elsewhere on the disk is never touched
- **The drive comes up read-only.** That is `FDVDenyWriteAccess` - see [Caveats](#caveats). Enable BitLocker, or clear the setting if it is yours to clear
- **The `.vhdx` is gone after a restart.** Windows refused `ATTACH_VIRTUAL_DISK_FLAG_AT_BOOT`, or automatic mounting was declined. Mount it by hand with the command the script printed
- **A run failed part-way.** It names what it left behind - a `.vhdx` still attached, or a volume already shrunk. Undo that before running again: a rerun starts from the beginning and would shrink the drive a second time
Expand Down
Loading
Loading