When you create a virtual hard disk in Hyper-V, you choose from three disk types. A fixed disk reserves the full storage size at creation, which gives steady performance but uses the space immediately. A dynamically expanding disk starts small and grows as data is written, saving storage space until it is needed. A differencing disk records only the changes made from a parent disk, making it useful when multiple virtual machines share a common base image. You can create these disks using the Hyper-V Manager graphical interface or with PowerShell cmdlets such as New-VHD. Each type fits a different scenario, so the choice depends on whether you prioritize performance, storage efficiency, or shared baselines.
A decision tree that branches based on whether the priority is performance, storage efficiency, or shared baselines to choose between fixed, dynamically expanding, or differencing virtual hard disks.
Hyper-V supports two virtual hard disk formats: VHD and VHDX. VHD is older and has a maximum size of 2 TB, while VHDX supports up to 64 TB and adds better protection against data corruption. You may need to convert a disk from one format to the other to gain the larger capacity or the newer features. Use the PowerShell cmdlet Convert-VHD and specify the source file and the destination format. The conversion does not change the data inside the disk, only the container format, so you can upgrade existing disks without rebuilding the virtual machine.
You can increase the size of a virtual hard disk either while the virtual machine is running (online) or after it is stopped (offline). Expanding the disk adds storage space without losing existing data, so it is a common way to meet growing capacity needs. Shrinking a disk is generally not supported because it risks data loss and can break the disk’s internal structure. To resize a disk, use the Resize-VHD PowerShell cmdlet and provide the new size. Online resizing minimizes downtime, making it the preferred choice when the virtual machine must stay available.
To get the best disk I/O performance from your virtual machines, you must check partition alignment and interleave settings. Partition alignment ensures that the logical partitions line up correctly with the physical disk sectors; misalignment can cause a noticeable slowdown. For striped volumes, the interleave size should typically be set to 64 KB to match common performance best practices. Regularly analyzing storage performance helps you spot bottlenecks and adjust the disk configuration before it affects the virtual machine’s workload. Proper alignment and sizing keep the storage layer efficient in both on-premises and hybrid Azure environments.
Eager to master hybrid server management? Discover how to administer Windows Server Hybrid Core Infrastructure on Azure, setting your path towards the Microsoft Certified: Azure Hybrid Infrastructure Administrator Associate certification!
Prepare and test your skills

Prepare and test your skills

VHD is an older format with a maximum size of 2 TB, whereas VHDX supports up to 64 TB and provides better protection against data corruption. Disks can be converted between the two container formats using the Convert-VHD PowerShell cmdlet without altering the underlying data.
A fixed disk allocates its full storage capacity immediately at creation to deliver steady performance, while a dynamically expanding disk grows incrementally as data is written to conserve storage. A differencing disk records only the changes made relative to a parent disk, allowing multiple virtual machines to share a common baseline image.
Yes, virtual hard disks can be expanded online while the virtual machine is running to minimize downtime, or offline after the virtual machine is stopped. Expanding disk capacity is performed using the Resize-VHD PowerShell cmdlet, whereas shrinking disks is generally not supported due to the risk of data loss.