May 29 2019
When creating a partition with New-Partition -UseMaximumSize, it does not use the 100% available free space.
There seems to always be 1031680 bytes left, when looking at the difference between these values:
(Get-PartitionSupportedSize -DriveLetter E).SizeMax
(Get-Partition -DriveLetter E).Size
But when creating the partition with a specific size, for example 10GB, and afterwards extending it using Resize-Partition -DriveLetter E -Size 64423443968 (value from SizeMax), then it is fully used:
(Get-Partition -DriveLetter E).Size64423443968
Is there a reason why the partition is created with a size of 1031680 bytes less, when the UseMaximumSize parameter is passed?
This causes problems because when resizing this partition afterwards, without actually having the disk resized, an error is returned:
The size of the extent is less than the minimum of 1MB
Which is correct, 1031680 bytes = 1007,5 KB.
I tested this on a Windows Server 2019 on VMWare 6.7.