Skip to content
AS

Virtual Machine Recovery

Beyond VMware, AS recovers virtual disks and guest data across Hyper-V, Proxmox, KVM and Citrix, including checkpoint and differencing-disk chains.

When you need this

  • VHDX or QCOW2 file corrupted or won't mount
  • Checkpoint or differencing chain broken after failed merge
  • VM deleted from the host
  • Host storage failure (ReFS, Storage Spaces, ZFS, LVM)
  • Ransomware encryption of host or guest volumes

What we do

Virtual disk recovery

VHD, VHDX, QCOW2, VDI and raw images are recovered or repaired, including chain reconstruction.

Host storage recovery

ReFS, Storage Spaces, ZFS and LVM layers are recovered to expose virtual disks after host failure.

Guest data extraction

Files, databases and applications are recovered from inside virtual disks when the VM itself can't be restored.

How it works

  1. Step 1

    Consultation and scope

    We establish what failed, what has been tried, and which data matters most. This shapes a targeted plan rather than a generic one.

  2. Step 2

    Secure imaging and diagnosis

    Where possible the source media is imaged before any work, so the original is never altered. Diagnosis then determines the safest recovery method.

  3. Step 3

    Recovery

    Data is extracted from the image or source using methods matched to the failure — logical, structural or hardware-level as required.

  4. Step 4

    Verification

    Recovered data is checked for integrity and completeness, and a file list is shared so you can confirm what matters is there.

  5. Step 5

    Secure delivery

    Verified data is returned through an agreed secure method, with guidance on validation before it goes back into production.

What affects the outcome

Outcomes are never guaranteed. Every case is assessed on its own condition, and we tell you what is realistic before you commit.

  • Physical condition of the media and the extent of any damage
  • Whether the media has been written to, reformatted or re-initialised since the failure
  • Encryption, corruption or partial overwriting of the data
  • Availability of source data such as images, backups, logs or transaction records
  • Attempts made before assessment (rebuilds, repair tools, repeated reboots)

Frequently asked questions

A failed checkpoint merge left our VM unbootable. Can you help?

Usually. Chain analysis identifies which differencing disks hold valid data and allows a consistent virtual disk to be rebuilt.

Do you support Proxmox and KVM?

Yes, including QCOW2 and raw disks on LVM, ZFS and Ceph-backed storage where the underlying storage is readable.

Request assessmentEmergency