Flickr Badge

My Flickr Photostream

Thursday, October 08, 2009

STOP 0x0000007B on P2V'd Windows 7

I have neglected this blog terribly, but I wanted to get this out there because I know I'll forget and I know others will find it useful.

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:

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:
  1. Mount the Win7 DVD in VMware Player and boot to it.
  2. At the first screen (Language Selection), hit Shift-F10 for a command prompt.
  3. Run Regedit.
  4. Load the system hive from the VM's disk:
    1. Highlight HKEY_LOCAL_MACHINE
    2. File > Load Hive
    3. Select &lt c: &gt \Windows\System32\config\system (name it something like "asdf")
  5. Expand HKEY_LOCAL_MACHINE\asdf\ControlSet1\Services\intelide
  6. Change the data for value "Start" from "3" to "0".
  7. File > Unload Hive.
  8. Exit regedit.
  9. Reboot the VM.
Voila! Hear the angles sing!


Valeriy said...

what if its already 0 ; i changed it to 3 and both ways i still can not bootup my windows7.
Any ideas please?

IT_Frank said...

Thank you very much,

This fixed my problem and it worked.

Well done !!!!

Fabrice said...

your are the king!

Jeff said...

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?

Andrew Cohen said...
This comment has been removed by the author.
Andrew Cohen said...

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.

Matt said...

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.


BSJ968 said...

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

Kevin Jackson said...

Worked. Thank you sir!

Anonymous said...

Fixed my driver mismatch issue.

(AHCI physical vs IDE Virtual)


Anonymous said...

Brilliant. Thank you sir!

Anonymous said...

Saving atapi to 0 fixed my problem. Thanks for your help.

Emil Zegers said...

Thanks, thanks, thanks, more than brilliant. The atapi=0 did it for me. You really made my holidays!

Anonymous said...

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.

Anonymous said...

Great article!

I had to set lsi_sas and lsi_sas2 to value 0, and ESXi 5 now boots my WHS 2011 install! :) :)

Momaweb said...

It worked like a charm with ATAPI=0
Thank you so much!

Anonymous said...

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!

nippertje said...

I love you, man!

Anonymous said...

Your gift keeps on giving... Bless you!

Anonymous said...

Your gift keeps on giving... Bless you!

Anonymous said...

Worked great! Thanks a heap. :-)

Anonymous said...

Gift that keeps on giving!

DaHude said...

Wooohooo - Your're the man !
Worked; using a W2k8R2 boot iso to correct Setting of my win7 p2v !!

Thank's alot !

Darren said...

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.


Anonymous said...

Thank you so much!

In my case I had a VMWare vdmk file which I was trying to boot with Virtualbox.
I had to change the registry set MSAHCI key (hklm\system\ccset\services\msahci) START from 3 to 0(zero).
This change allowed to boot with the generic Windows sata drive.

Anonymous said...

Did what BSJ9868 suggested and this worked, thank you both.

Anonymous said...

Thanks!!!! You are my hero!

James Martin said...

IF this does not work, and you are using virtual box, simply edit the settings and remove the virtual drive from the sata controller and add it to the ide controller. Virtual box adds virtual disks to the sata controller by default. Worked for me!

Anonymous said...

Thank you. 2013. still valid. )

I had p2v a workstation win 7 and it could not boot. AHCI enabled.

after setting as in BSJ968 post,
it booted.
I think i love you...

Shepparton PC Doctor said...

Andrew, you are a superstar! Thank you :) This fixed it for me - now my client has a working VM of an old, dead PC! Yay.

Shepparton PC Doctor said...
This comment has been removed by the author.
Anonymous said...

The angels sing!

Anonymous said...

awesome thank you ever so much

Anonymous said...'re a champ!
I was using virtualbox and changing MSAHCI to "0" did the trick just as Anonymous said on 7/13/2013 12:14 AM.
Thank you sir!

Anonymous said...

Thanks a lot!

Did a P2V WHS2011 to ESXI 5.5.0

Got around the BSOD changing:
"LSI_SAS" ot 0