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:
http://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:
  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!

87 comments:

Valeriy said...

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?

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)

Thx!

Anonymous said...

Brilliant. Thank you sir!

Anonymous said...

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

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

Thanks.

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!

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

Mate...you'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

Anonymous said...

GREAT!

Checking these settings worked for me!

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Unknown said...
This comment has been removed by a blog administrator.
Stone Gallery said...

Tanks. Você me ajudou muito, valeu mesmo...

Anonymous said...

I <3 you! Can I buy a e-beer or something...

Anonymous said...

Excellent Boss. It worked. Thanks.
I used lsi_sas to start to 0.

Anonymous said...

MANY THANKS :)

This worked for me, in Oracle Virtualbox set the controller type to LSI_SAS then just changed the start variable from 3 to 0 for the LSI_SAS service. Winner, much appreciated.

Anonymous said...

A MASSIVE THANK YOU to all the comments on the issue....

I P2V my W2k8 srv onto HYPER-V 2012R2 and it DIDN'T boot. I tried to fix this issue until 2:00am, and gave up thinking I needed to re-think my plan/migration.

I can across this information, and all I can say IS YEEHAW, ride em cowboy.

I can't thank you enough..... MY EFFING server is now working !!!!!!!

Thank you MASSIVE!!!!!!!!

Unknown said...

How this is not the #1 answer for Virtualbox 7B errors I have no idea. It's very technical, so maybe side-loading the registry is too scary for some people. But after 16 hours of trial and error with everything else under the sun, I found this site and had my Windows 7 VM running in about 30 minutes!!! Thank you SO much!

Paul said...

Fantastic post, thanks a lot.

I was moving a Windows 7 64 bit VM from Virtual Box (v4.3.28) to VMware ESXi 5.0.0, had to set LSI_SAS start to 0.

Mar said...

The Angels singing :) Thank You

Anonymous said...

Just wanted to post many thanks! The Misani forum is down, so this blog post and the comments helped me fix my Hyper-V P2V issues.

Anonymous said...

FIXED MY ISSUE AS WELL! THANK YOU!!

Mandrake said...

I had exactly this problem trying to get a P2V Windows 7 install up that I no longer had access to the Physical Disks, just the vhd created from disk2vhd ages ago. I knew the likely problem and was just searching the net for the process that you so kindly detailed. Thanks Dude!

From just another thirty-something fiscally conservative yet socially liberal married suburbanite with 2 young kids, 2 dogs, an hour commute, and bunch of nerdy hobbies. (There are likely more of us than we realise)

Anonymous said...

Upgraded to Windows 10 on a new disk and wanted to convert my old disk to a VM. Your fix allowed me to boot it up so thanks for that!

Cheers!

Anonymous said...
This comment has been removed by a blog administrator.
Unknown said...
This comment has been removed by a blog administrator.
Anonymous said...

Thanks Andrew, you saved my Christmas! :-)

Anonymous said...

First comment of 2016 and this is still the best solution I have found.

Absolutely fantastic!! I tried the intelide setting and it didn't work, then I went through the whole list. It tuns out atapi = 0 went ahead and let Windows boot up. It took a few moments but the fact that it didn't immediately BSOD and reboot I waited patiently and.....the Angels sang in 2016 bruh!

(Windows 7 x64 laptop, AHCI boot, converted to VM used on Gen1 Hyper-V Windows 8.1 [will be transferring to a sever later today]).

Thank you soooo much.

Anonymous said...

Thank you, Thank you, Thank you. LSI_SAS to 0 was the fix for me. This post was the only place I've seen these keys mentioned. Great work.

Anonymous said...

March 6, 2016. Still valid.
Performing a restore from a backup of a physical machine to a VMware virtual. After successful restore, VM would BSOD. Followed your guide and had to change LSI SAS from 3 to 0 and the restored VM powered on and is running!

Administrateur said...

Many thanks :)
I had to set lsi_sas and lsi_sas2 to value 0 too after P2V

Anonymous said...

Thank you very much.... You just saved my day... or my week :)

Thanks a lot

Anonymous said...

THANK YOU THANK YOU THANK YOU!!!!!

Anonymous said...

After day n half banging my head on p2v windows 2003 conversion, your solution worked. This bud for you :)

Thanks!!!

simonation said...

still valid - thank you sir!

Like others i needed to set lsi_sas and lsi_sas2 to value 0 and it then boots!

Anonymous said...

