This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 21%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I have the same issue with Storage Spaces as the person who posted a question here on March 5th.
In an administrative PowerShell console, when I issue the below command:
New-VirtualDisk -StoragePoolFriendlyName "Storage pool" -FriendlyName "StoragePool" -NumberOfColumns 4 -Interleave 32KB -ResiliencySettingName Parity -UseMaximumSize
I get the following error:
New-VirtualDisk : Not Supported
Activity ID: {6ec5fb66-7faa-000e-0dce-c76eaa7fdb01}
At line:1 char:1
+ New-VirtualDisk -StoragePoolFriendlyName "Storage pool" -FriendlyName ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (StorageWMI:ROOT/Microsoft/...SFT_StoragePool) [New-VirtualDisk], CimException
+ FullyQualifiedErrorId : StorageWMI 1,New-VirtualDisk
I'm trying to create the new Storage Space because I want to create a custom interleave size.
Has anyone else experienced this issue or found a workaround?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 72%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
I've encountered the same error in Windows Server 2025, with five 2TB HDDs in a pool, trying to use single parity configuration.
The following command fails:
New-VirtualDisk -StoragePoolFriendlyName "HDDpool" -FriendlyName "HDDParity" -Size 7444GB -ResiliencySettingName Parity -ProvisioningType Fixed -Interleave 16KB -NumberOfColumns 5
But this one works:
New-VirtualDisk -StoragePoolFriendlyName "HDDpool" -FriendlyName "HDDParity" -Size 7444GB -ResiliencySettingName Parity -ProvisioningType Fixed -Interleave 64KB -NumberOfColumns 5
This also works:
New-VirtualDisk -StoragePoolFriendlyName "HDDpool" -FriendlyName "HDDParity" -Size 7444GB -ResiliencySettingName Parity -ProvisioningType Thin -Interleave 16KB -NumberOfColumns 5
So it would appear the minimum acceptable interleave size for thin provisioning is 16KB and for fixed provisioning it is 64KB. The question is why.
I have a lot of small files so prefer smaller interleave and stripe sizes. An interleave size of 8KB would be ideal, but specifying this size in the powershell command always fails, regardless of provisioning type.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
What is the configuration of the storage pool? NumberOfColumns should be less than or equal to the number of physical disks. You can use the Get-StoragePool cmdlet to check the status of the storage pool.
Also use the Get-PhysicalDisk cmdlet to check the status of the physical. Ensure that the disks are healthy and properly attached.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.
