AS VMware Recovery — VMware VMDK Recovery Software

It repairs what most often makes a VMDK unusable. To repair a VMDK file with an empty or damaged descriptor, the descriptor is rebuilt from the -flat, -sNNN or -delta data file; broken partition tables and boot sectors inside the disk are restored from their backup copies. The files are then recovered from the disk.

For ESXi data recovery, copy the VMDK files off the datastore and open them in the program. It works on VMDK files you still have. To recover a deleted VMDK from a VMFS datastore is not something this program does yet: that is laboratory work, so contact us before anything else is written to the datastore.

Yes. For VHDX recovery the VHD, VHDX and AVHDX files are opened directly with their checkpoint chains, and files are recovered from inside. A disk can be saved as one raw image with its checkpoints merged, which is a practical way to finish an AVHDX merge that Hyper-V refuses.

To repair a VHDX file that will not mount, open it in the free edition: partitions and the file table are restored from their backup copies where possible and the files are listed. To recover a deleted VHDX, the file must first be found on the host's disk: AS Data Recovery can scan that drive for deleted files, or send the case to our laboratory.

No. Copy the virtual disk files (the .vmdk and -flat.vmdk, or the .vhdx and .avhdx files) to a Windows PC and open them in the program, or open the virtual machine's folder.

Yes. The program lists every point in time in the snapshot chain. Open the disk as of the older snapshot: files that existed then are read exactly as they were, even if they were deleted or changed later.

Yes. Open the descriptor (or the -flat.vmdk). The program rebuilds the descriptor from the data file, opens the disk, and can save the repaired descriptor so VMware can use the disk again.

When ransomware encrypted only the start of a virtual disk (a common pattern), the partitions come back from the backup GPT table and backup boot sectors, and the files from the rest of the disk. Data that was itself encrypted cannot be read by any software without the key.

Yes. A flat VMDK is a raw image of the disk, so the program reads it by its content whatever its name. Copy the encrypted -flat.vmdk off the datastore, keep the original untouched, and open the copy in the free edition: the scan shows which partitions and files are still readable.

Then the files whose data lay in the encrypted stripes are damaged or lost; the rest is read normally. The free scan shows how much is affected before you buy. For large disks where the file table itself was hit, our VMware recovery service can rebuild more by hand.

Often in large part. When only the guest disk inside the VHDX was damaged, the program restores the partitions from their backup copies and reads the file table from its mirror, as with a VMDK. When the VHDX header and block table at the very start of the file were encrypted, Hyper-V and Windows can no longer open the file and the disk has to be rebuilt from its data blocks first; that is laboratory work by our Hyper-V recovery service. The free scan shows whether the program can open your file directly.

Not in this version. Copy the VM files out of the datastore with ESXi first. For a damaged VMFS datastore or SEsparse snapshots, use our VMware recovery service.

Your licence key (ASVM-…) arrives by e-mail and in your account. In the program open Licence, enter the key under Activate online and click Activate.