INACCESSIBLE BOOT DEVICE or 0x0000007B STOP error after Image Export

Issue

A virtual machine created from the image export process boots to an "Inaccessible Boot Device" or "0x0000007B STOP" error screen regardless of the virtual storage controller selected.…

Environment

  • Datto ALTO
  • Datto SIRIS
  • VMware
  • Microsoft Hyper-V

Resolution

If the VM did not boot properly initially, attempt to boot the VM using all available virtual storage controllers.

If the above step does not resolve the issue or if the VM booted properly initially, and then went to a 7B BSOD error after a reboot, run these steps:

  1. Boot the machine into safe mode with networking or without. Allow the machine to boot fully.
  2. Reboot the machine normally.
  3. Test one more reboot to ensure resolution.

If the above steps are unsuccessful, follow the steps listed for your hypervisor below.

On VMware hypervisors

  1. Mount a Windows Recovery or install disk using VMware Player.

  2. Boot the VM into the recovery environment.

  3. At the first screen (Language Selection), press Shift + F10 for a command prompt

  4. Open the registry editor with:

    regedit

  5. In the registry, highlight HKEY_LOCAL_MACHINE.

  6. Click File > Load Hive.

  7. In the window that opens, select the virtual machine's OS (or C:) volume, then navigate to the following file and select it:

    \Windows\System32\config\system

  8. Enter a name for the loaded hive, when prompted. This will be referenced in the registry paths.

  9. In the virtual machine's registry, expand the following key:

    HKEY_LOCAL_MACHINE\<name>\ControlSet001\Services\intelide

  10. Change the data for the Start value to 0.

  11. In the registry window, highlight the following key:

    HKEY\LOCAL_MACHINE\<name>

  12. Then select File > Unload Hive to unload the hive.

  13. Exit the registry editor.

  14. Reboot the virtual machine.

On Hyper-V hypervisors

Right-click the C.vhd or C.vhdx disk image within your datastore, and choose mount. Verify the location of the SYSTEM registry hive:

C:\Windows\System32\config\SYSTEM

Edit the registry hive

In the Registry hive, the vmbus START key and the LSI keys must be set to 0 to allow bootability.

  1. Open the registry editor with:

    regedit

  2. In the registry, highlight HKEY_LOCAL_MACHINE.

  3. Click File > Load Hive.

  4. In the window that opens, select the virtual machine's OS (or C:) volume, then navigate to the following file and select it:

    \Windows\System32\config\system

  5. Enter a name for the loaded hive, when prompted. This will be referenced in the registry paths.

  6. In the virtual machine's registry, expand the following key:

    HKEY_LOCAL_MACHINE\<name>\ControlSet001\Services\intelide.

  7. Change the data for the Start value to 0.

  8. In the virtual machine's registry, expand the following key:

    HKEY_LOCAL_MACHINE\<name>\ControlSet001\Services\vmbus

  9. Change the data for the Start value to 0.

  10. Make sure the following keys also have start values set to 0:

    Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS2i
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS3i
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SSS

  11. In the registry window, highlight the following key:

    HKEY\LOCAL_MACHINE\<name>

  12. Then select File > Unload Hive to unload the hive.

  13. Exit the registry editor.

  14. Right-click the C.vhdx virtual disk under This PC or My Computer and choose Eject.

  15. Reboot the VM.

If the issue persists attempt to boot the machine into safe mode or last known good config, if the machine does not come back up contact Datto Technical Support.