XRecovery supports reading and searching files in supported VHD, VHDX, VMDK, and EDISK virtual-disk images. Start with a complete, consistent image and preserve the original before scanning or exporting. A supported extension does not mean that an incomplete snapshot chain, encrypted guest volume, or damaged container can be read without its required components.
Determine what your image actually contains
A virtual-disk file represents storage presented to a virtual machine or another virtual-disk consumer. It is different from a complete virtual-machine backup containing configuration, memory state, snapshots, and multiple disks.
Record the image’s creator, format, virtual capacity, host-file location, and whether it is a standalone disk or part of a larger set. A small host file can represent a larger dynamically allocated virtual disk; its host-file size alone does not describe how much guest storage it presents.
If the virtual machine is still running, use a platform-supported backup process designed to capture a consistent state before recovery work. Copying an actively changing disk file without understanding its state can provide an inconsistent input.
Preserve dependencies before choosing a file
Differencing and snapshot disks may depend on parent images. Microsoft’s VHD overview explains the parent-and-changes relationship. The newest-looking file may contain only changes, while the base file alone may describe an older state.
Keep the complete original set and its directory relationships. Do not delete, rename, merge, or rebase the only snapshot chain in an attempt to make one file open. If a standalone copy is needed, use the creating platform’s documented process on protected copies and verify the resulting state.
Likewise, a split virtual disk can require a descriptor and several extent files, each holding part of the virtual disk. Opening one similarly named fragment is not equivalent to opening the complete virtual disk. A format label does not establish that every variant is independently readable.
Open the appropriate image source
With a suitable preserved source available, use XRecovery’s virtual-image recovery workflow to select it. Confirm the virtual disk identity and capacity, then examine the contained partitions or volumes.
Select the guest volume that actually held the lost files. A virtual disk can contain system, recovery, and data partitions. Finding a Windows directory does not mean you have selected the volume containing your project data.
For an encrypted guest volume, valid credentials remain necessary. Copying the image or scanning it with another program does not remove encryption. Keep credentials in your approved secure process rather than in recovery filenames or ordinary support attachments.
Scan the selected image and export elsewhere
After the image and required dependencies can be read, follow the recovery workflow for scanning, selecting and exporting files. Save outside the image set and retain the parent/extent relationships. A guest volume may still require its own valid credentials and supported file-system access.
If the image cannot be interpreted
Record the image format, creator/version, host-file size, virtual capacity if known, standalone/chain status, encryption state, and exact error. Confirm that the source was copied completely and all dependencies are available.
A missing parent, damaged container, incomplete extent set, or unreadable underlying host storage is different from deleted files inside an intact guest volume. Resolve the appropriate layer before expecting another file scan to help. Keep the protected originals and all useful exports while that specific issue is assessed.