Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMware Converter (1005208)

Last Updated: 3/20/2024Categories: How toTotal Views: 353244Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

37 like this article

Subscribe to get an email
newsletter with new updates

37 people found this helpful Please provide article feedback:

Symptoms

Conversion fails between 97% and 99%.

The virtual machine is created on the destination.

The virtual machine which was created fails to start after conversion.

Windows boots to a blue screen error:

STOP 0x7B INACCESSIBLE_BOOT_DEVICE

STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE

Purpose

This article provides instructions on copying the appropriate disk controller driver from a working virtual machine onto a physical or virtual machine prior to conversion to resolve a STOP 0x7B failure when using VMware Converter, or if the SCSI adapter has been changed.

This issue can occur when the appropriate drivers cannot be located by Windows on boot, and must be manually copied to resolve.

Resolution

All Windows Versions (vmscsi only)

To copy the appropriate disk controller driver from a working virtual machine with a Windows guest operating system:

Power on the source for the conversion. The source can be physical or virtual.

Download the VMware SCSI Disk Controller driver diskette at:

http://download3.vmware.com/software/vmscsi-1.2.0.4.flp

If the source is virtual, attach the driver diskette to the virtual machine's virtual floppy drive.

If the source is physical, use any of these methods to copy the files from the diskette image:

Extract the disk image into files and copy them to the source.

Attach the diskette to a virtual machine and copy the files from the virtual diskette drive to the physical source.

Write the contents of the image onto a floppy diskette and insert the diskette into the physical source.

Note: Image extraction software is required to use this method.

Access the floppy diskette or files

Right-click vmscsi.inf and click Install. The VMware SCSI drivers are installed.

Restart the source to complete installation.

Perform another conversion with VMware Converter.

Windows 2008 and Windows 7 (LSI SAS)

Windows 2008 and Windows 7 have the LSI SAS driver installed by default, but they require a registry key to activate it:

Confirm that the target machine has lsi_sas.sys present in the C:\Windows\System32\Drivers directory. This should be included by default during the installation of Windows. If it is missing, copy it from a working virtual machine.

Power on a working Windows 2008 or Windows 7 virtual machine.

Click Start > Run, type regedit, and press Enter.

Navigate to and export this registry key (right-click Export):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS

Import the registry keys from step 4 into the source system to be converted.

Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393.

Restart the source system to complete installation. This requires downtime for the source system.

Perform another conversion with VMware Converter.

Windows 2003 (lsilogic and vmscsi)

Note: This is not a VMware issue. Complete this workaround.

To copy the appropriate disk controller driver from a working virtual machine with Windows 2003 installed:

Power on the source for the conversion. The source can be physical or virtual.

Power on a working virtual machine running Windows 2003.

Copy the LSI Logic disk controller driver file located at %systemroot%\system32\drivers\symmpi.sys to the source for the conversion.

Copy the VMware SCSI disk controller device driver file (if present) located in %systemroot%\system32\drivers\vmscsi.sys to the source for the conversion.

Click Start > Run, type regedit, and press Enter.

Browse to and export these registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\symmpi

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_1000&dev_0030

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmscsi

Note: The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine.

Import the registry keys from step 6 into the conversion source.

Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393.

Restart the source to complete installation.

Perform another conversion with VMware Converter.

Windows XP / 2000 / NT (buslogic and vmscsi)

To copy the appropriate disk controller driver from a working virtual machine with a Windows XP/2000/NT guest operating system:

Power on the source for the conversion. The source can be physical or virtual.

Power on a working virtual machine running a matching version of Windows.

Copy the Buslogic disk controller device driver file located at %systemroot%\system32\drivers\buslogic.sys to the source for the conversion.

Copy the VMware SCSI disk controller device driver file (if present) located at %systemroot%\system32\drivers\vmscsi.sys to the source for the conversion.

Click Start > Run, type regedit, and press Enter.

Browse to and export these registry keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BusLogic

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\
pci#ven_104b&dev_1040

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmscsi

Note: The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine.

Import the registry keys from step 6 into the conversion source.

Note: Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft article 136393.

Restart the source to complete installation.

Perform another conversion with VMware Converter.

Related Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box

For translated versions of this article, see:

Español: Introducir controladores de dispositivo SCSI en Windows cuando falla al iniciarse luego de convertirlo con VMware Converter (2016494)

Português: Inserindo drivers de dispositivo do controlador SCSI no Windows em caso de falha ao inicializar após convertê-lo com o VMware Converter (2015995)

Mandarin Chinese: 使用VMware Converter转换后的Windows虚拟机无法启动手动加载SCSI控制器驱动程序 (2020967)

Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after using VMware Converter (2002106)

Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after using VMware Converter
Inserindo drivers de dispositivo do controlador SCSI no Windows em caso de falha ao inicializar após convertê-lo com o VMware Converter
Introducir controladores de dispositivo SCSI en Windows cuando falla al iniciarse luego de convertirlo con VMware Converter
当 Windows 在使用 VMware Converter 转换后无法引导时向其中插入 SCSI 控制器设备驱动程序
VMware Converter による変換後起動に失敗したとき、SCSI コントローラ デバイス ドライバを Windows に挿入する

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware vCenter Converter Standalone

VMware vCenter Converter

VMware ESX Server

VMware Converter

Related Versions:

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.0.x

VMware vCenter Converter Standalone 6.x

VMware vCenter Converter Standalone 6.0.x

VMware vCenter Converter Standalone 5.x

VMware vCenter Converter Standalone 5.5.x

VMware vCenter Converter Standalone 5.1.x

VMware vCenter Converter Standalone 5.0.x

VMware vCenter Converter Standalone 4.3.x

VMware vCenter Converter Standalone 4.0.x

VMware vCenter Converter 4.2.x

VMware vCenter Converter 4.1.x

VMware vCenter Converter 4.0.x

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

VMware Converter 3.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant