al-dot

A final comment (feature request?) It seems the "default" setting in the VC volume creation wizard isn't VC setting the value, but VC deferring to windows to choose the size? That isn't clear from the interface, and not the expected behaviour for a "default" setting in an app. Also, it would be nice if the UI showed the alloc unit size of mounted volumes, in the listbox and/or in the "volume properties" dlg. But yes, right at the bottom of the priority queue...

Ah. Much obliged @RichardH - a change in the default allocation unit size is exactly what's going on here. Finding the allocation unit size of a VC volume is quite opaque (my searches only turn up solutions for physical disks - but maybe that's just my search skill). Doesn't matter. To test, I've made another volume and set the alloc unit size to 1 kB. The same file contents on that volume take just 27.4 GB - less than the original. So that's QED.

Try this Powershell command for both containers: (Get-Volume -DriveLetter E).AllocationUnitSize (with the 'E' replaced with the appropriate drive-letter) Get-Volume doesn't find or show mounted VC volumes. (Neither does windows disk manager). I've just created and mounted a tiny NTFS volume to test, and it doesn't show up either. I don't know if this is some odd setting of my OS I don't know about, or true for windows 10 pro in general. In any case, the allocation unit size for all the VC containers...

Hi folks, (( Just signed up; first post here. Big thanks to maintainers and contributers for VeraCrypt. )) I have a 3 year old VeraCrypt container (32 GB) that is running out of space, so I created a new larger VeraCrypt container (40 GB) to replace it, mounted both volumes, and copied the entire contents from old to new. I've done this with various containers in the past and never had an issue, or been surprised by the result. This time, after the copy, the 40 GB volume has LESS free space than...