Converting a Physical Workstation to a Virtual Workstation

When using Disk2VHD to convert a physical workstation to a virtual workstation, problems can arise. This article specifically addresses the blue screen STOP 0x0000007B error that occurs when you try to boot your new virtual PC.

This problem is caused by Windows attempting to boot from a different hard drive controller than the controller used on your physical PC. If your physical PC is booting from a SATA, SAS, or SCSI controller, this problem will probably occur. Windows Virtual PC, Virtual Server, and Generation 1 VMs in Hyper-V all use a virtual IDE controller to which primary (boot) virtual disks are attached.

Thankfully, there is a relatively easy fix for this problem that can be accomplished even after the VHD (or VHDX) has been created. By mounting the virtual drive, it’s easy to verify that the proper driver files exist and modify the appropriate registry entries for the virtual PC.

Modifying the registry obviously comes with the standard disclaimers about how doing so can completely corrupt your PC installation. We accept no liability or responsibility for problems caused by registry editing and you should definitely make backups and proceed with care.

  1. Mount the virtual drive so that you can access the files contained therein. In Windows 8, you can right click the VHD file and click “Mount” on the context menu that appears. In Windows 7, follow the instructions found on this page: http://technet.microsoft.com/en-us/magazine/ee872416.aspx

  2. After the drive has been mounted, navigate to the Windows\System32\drivers folder on the mounted drive and make sure that the following files exist:

    1. intelide.sys

    2. pciide.sys

    3. atapi.sys

  3. If the any of these files are missing, they can be copied from another computer or from the installation media.

  4. Make a backup of the file Windows\System32\config\system on the virtual drive.

  5. To modify the registry keys of the virtual PC, open the registry editor (regedit.exe) and click on HKEY_LOCAL_MACHINE. Click the “File” menu and then on “Load Hive…”. Navigate to the Windows\System32\config folder on the mounted virtual drive and select the “system” file to load.

  6. When prompted to enter a name for the Hive, type something unique like TEMP or NEWPC.

  7. You can now navigate to the ControlSet001 key under the newly loaded hive (under the name that you typed) and then Services subkey. Under this key, find the following keys and verify that the “Start” value matches those listed here:

    1. aliide = 3

    2. amdide = 3

    3. Atapi = 0

    4. cmdide = 3

    5. iaStorV = 3

    6. intelide = 0

    7. msahci = 3

    8. pciide = 3

    9. viaide =3

  8. After any changes have been made, click on the File menu and select “Unload Hive….” to close the file being edited and then close the registry editor.

  9. Unmount the VHD file by right clicking the virtual drive letter and selecting “Eject”.

  10. Your new VM should now boot without any blue screen.

June 05, 2015 by Lauren Winstead Category: General IT 0 comments

Recent Posts