Convert VHD to VHDX Using Hyper-V Manager and PowerShell
Picked the old format, or inherited a disk that needs to move? Conversion is a safe, offline copy operation built into Hyper-V - the original stays untouched until you delete it. Here is the full routine, wizard and PowerShell, with the checks that keep it boring.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 7 minute read
🎥 Watch the video for the basics of creating and attaching disks - conversion builds directly on them
Formats are not forever. A VHD created for old software can become a VHDX for a modern Hyper-V host, and a VHDX can go back to VHD for Azure or an older tool. Windows ships the converter inside Hyper-V: the Edit Disk wizard for clicking, Convert-VHD for scripting. Both work the same way under the hood - read the old disk, write a brand-new file, change nothing in the original. That design is what makes the operation safe, provided you respect its one rule: the disk must be offline.
Old file afterwards - unchanged, still usableSafety net
New file - same contents, new formatVerify first
Delete the old file only after the new one boots or mounts cleanlyDiscipline
👆 Conversion writes a new file and leaves the old one alone. Your rollback plan is simply: do not delete anything until the new disk has proven itself.
1
Before You Convert - Four Checks
The disk must be offline: shut down the virtual machine that uses it, or detach it if it is mounted. Conversion of a live disk is refused - and anything that forces it would corrupt data
Free space: the new file is a second full copy. A fixed destination needs its whole declared size free on the host; a dynamic one needs room for the data it holds. Check before you start, not during
Going VHDX to VHD? The result must fit the VHD ceiling of 2,040 GB. A larger VHDX cannot become a VHD, full stop
Hyper-V must be available: both the wizard and the cmdlet come with the Hyper-V role or management tools. On a Windows edition without Hyper-V, do the conversion on a machine that has it - Disk Management alone cannot convert
2
Route One - The Hyper-V Edit Disk Wizard
Open Hyper-V Manager and click Edit Disk in the Actions pane
Browse to the source .vhd or .vhdx file and click Next
Choose Convert as the action
Pick the destination format - VHDX or VHD
Pick the type - Fixed size or Dynamically expanding. Conversion is also your chance to change type; many people convert an old dynamic VHD into a fixed VHDX in this single pass
Give the new file a name and location, review the summary, and click Finish. Large disks take real time - the wizard is copying every block
3
Route Two - PowerShell Convert-VHD
Open PowerShell as administrator on a machine with the Hyper-V module
VHD to VHDX: Convert-VHD -Path "D:\VM\OldDisk.vhd" -DestinationPath "D:\VM\NewDisk.vhdx" -VHDType Dynamic
VHDX back to VHD (for Azure or an old tool): Convert-VHD -Path "D:\VM\Disk.vhdx" -DestinationPath "D:\VM\Disk.vhd" -VHDType Fixed
Use -VHDType Fixed when the destination disk will do busy production work, Dynamic when host space matters more
The cmdlet reports progress and errors; a silent success leaves the new file ready in the destination path, original untouched
4
After Conversion - Verify, Rewire, Then Clean Up
Inspect the new file:Get-VHD -Path "D:\VM\NewDisk.vhdx" reports its format, type, and sizes - confirm they match the plan
Test it: mount it read-only and browse, or attach it to the VM and boot. For a data disk, a read-only mount plus opening a few files is a solid check
Rewire the VM: converting does not update any virtual machine's settings - open the VM's settings and point its hard disk at the new file yourself. Forgetting this is the classic 'conversion did nothing' moment; the VM calmly keeps using the old disk
Keep the original until the new disk has survived real use - a day of work, a full backup cycle, whatever fits the stakes
Only then delete the old file, and note that any snapshots or differencing children tied to the old disk belong to the old disk - they do not follow the conversion
🔴 Know your disk family before converting. Converting a differencing child produces a standalone full disk, but its parent and any sibling children stay behind - unchanged, and still dependent on each other. Map the whole chain before converting any member of it, or you can strand disks that other machines still need.
🎥 Watch the Complete Process in the Video
Watch the video to get comfortable creating and attaching disks first - conversion is the natural next skill once those feel routine.
No - conversion is a block-by-block copy into a new file. The contents, partitions and files are identical, and the original file is not modified at all. The realistic risks are operational, not technical: converting the wrong file, or deleting the original before verifying the new disk. Verify first, delete later, and the operation is one of the safest in disk management.
I converted the disk but my VM still uses the old format. Why?
Because conversion creates a new file; it does not edit your virtual machine's configuration. The VM keeps pointing at the old path until you change it. Open the VM's Settings, select the hard drive, browse to the converted file, and save. On the next boot the VM uses the new disk - and the old file can be retired after a successful test.
Can I convert a disk while its virtual machine is running?
No. Conversion needs the disk completely offline: VM powered off (not saved, not paused) or the container detached. Hyper-V refuses to convert a disk in use, and that refusal is protecting you - copying a disk that is changing underneath the copy would produce a torn, unreliable result.
This guide is based on the Technical Anshu Windows VHD video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