restore failure: unable to recognize virtual device: Vizioncore.Vim20.VirtualDev (4046918)

Standard restore of a VM with error, "Unable to recognize virtual device: Vizioncore.Vim20.VirtualDev"

After investigation following has been found:
VM resided on ESX5;
backup was performed by vRangerPro 5.0
VmConfig.metadata file contains corrupted hardware tag.

Ranger 5.0 did not support ESX5.

Instructions:

1. Make a copy of existing VmConfig.metadata file.
2. Edit VmConfig file
   2.1. delete following block. usually goes after <device xsi:type="VirtualMachineVideoCard">
   <device><key>12000</key><deviceInfo><label>VMCI device</label><summary>Device on the virtual machine PCI bus that provides support for the virtual machine communication interface</summary></deviceInfo><controllerKey>100</controllerKey><unitNumber>17</unitNumber></device>
   2.2. delete following tag near the bottom of the file
   <extraConfig xmlns="urn:vim2"><key>vmci0.pciSlotNumber</key><value xsi:type="xsd:string">34</value></extraConfig>
3. Create 'Restore from Savepoint Manifest' job and run.
4. If this job fails with error "API Call failed with message: The device "X" is referring to a nonexisting controller '1,000'."
   edit VmConfig file one more time
   replace following line
   <device xsi:type="VirtualSCSIController"><key>1000</key><deviceInfo><label>SCSI controller 0</label><summary>LSI Logic SAS</summary>
   with
   <device xsi:type="VirtualBusLogicController"><key>1000</key><deviceInfo><label>SCSI controller 0</label><summary>BusLogic</summary>
5. Create another 'Restore from Savepoint Manifest' job and run.

If restored VM is 64 bit, following line should be used in step 4:

<device xsi:type="VirtualBusLogicController"><key>1000</key><deviceInfo><label>SCSI controller 0</label><summary>BusLogic Parallel</summary>