Share via

P2V Migration Issues with Hyper-V: STOP: 0x0000007B

  • Article

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
    • 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\CriticalDeviceDatabase\pci#ven_8086&dev_7111
      • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601
      • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel
      • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel
      • HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde
      • 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\pci#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\pci#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\primary_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\secondary_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\

The End

--Mike Schmidt

Comments

  • Anonymous
    January 01, 2003
    @sbalk - You are correct. I updated the post. Thanks!

  • Anonymous
    January 01, 2003
    great help, thanks!

  • Anonymous
    January 01, 2003
    Love it!  Thanks for sharing how to fix this Michael.

  • Anonymous
    January 01, 2003
    this is nice however i have a question. should i not put them under  HKEY_LOCAL_MACHINESystemControlSet001Servicesatapi or leave out system? sorry for a dumb question. i was just wondering.thanks so much for your help.

  • Anonymous
    January 01, 2003
    Worked Great! Exactly what I needed for a 2008R2 and 2003R2 P2V.

  • Anonymous
    January 01, 2003
    thanks

  • Anonymous
    January 22, 2014
    Thanks! Thanks! Thanks! It works!!!

  • Anonymous
    January 22, 2014
    Thanks! Thanks! Thanks! It works!!!

  • Anonymous
    February 07, 2014
    Mike, we are experiencing a similar issue with virtual hard disks that are created from existing Windows Vista machines. One .vhd came from a laptop and the other from a HP workstation, but both yield the same stop error when booting in Hyper-V on Windows 8.1. We tried the above registry fix for one .vhd disk however we received a Winload.exe error c000000e error on boot. Any thoughts on how to correct this for Windows Vista .vhd disks? Thanks, David Lloyd

  • Anonymous
    February 28, 2014
    Thanks a lot works great!!!!!

  • Anonymous
    March 13, 2014
    I owe you a beer. Worked like a champ. Like some said before, this should absolutely be worked out by Microsoft by now.

  • Anonymous
    April 02, 2014
    Thanks!

  • Anonymous
    April 12, 2014
    The comment has been removed

  • Anonymous
    June 22, 2014
    This worked for me after i used Microsoft Windows Backup to image a physical HP Proliant DL360 G7 server and restore into Hyper-V 2012 R2 virtual and changed the reg key below:


    [HKEY_LOCAL_MACHINESYSTEMControlSet001ControlCriticalDeviceDatabasepci#ven_8086&dev_7110&cc_0601]
    "ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
    "Service"="msisadrv"

    TO

    [HKEY_LOCAL_MACHINESYSTEMControlSet001ControlCriticalDeviceDatabasepci#ven_8086&dev_7110&cc_0601]
    "ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}"
    "Service"="isapnp"


    Thanks allot for doing this article, i saved heaps of time!

  • Anonymous
    August 14, 2014
    Wonderfull

  • Anonymous
    August 29, 2014
    I love you!

  • Anonymous
    September 01, 2014
    Is there a way to automatically create or import the missing registry entries while the hive is loaded?

  • Anonymous
    September 18, 2014
    Thank you very much!
    You solved me this problem in just 1 minute google searching and half an hour rerunning disk2vhd

    We love you too ;)

  • Anonymous
    November 12, 2014
    Was having the same issue on physical to virtual converted Desktop running Server 2003 (don't ask!) on VMware and worked like a charm! Thank you Sir!

  • Anonymous
    November 12, 2014
    I was just missing intelide.sys file. Thank you !

  • Anonymous
    November 12, 2014
    Thanks Mike!

  • Anonymous
    November 14, 2014
    Genius! :)

  • Anonymous
    December 04, 2014
    Thanks! This saved my day :-)

  • Anonymous
    December 24, 2014
    Thanks! Work with 2008 SBS X64 ;)

  • Anonymous
    January 04, 2015
    how can you perform step and step 2?

    Mount the VHD to examine the contents
    Within the VHD, locate the SYSTEM registry and mount it with RegEdit (windowssystem32configsystem)

  • Anonymous
    January 27, 2015
    @Peter open regedit click on HKEY_LOCAL_MACHINE > click file load hive > browse for SYSTEM on the mounted VHD> open> give it a key name like tst. > ok

  • Anonymous
    February 26, 2015
    This was great, fixed my issue P2V win 2k3 server instance to Hyper-V. (via datto export of Hyper-V disk)

  • Anonymous
    February 28, 2015
    Many years after you posted this it's still saving people. Just ran into this after doing a disk2vhd on a Windows 2008 R2 install for a Hyper-v 2012 R2 guest conversion and your fix did the trick. Nice and quick - thanks very much!

  • Anonymous
    April 09, 2015
    Thank you so much ! You are great man, Mike !

  • Anonymous
    April 13, 2015
    The comment has been removed

  • Anonymous
    April 14, 2015
    Amended: the issue is Hyper-V integration services. These need to be removed first. Our HyperV is 2012 which throws the BSOD if the IS are not removed first.

  • Anonymous
    April 14, 2015
    @Not_So_Ninja
    Would you mind posting how you went about removing the Hyper-V integration services from the VHD image, sadly my physical machine has now died and all I have to work with is the VHD and a VHDX image. Thanks

  • Anonymous
    May 03, 2015
    You're the best, thanks!

  • Anonymous
    May 04, 2015
    Hello all,

    Thank Mike for your nice help ... but i have bsod again on my vhdx (windows XP).

    When i check the registry, all registry keys added are present exept "CriticalDeviceDatabase" keys ... however, i saved it fews times on system hive but nothing ... :(

    Do you know if my bsod is due to this registry key who is missing ?

    Thanks for your help.

  • Anonymous
    May 09, 2015
    i award 500$ for someone who can bring up a p2v windows 2000 server machine in hyper-v, i tried every method i found on the web for over 30 hours now, always end up in getting 0x0000007B and can not get ride of it, contact me at info@michaelmollet.de and i will give you the download link to the vhd file so you can try your luck.

  • Anonymous
    May 10, 2015
    hah, after trying only to p2v drive c it worked ...

  • Anonymous
    June 03, 2015
    The comment has been removed

  • Anonymous
    June 25, 2015
    Worked perfectly, thank you!!

  • Anonymous
    June 27, 2015
    Where i can mount vhd file..in Hyper-v server or local server.if hyper-V server how to i modify the registry.

    Please help me..

  • Anonymous
    June 29, 2015
    Hi.
    My issue still not resolved after following above steps.

    Kindly help

  • Anonymous
    August 19, 2015
    We love you to... you are the king of Hyper-V & Registry

  • Anonymous
    October 09, 2015
    Yes, this worked! Thanks so much!

  • Anonymous
    October 15, 2015
    Thanks Mike!!!! It Works!!!! Thanks a lot!!!

  • Anonymous
    October 15, 2015
    Thanks Mike!!!! It Works!!!!

  • Anonymous
    October 28, 2015
    Just used your method for a 2k8 R2 P2V Conversion to successfully fix our blue screen issue. Running 2012 R2 Hyper-V Host. Thanks!!

  • Anonymous
    December 12, 2015
    Thank You!!! It helped me a lot!

  • Anonymous
    January 06, 2016
    Great! You saved us!!!

  • Anonymous
    January 15, 2016
    After converting a physical Windows XP to VHD, I had the problem described in this article. I applied all the fixes, but I now encounter another error: when booting, the SYSTEM file is missing. I checked, but the file is there, it looks to have the correct size and security.
    What can be wrong? Thank you very much.

  • Anonymous
    January 22, 2016
    it really help me on 17 January 2016 when I was on site, thanks very much,
    in my case, I convert server 2008R2 to virtual machine running on hyper-V 2012. only one registry key I didn't change is "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"
    under
    [HKEY_LOCAL_MACHINESYSTEMControlSet001Servicesatapi]
    again, thanks a lot.

  • Anonymous
    February 15, 2016
    The comment has been removed

  • Anonymous
    March 16, 2016
    Capo total ! ! ! !

  • Anonymous
    March 27, 2016
    Searched whole internet for the fix and finally found article on experts exchange which source its information from this link. Very grateful for information here which worked a treat after hours spent! Thank YOU!!!!