**Minor caveat when running the Sysinternals SDelete.exe tool, is that in the process of "Zeroing Out the Free Space" it will cause a Dynamically Expanding .vhdx to expand to its full configured size. So if you're overlapping the physical drive space by double-booking it ... This will byte you in the ass.-Stoic Joker
Would using cipher /W <drive> be any better?
-4wd
Unknown. It's really not a encryption/decryption issue I'm trying to address. It's an issue with compacting a .vhd/.vhdx drive (that has dynamically expanded due to the build update) to reclaim the unused free space. The SDelete -c run was supposed to assist with that according to a TechNet article about how to compact an uncooperative .vhd. And while it did do just that, it also shutdown the lab by overflowing the Host drive ... Which is a -
perhaps in retrospect obvious - behavior that was not mentioned in the article.
No additional software was ever added to the install, so it is only Windows 10 playing games with ~5GB of space. Where is it storing what and why?? The clean install has been running for 24hrs, and is still sitting at it's original ~7GB so I'm assuming it isn't the indexing service(s) using up the space. And trying to get a birds eye view with SpaceSniffer didn't yield anything useful in the way of what was using the space either.-Stoic Joker
My guess is that it keeps separate "images" (snapshots) so it can revert to a known working system if an upgrade goes bad.
-Deozaan
I thought of that, but there is nothing I can see. cleanmgr.exe took care of Windows.old and $Windows.~BT, and I checked for shadow copies and file system Previous Versions ... Nothing, nothing, and nothing.
Right now I've got 2 clean loaded 10162 VMs, one pro, one home. Both are sitting at just over the 7GB mark. I'm going to keep a weary eye on them to see if/when one of them starts to bloat, to see if I can figure out why.