Hyper-V Program Manager
Well we are at the final post in my series on migrating a physical computer to a virtual machine. If all other steps have failed the last thing to check is the HAL that is being used by the operating system. The HAL is the 'Hardware Abstraction Layer' and is responsible for some of the lowest level access in the system. You can find out about all the various HALs here: http://support.microsoft.com/default.aspx?scid=kb;en-us;309283.
Having the wrong HAL loaded can result in:
In order to update the HAL you should boot into the recovery console (as described here: http://blogs.msdn.com/virtual_pc_guy/archive/2004/12/10.aspx). You should then change directory to the \WINDOWS\SYSTEM32 directory and run "expand D:\I386\HALACPI.DL_" followed by "copy HALACPI.DLL HAL.DLL".
Note - this method is not officially supported by Microsoft - but I have found it to be very handy :-)
Thanks so much for this! It's been very helpfull. In my case, doing part four fixed my booting issues w/o step three. Also, step four is quick and easy compaired to three, so why not try it first? Again, great tutorial.
I just wanted to give a shout out - this process was instrumental in letting us get integration services installed on a 2003 server that has been dragged from physical to virtual server 2005 to now hyper-v. After performing this process, we were able to open device manager, and then delete the "standard pc" device. then after reboot integration services installed. Thank you!