P2V Migration Issues with HyperV: STOP: 0x0000007B

When converting a Windows XP / Windows 2003 machine with P2V utilities,

a STOP: 0x0000007B may occur during boot in Hyper-V. (Pressing F8 during boot
and selecting the option to "Disable automatic restart on system failure" will
reveal the blue screen error code.) Typically this indicates the lack of a necessary
driver required by Hyper-V virtual hardware (IDE channel).
To confirm the issue relates to this article, follow these steps:
1.

Mount the VHD to examine the contents

2.

Within the VHD, locate the SYSTEM registry and mount it with RegEdit
(\windows\system32\config\system)

3.

Check the file system and registry for these entries

o

Confirm Files Exist

windows\system32\drivers\intelide.sys

windows\system32\drivers\pciide.sys

windows\system32\drivers\atapi.sys

Confirm Registry Entries Exist

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalD
eviceDatabase\pci#ven_8086&dev_7111

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalD
eviceDatabase\pci#ven_8086&dev_7110&cc_0601

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalD
eviceDatabase\primary_ide_channel

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalD
eviceDatabase\secondary_ide_channel

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelId
e

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi

Any missing items from step #3 can be remedied through the information given
below. Hyper-V requires these critical devices and services to boot; a lack of this
information in Windows will result in a 0x0000007B, or perpetually rebooting
machine.
Required Registry Critical Boot Entries
pci#ven_8086&dev_7111
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\p
ci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"
pci#ven_8086&dev_7110&cc_0601
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\p
ci#ven_8086&dev_7110&cc_0601]
"ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
"Service"="isapnp"
primary_ide_channel
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\p
rimary_ide_channel]
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
secondary_ide_channel
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\s
econdary_ide_channel]
"Service"="atapi"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
Required Registry Service Entries
intelide.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"

"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
pciide.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,
00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
atapi.reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,
00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
Required Driver Files

windows\system32\drivers\intelide.sys

windows\system32\drivers\pciide.sys

windows\system32\drivers\atapi.sys

Any missing file may be available from a .CAB within \windows\Driver Cache\

 Cause
Hyper-V mounts the VM's virtual disks through an IDE controller, and when a P2V from SCSI
drives to IDE is performed, the IDE drivers are not active. Below is how to activate those
drivers.

Resolution
To resolve this issue, complete the following steps.
First, confirm that the necessary drivers are present by booting into the AppAssure BootCD
o

Open a cmd prompt

Change the directory to C:\Windows\System32\drivers

The command is: cd C:\Windows\System32\drivers

List the directory: dir

Verify that the following drivers are present:

intelide.sys

pciide.sys

atapi.sys

Open the Registry Editor within cmd prompt: regedit

Scroll down to Users and File-> Import Hive

Navigate to C:\Windows\Systems32\Config\

Right click the SYSTEM file and select copy and then paste to make a
backup of it (refresh the window to verify a copy has been made)

Import the file and give a temp name, such as P2V

Confirm that the existing registries exist:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDev
iceDatabase\pci#ven_8086&dev_7111

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDev
iceDatabase\pci#ven_8086&dev_7110&cc_0601

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDev
iceDatabase\primary_ide_channel

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDev
iceDatabase\secondary_ide_channel

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi

Take note of any missing drivers or registry keys from the above steps. If any of these files are
missing they can be created or imported. Hyper-V needs these drivers and services to boot and
an absence of this information will result in the 0x7B STOP error.
The following is the information to create the missing registry keys:
pci#ven_8086&dev_7111
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&d
ev_7111]
ClassGUID={4D36E96A-E325-11CE-BFC1-08002BE10318}
Service=intelide
pci#ven_8086&dev_7110&cc_0601
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&d
ev_7110&cc_0601]
ClassGUID={4D36E97D-E325-11CE-BFC1-08002BE10318}
Service=isapnp
primary_ide_channel
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_cha
nnel]
Service=atapi
ClassGUID={4D36E96A-E325-11CE-BFC1-08002BE10318}
secondary_ide_channel
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_c
hannel]

Service=atapi
ClassGUID={4D36E96A-E325-11CE-BFC1-08002BE10318}
Required Registry Entries
intelide.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde]
ErrorControl=dword:00000001
Group=System Bus Extender
Start=dword:00000000
Tag=dword:00000004
Type=dword:00000001

pciide.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde]
ErrorControl=dword:00000001
Group=System Bus Extender
Start=dword:00000000
Tag=dword:00000003
Type=dword:00000001
ImagePath=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
DisplayName=Standard IDE/ESDI Hard Disk Controller

atapi.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi]
ErrorControl=dword:00000001
Group=SCSI miniport
Start=dword:00000000
Tag=dword:00000019
Type=dword:00000001
DisplayName=Standard IDE/ESDI Hard Disk Controller
ImagePath=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
Required Driver Files
windows\system32\drivers\intelide.sys
windows\system32\drivers\pciide.sys
windows\system32\drivers\atapi.sys
Located within C:\Windows\Driver Cache\i386, you should be able to extract these drivers from
the driver.cab file. The expand command will allow you to extract from this .cab file. Verify
that the driver.cab file is located in the above directory.

In a command prompt, issue the following command:

expand "c:\windows\driver cache\i386\driver.cab" /f:driver.sys c:\windows\system32\drivers
For c:\, verify the proper volume letter for your scenario.
The /f:driver.sys is telling the command to find the specific driver (for instance the pciide.sys)
and to extract it to the directory following the switch. The "driver.sys" should be modified to
match the missing drivers that have been discovered.
Much of the information was pulled from the resources below and can be referenced if
necessary: