COMMAND EVERYTHING.
Creates a new virtual disk in the specified storage pool.
Microsoft Storage reference: Creates a new virtual disk in the specified storage pool. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for New-VirtualDisk. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Windows / Storage · Windows Server 2025 documentation; feature/module prerequisites apply
-AllocationUnitSize- Specifies the allocation unit size to use when create the virtual disk.
-AsJob- Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-AutoNumberOfColumns- Specifies that the number of columns used by the virtual disk should be automatically determined. Columns represent the number of underlying physical disks across which one stripe of data for a virtual disk is written.
-AutoWriteCacheSize- Indicates that the cmdlet sets the size of the write-back cache to 1 GB for all types of storage spaces, which include simple, mirror, and parity, to create from the pool. If the number or size of the solid-state drives (SSDs) or journal disks in the storage pool is not sufficient and you specify a value of $True for this parameter, the cmdlet sets the write-back cache size to 0 for simple and mirror spaces, and to 32 MB for parity spaces.
-CimSession- Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-ColumnIsolation- Specifies at which level columns within a virtual disk should be isolated from each other. We recommend omitting this parameter and using the defaults. The acceptable values for this parameter are: - PhysicalDisk - StorageScaleUnit - StorageChassis - StorageEnclosure - StorageRack
-FaultDomainAwareness- Specifies at what level you want the virtual disk to be fault tolerant. The acceptable values for this parameter are: - PhysicalDisk - StorageScaleUnit - StorageChassis - StorageEnclosure - StorageRack For example, specify StorageScaleUnit to store data copies on separate nodes of a Storage Spaces Direct cluster. This cmdlet refers to nodes of a Storage Spaces Direct cluster as storage scale units because you can expand the scale of the cluster by adding more nodes.
-FriendlyName (required)- Specifies the friendly name for the virtual disk. The friendly name is not required to be unique.
-InputObject (required)- Specifies the input object that is used in a pipeline command.
-Interleave- Specifies the interleave value to use during the creation of a virtual disk. The interleave value represents the number of bytes that is written to a single physical disk. Therefore, Interleave * NumberOfColumns yields the size of one stripe of user data.
-IsEnclosureAware- Specifies that the virtual disk should use enclosure awareness. To support deployments that require an added level of fault tolerance, Storage Spaces can associate each copy of data with a particular just-a-bunch-of-disk (JBOD) enclosure. This capability is known as enclosure awareness. With enclosure awareness, if one enclosure fails or goes offline, the data remains available in one or more alternate enclosures. To use enclosure awareness, you must use JBODs that are certified for use with Storage Spaces and you must have a sufficient number of JBODs and disks to support the resiliency types of the storage spaces you create (generally you'll need three or four JBODs). For a list of certified JBODs, see the Windows Server Catalog. For more information about enclosure awareness, see Storage Spaces Frequently Asked Questions.
-MediaType- Specifies the media type of the storage tier. The cmdlet creates the storage tier for the media type that you specify. The acceptable values for this parameter are: - SSD - SCM - HDD Use SCM for storage-class memory such as NVDIMMs.
-NumberOfColumns- Specifies the number of columns to use when allocating the virtual disk.
-NumberOfDataCopies- Specifies the number of data copies to create. Specify 2 to create a two-way mirror, or 3 to specify a three-way mirror or for dual parity.
-NumberOfGroups- specifies the number of groups used by Local Reconstruction Coding (LRC) with a dual parity virtual disk. We recommend omitting this parameter and using the defaults.
-OtherUsageDescription- Specifies an OtherUsageDescription string for the virtual disk. You can use the *OtherUsageDescription* parameter only if you set the *Usage* parameter to Other or do not include the *Usage* parameter.
-PhysicalDiskRedundancy- Specifies the physical disk redundancy value to use during the creation of a virtual disk. This value represents how many failed physical disks the virtual disk can tolerate without data loss. - For two-way mirror spaces, the virtual disk can tolerate 1 failed physical disk without data loss. - For three-way mirror spaces, the virtual disk can tolerate 2 failed physical disks without data loss. - For single-parity spaces, the virtual disk can tolerate 1 failed physical disk without data loss. - For dual-parity spaces the virtual disk can tolerate 2 failed physical disks without data loss.
-PhysicalDisksToUse- Specifies an array of one or more PhysicalDisk objects. The PhysicalDisk objects represent the specific physical disks on which to create this virtual disk.
-ProvisioningType- Specifies the type of provisioning. The acceptable values for this parameter are:Fixed, or Thin. You must specify Fixed for storage spaces that use storage tiers or a clustered storage pool.
-ReadCacheSize- This parameter is no longer supported.
-ResiliencySettingName- Specifies the resiliency setting, or storage layout, to use for the virtual disk. Acceptable values vary by storage subsystem. Allowed values for the Windows Storage subsystem are: Simple, Mirror, or Parity. By default, when you specify Mirror, Storage Spaces creates a two-way mirror, and when you specify Parity, Storage Spaces creates a single-parity space. To create a three-way mirror space, specify 3 for the *NumberofDataCopies* parameter or 2 for the *PhysicalDiskRedundancy* parameter. To create a dual-parity space, specify 2 for the *PhysicalDiskRedundancy* parameter and Fixed provisioning for the *ProvisioningType* parameter.
-Size- Specifies the size of the virtual disk to create. The default unit is Bytes; to specify a different unit, enter the size followed by one of the following unit values, with no spaces: Bytes, KB, MB, GB, or TB.
-StoragePoolFriendlyName (required)- Specifies the friendly name of the storage pool in which to create the virtual disk. Enter a friendly name, or use wildcard characters to enter a name pattern.
-StoragePoolName (required)- Specifies the name of the storage pool in which to create the virtual disk. Enter the name of the storage pool provided by the Storage Management Provider, or use wildcard characters to enter a name pattern.
-StoragePoolUniqueId (required)- Specifies the ID of the storage pool in which to create the virtual disk Enter an ID or use wildcard characters to enter a pattern.
-StorageTierSizes- Specifies an array of sizes of the storage tiers that you specify for the *StorageTiers* parameter.
-StorageTiers- Specifies an array of storage tiers as a CIMInstance object. The cmdlet adds the storage tiers that you specify to the virtual disk. To obtain a virtual disk object, use the Get-StorageTier cmdlet.
-ThrottleLimit- Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
-Usage- Specifies the intended usage of the virtual disk. You can specify one of the predefined descriptions, or use the default value (Other) and instead use the *OtherUsageDescription* parameter to specify a custom value.
-UseMaximumSize- Creates a virtual disk with the maximum size possible given the available storage pool space and specified parameters.
-WriteCacheSize- Specifies the size of the write-back cache. The cmdlet creates the write-back cache of the size that you specify when the cmdlet creates the virtual disk space. The following describes the behavior of this parameter based on the value that you specify: 1. If you do not specify this parameter, the cmdlet sets the value of the WriteCacheSizeDefault property from the storage pool. 1. The default setting of WriteCacheSizeDefault for a storage pool is Auto, which specifies that Windows Server automatically selects the optimal write-back cache size for your configuration. You can change the value of WriteCacheSizeDefault to a concrete value at any time. 1. The Auto setting for WriteCacheSize functions as follows: 1. If any of the following is true, Auto is set to 1 GB: 1. The storage pool contains at least N drives with enough capacity and you set the *Usage* parameter to Journal. (N = 1 for simple spaces, N = 2 for two-way mirror and single parity, N = 3 for three-way mirror and dual parity) 1. The storage pool contains at least N drives with enough capacity and the media type of the virtual disk is set to SSD (N = 1 for simple spaces, N = 2 for two-way mirror and single parity, N = 3 for three-way mirror and dual parity) 1. Otherwise, Auto is set to 0 (no log) for simple and mirror spaces, and 32 MB for parity spaces. 1. If you specify Auto or 0 (zero) for this parameter and the storage space is not a parity space, the cmdlet verifies that either 3.a.i or 3.a.ii is true. If either 3.a.i or 3.a.ii is not true, you cannot set WriteCacheSize to Auto or 0. 1. The objective of these conditions is to help you avoid scenarios in which you force the creation of a write-back cache in situations that result in slower performance.
Windows with the Storage module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.