In cross-replication (Hyper-V -> VMware), after a Failover\Move, Windows VMs may fail to boot with the following error code\message:

Windows boot with STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE.
Windows boot into Recovery Mode.

Root Cause

This issue is the result of missing SCSI controller drivers in Windows operating system.


Depending on the Windows version of the VMs that failed to boot, there are specific steps to perform on the operation system that will allow support for SCSI controllers.

When in a Failover\Move scenario, please rollback the operation, perform the necessary changes on the source VM, and Failover again to make sure Windows is able to boot.
Follow this article to explain which SCSI controllers to apply:

Note the different steps for the different Windows versions, for example:
Windows All Versions (Most commonly 2012\2012R2 'etc) - vmscsi drivers
Windows 2003 - lsilogic and vmscsi drivers
Windows 2008 and 7 - LSI SAS drivers

IMPORTANT NOTE: After performing the necessary changes on the protected VM, please reboot it in order to apply the changes. This step is crucial to the success of the procedure, and tends to get overlooked.