So for reasons fully understood and accepted, my employer has stated that we may no longer use Windows 7 on laptops in the short term. The carrot is that we may run it as a VM if we wish. Fantastic! As I've done many times in the past with XP, I'll just P2V my Win7 laptop and run it in VMWare Player (3.0 RC, so I can get Aero). Only one problem. As before, I used the VMware vCenter Converter 4.0 to P2V my laptop expecting the angels to sing. No so much. Got a STOP 0x0000007B on boot. With automatic reboot on error enabled, it also manifests itself as a Windows Boot Manager error, Status: 0xc0000225, Info: The boot selection failed because a required device is inaccessible.
So off to Google I went. For two days I played with DiskPart and BCDEdit. Learned a lot, but made no headway. Until I found this:
http://web2.minasi.com/forum/topic.asp?TOPIC_ID=31980
Yes, that's right... It's a simple, old fasioned mass storage driver issue. The hitch is that drivers are there but not enabled in an effort to improve boot performance. The article on Minasi's site offers a pretty good explanation for Hyper-V, and the same applies to VMware. I took slightly different (and less complicated, I think) steps to resolve the issue without having to re-do the P2V:
- Mount the Win7 DVD in VMware Player and boot to it.
- At the first screen (Language Selection), hit Shift-F10 for a command prompt.
- Run Regedit.
- Load the system hive from the VM's disk:
- Highlight HKEY_LOCAL_MACHINE
- File > Load Hive
- Select < c: > \Windows\System32\config\system (name it something like "asdf")
- Expand HKEY_LOCAL_MACHINE\asdf\ControlSet1\Services\intelide
- Change the data for value "Start" from "3" to "0".
- File > Unload Hive.
- Exit regedit.
- Reboot the VM.
24 comments:
HKEY_LOCAL_MACHINE\asdf\ControlSet1\Services\intelide
what if its already 0 ; i changed it to 3 and both ways i still can not bootup my windows7.
Any ideas please?
Thank you very much,
This fixed my problem and it worked.
Well done !!!!
your are the king!
So close! I'm in the same boat as Valeriy: HKEY_LOCAL_MACHINE\asdf\ControlSet1\Services\intelide was set to '0'.
1. Is there any point to changing it back to '3' and then resetting to '0'?
2. If the setting was originally '0' does that indicate another problem?
Valeriy & Jeff... My instructions are for a VM with an virtual IDE controller. If you are using a virtual SCSI controller, you'll need to find out which driver it is that you need to change to '0'. It won't be intelide.
Thank you so much!
I spent ages fiddling with VirtualBox and VMWare trying to fix this (I don't often use Windows), until I found your post.
:-)
My intelide was also already set to 0. I followed the link Andrew provided and read through that thread, then I made sure my settings matched these:
Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3
3 or 4 of them were different. This worked for me
Worked. Thank you sir!
Fixed my driver mismatch issue.
(AHCI physical vs IDE Virtual)
Thx!
Brilliant. Thank you sir!
Saving atapi to 0 fixed my problem. Thanks for your help.
Thanks, thanks, thanks, more than brilliant. The atapi=0 did it for me. You really made my holidays!
great tip! thanks for sharing I used it to recover a virtual box vm I had ghosted with win 7 image from a physical machine.
Great article!
I had to set lsi_sas and lsi_sas2 to value 0, and ESXi 5 now boots my WHS 2011 install! :) :)
It worked like a charm with ATAPI=0
Thank you so much!
I thought that by End 2012 that would have been resolved in new Vmware, but it wasn't so still very accurate & up to date, works :):)
thank you!
I love you, man!
Your gift keeps on giving... Bless you!
Your gift keeps on giving... Bless you!
Worked great! Thanks a heap. :-)
Gift that keeps on giving!
Wooohooo - Your're the man !
Worked; using a W2k8R2 boot iso to correct Setting of my win7 p2v !!
Thank's alot !
Awesome. I just used this tip to fix a physical machine Windows Server 2008 R2 that I converted to hyper-V using Acronis. One item: unload hive was disabled so I could not perform this step but the reboot worked anyway.
Thanks.
Post a Comment