Microsoft Hyper-V Recovery

Attingo reverse engineered all Microsoft Hyper-V servers and is able to reconstruct virtual machines successfully with in-house software. The data recovery is possible regardless of the server size and the number of servers running on it.

The underlying storage system may comprise a single hard drive of a PC, whole RAID networks of a server or storage connected via iSCSI. It uses the virtual disk image format VHD (virtual hard disk).
With the introduction of Windows 8 and Windows Server 2012 the VHDX file format was introduced to enable the smooth operation of even bigger VHDs. It offers the following improvements compared to the previous VHD format:

Creation of virtual drives with a size up to 64 TB

Access is possible under Windows Server 2012 and also under Windows 8 via the explorer.

Error patterns we already dealt with successfully

Because of incomplete Hyper-V replica backups only temporary .vhdx.tmp files are left. They can neither be added as a virtual hard drive via the data storage administration nor be attached via diskpart.

Defective incremental avhd and avhdx snapshots due to missing or defective files in the parent-child-chain (corruptive parent locator).

Dynamic data storage cannot be mounted

Static virtual hard drive was deleted from the file system: by aimed search for file type headers connectix (with vhd) or vhdxfileM.i.c.r.o.s.o.f.t (with vhdx).

Data recovery deleted or defective Hyper-V servers - We help in case of data loss!

We provide multiple diagnosis options depending on the urgency of your data rescue case

After the diagnosis is completed you receive a fixed price offer

No hidden costs - Expenses are only incurred if the database data rescue is successful

The recovery of your Hyper-V server will be done by experienced and specially trained engineers

Fast reaction times - in urgent cases, we offer a 24x7 service

In-house research and development in order to keep up with the newest hardware and software

More than 14.500 spare parts in Vienna, Hamburg and Amsterdam

Contact us - order your diagnosis today.

Possible error sources

Eventual problems or errors can occur inside the host system or within the VHD container files. It often happens that dynamic VHD files or snapshots are defective - in both cases we are able to reconstruct your data. Recently we received many data rescue cases with deleted VHD files which comprised virtual hard drives.

0 byte problem

The so-called 0 byte problem is also very common. The VHD file is displayed with a file size of 0 bytes. It's really important that the host system is turned off and the power cable is unplugged immediately. The system should not be restarted or continued to use to prevent new writing errors.

Typical error messages

Virtual computers are missing
0x800704C8 error: The requested process cannot be carried out, the file is assigned to an opened section use. (0x800704C8)
0x80070037 error: VMName ’ Microsoft Synthetic Ethernet-Port (authority identification {7FGDB81A-A7B4-4DFD-869F-37002C36Z816}): Error during power on with error message "the network resource or device us no longer available" (0x80070037)
0x800703E3 error: The I/O process was cancelled due to en ending thread or an application requirement (0x800703E3)
A Virtual Disk Provider for the specified file was not found
An error occurred while attempting to start the selected virtual machine(s).
For the indicated file no host for the virtual data carrier support was found
vhd: BOOTMGR is missing
CDynamicVHD2::Write: current position error ; WriteToDisk: m_pCurDisk->Write failed. dwBytesToWrite[512], dwWritten[0] ; Write: WriteToDisk failed.