Inspect before you export
The evaluation lets you scan and review the result. A license is needed to save recovered content to a separate healthy destination.
VHD Recovery and VHDX Data Recovery Software: DiskInternals VHDX Recovery
Recover the container itself or files from inside it when:
- Deleted
- Missing
- Corrupted
- Damaged
What this recovers: a deleted or missing VHD/VHDX container when its source data remains readable and has not been overwritten; a corrupted or damaged container when recoverable data remains; or selected guest files from a scanned container.
The software scans the affected source and builds a result you can inspect in the application. A visible result does not guarantee that every file is intact.
-
Evaluate the affected sourceDeleted, missing, corrupted, or damaged containers can be scanned when the source remains readable.
-
Two distinct outcomesRecover the damaged or corrupted container itself, or browse and select guest files inside it.
-
Export away from the sourceThe software retrieves data without an in-place repair.
You then choose what to export to a separate healthy destination.
Safe start
- Stop writing to the affected source before scanning. Do not format, initialize, repartition, run CHKDSK, or attempt an in-place repair.
- Install the software on a healthy drive. Prepare a separate healthy destination with enough free space for the recovered data.
- Watch for physical failure. If the drive clicks, disconnects, or becomes unstable, stop software attempts. See source protection before scanning.
- Platform
- Windows
- Privileges
- Administrator, when raw physical-drive access is needed
- Install target
- Healthy drive, including USB
- Output
- Separate healthy destination
Built on the DiskInternals Recovery Engine
DiskInternals VHDX Recovery brings together the DiskInternals recovery engine, VHD and VHDX container handling, and a guided disk recovery wizard. The wizard takes you through source selection, scanning, result inspection, and export.
- Foundations
- Shared DiskInternals engine
- Source
- Unchanged
- Container handling
- VHD & VHDX
- Workflow
- Guided wizard
Each Product Contains the One Below It
The recovery products are layered rather than parallel. A higher-level product includes the complete functionality of every product beneath it and adds one further class of problem on top. Choosing a product means choosing the highest layer your case actually requires — nothing from the lower layers is lost.
- Layer 5VMFS Recovery
Adds VMware datastores: VMFS3 through VMFS6, ESX/ESXi storage, VMFS metadata, VMDK descriptor and snapshot-chain problems.
- Layer 4RAID Recovery
Adds reconstruction of the array itself: unknown parameters, missing member order, a failed controller, unavailable member disks, an interrupted rebuild.
- Layer 3Partition Recovery
Adds the partition layer: lost, deleted, formatted, RAW, inaccessible, corrupted, and damaged partitions; partition-table, MBR, GPT, and boot-sector analysis; ReFS and Ext2/3/4 sources; disk images; remote Ext2/3/4 over SFTP.
- Layer 2DiskInternals VHDX RecoveryThis product
Adds VHD/VHDX container recovery and recovery of files inside those containers.
- Layer 1Uneraser
Base deleted-file recovery on a file system that Windows can still read. Available inside Partition Recovery as the Fast recovery depth.
For physical-disk or partition problems, choose the broader Partition Recovery product. If the affected volume lives inside a failed array or a VMware datastore, choose RAID Recovery or VMFS Recovery for those storage layers.
Choose the Recovery Outcome and Safe Next Step
First identify what you need back. Both paths begin with source protection, before any scan.
| Source condition | Recovery object | Safe next step | Output and boundary |
|---|---|---|---|
| VHD/VHDX container is deleted, missing, corrupted, or damaged | The container itself | Protect the source, then scan and inspect the container result | Recovery depends on readable, non-overwritten data. Export only to a separate healthy destination. This does not repair the original or promise a bootable VM. |
| You need selected files inside a VHD/VHDX container | Guest files and folders | Protect the source, scan the container, then browse the guest file tree | Select recoverable files for export to a separate healthy destination. This does not restore a complete VM. |
If the physical source is unstable, stop software attempts. A container that does not open may still be worth evaluating; it is not proof that its data is readable.
If an existing VHD or VHDX will not attach or open, use the VHDX repair guide to identify the affected object and choose a safe next step.
Container recovery
If the container was deleted, protect the physical drive that held it from new writes before scanning. The recovered file is a result, not an in-place repair.
Selected guest-file recovery
If the container is accessible, select it as the source, then browse the guest tree to choose individual files or folders.
Scan and Preview Recoverable Files for Free
Use the free evaluation to scan a supported VHD/VHDX source, inspect the scanned container result or browse the recovered guest tree, and preview supported results. Inspection helps you judge what was found; a preview applies only to the item shown and does not prove every result is complete or will export successfully. Saving or exporting recovered data requires a license. See pricing before export.
When a License Is Required to Export Files
A license is required to save or export recovered data. The read-only result drive in Windows Explorer is available after licensing. A preview confirms only the item shown; it does not guarantee that every file is complete or that export will succeed.
Free in the evaluation
- Scan an accessible supported VHD/VHDX source
- Review the container result or found guest folders
- Preview supported guest-file results
Requires a license
- Save or export recovered container data or selected guest files
- Browse available recovery results through the read-only virtual drive in Windows Explorer
What You Can Do Before Purchase
Before purchase, you can:
- Select an accessible supported VHD/VHDX source.
- Scan the guest file system when source data remains readable.
- Review the container result, browse found guest folders, and preview supported files.
- Check several representative files from the folders that matter most.
A successful preview confirms only the condition of the specific file opened. It does not prove that every file is complete or recoverable.
How DiskInternals Protects the Source Drive
The recovery workflow separates the affected VHD/VHDX container and the physical host drive that may hold it, the virtual recovery result, and the export destination. The software reads its selected source without writing changes or repairing the original in place.
The Source Drive Is Never Modified
The selected source may be the VHD/VHDX container or the physical host drive that holds a deleted container. The scan reads that source without formatting, initializing, repartitioning, or using write-capable repairs. A reconstructed result appears inside the application; the original container and its guest file system are not rewritten in place.
Prepare a healthy output location
Install the software on a healthy drive, never on the affected source. A healthy USB drive is an option for installation when needed. Prepare a physically separate healthy destination with enough free space for the data you select. Administrator rights are required when the workflow needs raw physical-drive access.
The software does not:
- format or initialize the selected source;
- create, delete, resize, or rewrite host-drive partitions;
- run CHKDSK or another write-capable repair on the original;
- rewrite the original VHD/VHDX container or guest file system;
- write reconstructed data or recovered files back to the selected source.
Affected source — unchanged
The VHD/VHDX container, or the physical drive that held a deleted one, is scanned without formatting, repairing, or writing changes.
Virtual recovery result
Readable container or guest-file structures are reconstructed for inspection inside DiskInternals VHDX Recovery. The original source is unchanged.
Export to another healthy destination
Selected files are saved to a healthy, physically separate device with enough free space, after licensing.
The File System Is Reconstructed Virtually
The software uses structures and data that remain readable to build a browsable guest-file result inside the application, without changing the original container or host file system. A visible result does not guarantee that every file is intact or that a complete virtual machine can be restored.
Browse and Copy from a Virtual Drive
After licensing, browse available recovery results through the read-only virtual drive in Windows Explorer and copy selected files to another healthy, physically separate destination. This is the application's recovery result; mounting the original VHD/VHDX in Windows is a separate task.
Safety Rules Before You Start
- Stop normal use of the affected host source and stop virtual-machine writes to the affected image before scanning.
- Do not format, initialize, or repartition the source; do not run CHKDSK or another write-capable repair tool.
- Do not repair or merge checkpoints on the affected original VHD/VHDX container.
- Install the software on a healthy drive, not on the affected source.
- Do not save recovered data to the source or another partition on the same affected physical drive.
- Prepare a healthy destination on physically separate storage with enough free space.
Stop software attempts if the physical source clicks, repeatedly disconnects, overheats, is detected inconsistently, or shows severe read instability. Further reads can make a failing drive worse. Seek a hardware-safe data recovery specialist instead of repeating the scan.
Recover Data Through the Guided VHDX Workflow
Start only after completing the source checks. Follow the screens from source selection through inspection and separate output.
Choose the workflow for the recovery object you need:
Recover a Deleted or Missing VHD/VHDX Container File
Recover the VHD/VHDX as an ordinary file from the storage that held it. A deleted container cannot be selected in the Mount Image dialog. Complete the source checks before scanning.
Select the Host Storage
Run the evaluation from a healthy drive. Select the storage that held the missing VHD/VHDX file and use Open as Uneraser or Open as Recovery for ordinary-file recovery. Keep installation files and recovered output off that source. Stop if the physical source becomes unstable.
Find the VHD or VHDX File
Scan the selected host storage and locate the VHD/VHDX file in the recovery results. Here, the recovery object is the container file itself, not files inside the virtual disk. Recovery depends on readable data that has not been overwritten.
Review and Select the Found Container
Review the found file entry and select the container you need. Finding an entry does not prove that the whole container is intact or that its virtual machine will start. This step does not require mounting a deleted container.
Export the Container to Separate Healthy Storage
Use Export to save the selected VHD/VHDX file to healthy, physically separate storage with enough free space. A paid license is required. Do not save to the affected source or another partition on the same physical drive. The output is the recovered container file; its completeness and usability need a separate check before use.
Recover Files Inside an Existing VHD/VHDX
This route requires an accessible VHD/VHDX container. It covers files inside the virtual disk, not recovery of a deleted host container file.
Launch the Evaluation and Select the Source
Launch the evaluation from a healthy drive, keeping installation files and output off the affected source. Select an accessible, existing VHD/VHDX container in the mount dialog. Confirm what you selected before scanning.
Confirm the Disk in the Interface
After mounting the existing VHD/VHDX container, confirm that it appears as a disk in the main window before continuing with guest-file recovery.
Start the Guided Recovery Wizard
Start the Disk Recovery Wizard and select the intended disk to scan.
Review the File-System Selection Screen
Review the wizard's file-system selection screen before the scan starts.
Run the Scan, Then Inspect the Result
Run the scan and stop if the physical source develops any of the warning signs described in source protection. When scanning finishes, continue to the recovered result.
Inspect the Guest Files and Select What You Need
Inspect the recovered guest tree and the files you need before you pay, then select the guest files or folders you want to export. This step is for contents inside the existing container, not recovery of the container file itself.
Choose a Separate Destination and Complete Licensed Guest-File Export
Choose Save Files, set a folder on a separate healthy drive, then review the selected guest-file list. Never save to the source or another partition on the same affected drive. A license is required to complete the guest-file export; the registration screen marks that transition and does not guarantee a successful export.
VHD and VHDX Sources and Recovery Results
VHD and VHDX containers are the scope of this product page. It does not promise recovery for other virtual-disk formats.
A physical drive holds the container file; the container holds the guest file tree. For a deleted container, scanning may start at the host drive. If a readable working copy exists on healthy media, use it to spare the affected source. The application builds a browsable result without writing guest structures back to the container.
Compatibility, Requirements, and Limits
DiskInternals VHDX Recovery runs on Windows. Raw physical-drive access may require administrator rights. Recovery depends on source data that remains readable and has not been overwritten.
The product does not repair a VHD/VHDX container or guest structure in place. It does not rewrite the source or a partition table, convert or resize the container, merge checkpoints, or restore a complete bootable virtual machine. BitLocker and EFS recovery are outside this product's scope.
For a damaged or unreadable container, see how to assess a damaged VHDX safely. The guide separates data recovery from repair of the original and restoration of a bootable VM.
If a Scan or Export Does Not Go as Expected
| Situation | Check | Next safe action |
|---|---|---|
| A scan is slow or seems stalled | Is the source still detected consistently? | If the physical source is stable, allow the scan to continue. Otherwise, follow source protection. |
| Expected files are missing | Did you select the intended source and recovery object? | Review the scanned result. Data that is unreadable or overwritten may not be recoverable. |
| An inspected item differs from its export | Did you select the intended items and destination? | Check the specific result again. Inspection is useful evidence, not a guarantee that every exported item is intact. |
| The physical source becomes unstable | Does it show any of the physical stop signals? | Stop software attempts and seek a hardware-safe specialist. |
VHDX Recovery Pricing
Scan and inspect the container result or selected guest files for free. Purchase a license to save or export recovered data. All prices below are in USD.
| License | Price |
|---|---|
| Free Evaluation | $0 |
| Personal | $99.95 |
| Business | $149.95 |
| Professional | Contact us |
For Professional licensing, tell us how you plan to use VHDX Recovery so we can discuss your requirements.
VHD and VHDX Recovery FAQ
-
Choose container recovery for the VHD/VHDX file itself, or guest-file recovery for selected contents. Neither restores a complete VM.
-
Yes, if the underlying data remains readable and has not been overwritten. Protect the host drive first.
-
No. It reads the source and builds an in-app result; export goes to a separate healthy destination. See source protection.
-
Saving to the source could overwrite recoverable data. Use a healthy drive with enough free space.
-
No. The product recovers data from what remains readable. It does not repair the original container or guest structure in place, convert or resize the virtual disk, or promise a bootable VM. See the VHDX repair decision guide for symptom-based next steps.
-
Scan and inspect the result; saving or exporting requires a license. See pricing.
-
For a physical disk or partition problem rather than a VHD/VHDX container case, use the parent-product route above.
-
No. BitLocker and EFS recovery are outside its scope.
-
When the recovery task needs raw access to a physical drive. Install the software on a healthy drive; a healthy USB drive is an option when needed.
-
Stop software attempts and seek a hardware-safe specialist if you see the physical stop signals.
Choose the Next Safe Step
The source is stable and consistently detected
Download the evaluation version to a healthy drive. Scan the affected source in read-only mode, inspect the container result and guest folders, and preview supported files you need.
The required data has been found and inspected
Purchase a license to save the container or selected guest files. Enter the license key without reinstalling the software or repeating the scan.
The source shows signs of physical failure
Stop scanning if the physical host drive clicks, disconnects, overheats severely, disappears, or develops rapidly increasing read errors — contact a data-recovery specialist when the device is physically unstable or the data is irreplaceable.
Install on a healthy drive. Export only to a healthy, physically separate destination with enough free space.
DiskInternals keeps the original source unchanged throughout the software recovery workflow. Licensed export saves the container or selected guest files to another healthy, physically separate destination with sufficient free space.