You saved my life!!!!!!!!!!!!!!!!!!

Anonymous said...

Awesome work!!!! This is always an issue for me going from P2V. I set the start value to zero for a number of values and it finally worked. Is there a way to definitively know exactly which driver/controller is the issue (in advance or afterwards? I remember using sysprep before, vbs based system prep and ACPI drivers in the past. Doesn't seem to be a straightforward way to fix this in every similar situation. The reference link seems to be dead unfortunately. Thanks again for the help!

Ian AT said...

Just tried this on a Hyper-V machine that was blue screening. You are genius it worked a treat :)
how ever I used the below as intelide was set to 0
Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Dashrender said...

Well like the first guy in 2016, I'm singing your praises in 2017!

Thanks a lot for making this post - took me 4 days to find it, but it works.

Anonymous said...

Excellent worked for me but had to locate the SCSI driver and change that from 0 to 3 also did the IntelIde file from 4 to 0. - Thanks

Unknown said...

You could also just boot into Win7PE then use the DriverInjection app (Google DriverInjection.exe) to inject the appropriate controller driver into the system hive. Worked well for me when needing to install and change the storage controller on a P2V ESXi Server 2003 VM. You'll need the txtsetup.oem file for the driver you're looking to install, however.

-Gray Fox

Anonymous said...

This worked for me also

atapi to 0 fixed my problem.

many,many thanks

Anonymous said...

You Legend - I have read so many damn posts starting at UEFI GPT and end at MBR Bootmgr then Bluescreen aaarrrrhhh pain! and yours finally worked for me!
The force is strong with you! ;-)
Thanking you from Edward!

Anonymous said...

Worked for me, thank you Sir!

Best Regards, Marc

Anonymous said...

If you are using recovery mode, you'll likely want to open regedit and then open the correct hive from your source disk. HKLM\SYSTEM here's an article on how to do that:

http://www.winhelponline.com/blog/edit-registry-offline-windows-re/

Unknown said...

Paragon released a tool that was still free until 2010. It was called "paragon adaptive restore". If you can find the freeware version then this tool automatically sets the storage (and other drivers such as troublesome VGA) to "defaults".

Sorry for gravedig but this is still high on google results for p2v 7b errors

steve heller said...

This is still valid today, although for some reason the Shift-F10 trick to get into the command prompt didn't work. I had to cancel the automatic repair, then use the "advanced options". But after that it was easy.

Thanks!

Anonymous said...

Just wanted to post and show my appreciation for helping me fix this issue!

had this issue when trying to P2V a hard drive from a failed raid controller.

Jullez said...

Thank you!!!! 72 hours later..and this fixed my issue!!!

Anonymous said...

For me Works this:

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Unknown said...

Still relevant even today. Changing "start" worked like a charm, and now to just figure out how to get the rest of this machine to cooperate.

DSvegad said...

Friend,

You save my days and "JOB"
I did all these settings

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

and

megasxxx = 0

it worked

Thanks a Lot...

Harald said...

Worked for me too

Thank you

happymeal00 said...

setting LSI_SAS to 0 worked for me with exporting a windows 7 x64 machine from virtual box to Qubes-OS. Version 4.0RC3 uses the mptsas1068 SCSI controller which is loaded by windows only when LSI_SAS is set this way.

design said...
This comment has been removed by a blog administrator.
Anonymous said...

atapi=0 worked for me too! Thank you very much!

Chris said...

Champion


You just saved me a weekend of HURT because I could not boot a (retired) SBS2011 vhd.

i knew there would be a simple fix, just wish I found this page 18 hours ago

Anonymous said...

This is awesome and would like to say big thank you to Andrew. you save me huge times ....

The LSI_SAS changed to 0 fixed my issue - I had a look on my vm and the SCSI controller set LSI Logic SAS which makes sense with the changes.

Anonymous said...

Great thank you, solved.

cybacolt said...

Windows 7 SATA -> VMWare Converter -> Virtualbox here -

made sure VMWare converter was set to 'SATA' controller on conversion, and left Virtualbox as SATA controller with AHCI type.

The only registry setting i had to change to get it to boot was msahci to 0.

thanks for the article, and all the comments!

VanBond007 said...

Bing, bing, bing! Migrated a 32-bit Win7 Ultimate from VBox 6.1 to kvm.

Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3

Feexed!!!

Anonymous said...

8/31/2022, 3 AM, this is still relevant, and saved my bacon.