New-Partition -UseMaximumSize does not create partition with full available space

%3CLINGO-SUB%20id%3D%22lingo-sub-656258%22%20slang%3D%22en-US%22%3ENew-Partition%20-UseMaximumSize%20does%20not%20create%20partition%20with%20full%20available%20space%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-656258%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20creating%20a%20partition%20with%26nbsp%3BNew-Partition%20-UseMaximumSize%2C%20it%20does%20not%20use%20the%20100%25%20available%20free%20space.%3C%2FP%3E%3CP%3EThere%20seems%20to%20always%20be%26nbsp%3B%3CSPAN%3E1031680%20bytes%20left%2C%20when%20looking%20at%20the%20difference%20between%20these%20values%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Get-PartitionSupportedSize%20-DriveLetter%20E).SizeMax%3C%2FP%3E%3CP%3E64423443968%3C%2FP%3E%3CP%3E(Get-Partition%20-DriveLetter%20E).Size%3C%2FP%3E%3CP%3E64422412288%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20when%20creating%20the%20partition%20with%20a%20specific%20size%2C%20for%20example%2010GB%2C%20and%20afterwards%20extending%20it%20using%20Resize-Partition%20-DriveLetter%20E%20-Size%2064423443968%20(value%20from%20SizeMax)%2C%20then%20it%20is%20fully%20used%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E(Get-Partition%20-DriveLetter%20E).Size%3CBR%20%2F%3E64423443968%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIs%20there%20a%20reason%20why%20the%20partition%20is%20created%20with%20a%20size%20of%26nbsp%3B1031680%20bytes%20less%2C%20when%20the%26nbsp%3BUseMaximumSize%20parameter%20is%20passed%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThis%20causes%20problems%20because%20when%20resizing%20this%20partition%20afterwards%2C%20without%20actually%20having%20the%20disk%20resized%2C%20an%20error%20is%20returned%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3EThe%20size%20of%20the%20extent%20is%20less%20than%20the%20minimum%20of%201MB%3C%2FPRE%3E%3CP%3E%3CSPAN%3EWhich%20is%20correct%2C%201031680%20bytes%20%3D%201007%2C5%20KB.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20tested%20this%20on%20a%20Windows%20Server%202019%20on%20VMWare%206.7.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-656258%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECommunity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Frequent Visitor

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

64423443968

(Get-Partition -DriveLetter E).Size

64422412288

 

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).Size
64423443968

 

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.

 

0 Replies