P2V Migration Issues with Hyper-V: 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
    • 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


Windows Registry Editor Version 5.00



Windows Registry Editor Version 5.00



Windows Registry Editor Version 5.00



Windows Registry Editor Version 5.00


Required Registry Service Entries


Windows Registry Editor Version 5.00

"Group"="System Bus Extender"


Windows Registry Editor Version 5.00

"Group"="System Bus Extender"
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"


Windows Registry Editor Version 5.00

"Group"="SCSI miniport"
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"

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 (52)

  1. --Mike says:

    @sbalk – You are correct. I updated the post. Thanks!

  2. Anonymous says:

    great help, thanks!

  3. ChrAd says:

    Love it!  Thanks for sharing how to fix this Michael.

  4. Anonymous says:

    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.

  5. MrTech86 says:

    Worked Great! Exactly what I needed for a 2008R2 and 2003R2 P2V.

  6. MikesMMM says:

    Thanks! Thanks! Thanks! It works!!!

  7. MikesMMM says:

    Thanks! Thanks! Thanks! It works!!!

  8. David Lloyd says:

    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

  9. Giomel says:

    Thanks a lot works great!!!!!

  10. Mingus says:

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

  11. stella says:


  12. Nick Burns says:

    You are a god among men, sir. Just make sure you modify your .reg file to match what you have on your system. I had to do it a couple times but once I actually paid attention, WHAMMY!

  13. DJ Windows says:

    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:




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

  14. giordano says:


  15. Eric says:

    I love you!

  16. jlewis says:

    Is there a way to automatically create or import the missing registry entries while the hive is loaded?

  17. Marcotrotamundos says:

    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 😉

  18. Andy says:

    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!

  19. Henri R says:

    I was just missing intelide.sys file. Thank you !

  20. Trevor says:

    Thanks Mike!

  21. alex says:

    Genius! 🙂

  22. jan says:

    Thanks! This saved my day 🙂

  23. Nicolas R. says:

    Thanks! Work with 2008 SBS X64 😉

  24. Peter says:

    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)

  25. sam says:

    @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

  26. Works! says:

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

  27. KHolden says:

    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!

  28. Alexey says:

    Thank you so much ! You are great man, Mike !

  29. Not_So_Ninja says:

    I appreciate all the information that has been give in this post. I have a random scenario: we have a windows 2k box that was p2v’d successfully, after trying to do an in place upgrade to 2k3, we get the BSOD related to this post. I have gone through and
    verified the drivers/registry are correct. Any thoughts would be greatly appreciated to troubleshoot

  30. Not_So_Ninja says:

    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.

  31. mike says:

    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

  32. Tim says:

    You’re the best, thanks!

  33. Back says:

    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.

  34. Michael Mollet says:

    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.

  35. Michael Mollet says:

    hah, after trying only to p2v drive c it worked …

  36. NOEL says:

    Flawless! Worked after making changes to hive. Installed integration services and the 2003 box works like a champ.

  37. CS says:

    Worked perfectly, thank you!!

  38. anv says:

    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..

  39. Ramana says:

    My issue still not resolved after following above steps.

    Kindly help

  40. Flavio & Roman says:

    We love you to… you are the king of Hyper-V & Registry

  41. ImTryingtoBeVitualizationKing2 says:

    Yes, this worked! Thanks so much!

  42. Forcelledo says:

    Thanks Mike!!!! It Works!!!! Thanks a lot!!!

  43. Hector Forcelledo says:

    Thanks Mike!!!! It Works!!!!

  44. Dminard says:

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

  45. Mindaugas says:

    Thank You!!! It helped me a lot!

  46. Andrew says:

    Great! You saved us!!!

  47. Van says:

    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.

  48. Erik says:

    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,
    again, thanks a lot.

  49. John Zoch says:

    Thank you! Maybe you should make a reg file. I got into command shell from the Win 7 install DVD, ran reg edit, mounted the hive at "Foo" (System was taken by the Win PE registry) then imported a foo.reg file from a CD-ROM I burned. I made the reg file
    with text editor and just copied your settings substituting SYSTEM for Foo in my hive.

  50. Carlos says:

    Capo total ! ! ! !

  51. Very Grateful says:

    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!!!!