Virtual Hard Disk v2
Virtual MachinesVHDX differs from VHD. A reader’s container support does not establish support for the contained filesystem/encryption. Review parents/checkpoints and the desired current state as a complete set.
- What it is used for
- Virtual-disk storage for Hyper-V and compatible tools
- What the file contains
- Binary data
All sections, questions and sources
Content reviewed： · Editor：Kai
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- Old reader fails: check VHDX support.
- Contents unreadable: review filesystem/encryption requirements.
- Recent changes absent: establish the current checkpoint/difference state.
- VHD conversion limit: inspect destination constraints/source capacity.
- Attached during conversion: inspect host mount as well as VM use.
- Host size unchanged: inspect allocation and supported optimization.
VHDX → supported VHD or other disk format
- Review the stopped image set and select supported offline conversion.
- Check target capacity/features and validate data/VM compatibility.
- Verify target limits and the state represented by the output.
Target formats may not express the same capacity/features; distinguish container conversion from full checkpoint migration.
Base image versus current state
Inspect VM attachments/checkpoints rather than inferring state from the suffix.
Example: inspect managed current state when differencing files accompany VHDX.
Source for these steps：Microsoft · Convert-VHD / Microsoft · Mount-DiskImage / Microsoft · Hyper-V checkpoints
Create a migration test copy
Use supported state capture and offline conversion, then validate capacity, data and boot conditions.
Source for these steps：Microsoft · Convert-VHD / Microsoft · Mount-DiskImage / Microsoft · Hyper-V checkpoints
Related-format differences
| Format / method | Role | What to verify |
|---|---|---|
| VHDX | Virtual disk | Active attachment/parent |
| AVHDX | Differencing data | Managed workflow |
| VHD | Older format target | Capacity/compatibility |
Handling and security
Stop the VM and preserve originals/parents. Disks may contain credentials or deleted data; avoid public converters and shared host connections for unknown guests.
Questions and answers
Does VHD support imply VHDX support?
Check the reader’s supported formats.
Does unreadable mean empty?
Encryption or unsupported filesystems are possible.
Are all checkpoints contained?
Establish related differences/configuration.
May I delete an AVHDX file?
It may be checkpoint data; use supported management/merge workflows.
Does the base VHDX contain the latest state?
Active deltas may hold newer changes; inspect the complete current state.
Format facts: name, steward and MIME type
- Formal name
- Virtual Hard Disk v2
- Steward / specification
- Microsoft
- MIME type
- Depends on the producer or server; an extension alone does not establish a MIME type.
Primary and official sources
- Platform documentationConvert-VHD
Reference for offline VHD/VHDX conversion.
Microsoft · Link checked： - Platform documentationMount-DiskImage
Reference for supported Windows disk-image mounting.
Microsoft · Link checked： - Official documentationHyper-V checkpoints
Checkpoint types, management and merging.
Microsoft · Link checked：