Generate New Uuid Vmware Is Giving Blue Screen in Windows
That error (INACCESSIBLE_BOOT_DEVICE) generally indicates that the correct hard disk drivers are not installed in the VM; see this VMware KB for options: http:/
Generally, it's difficult to deal with this type of error after the fact, and it's best to ensure the proper drivers are installed before conversion. I'd recommend you retry the conversion and do it directly with VMware Converter, if you possibly can. The above link can give you pointers on how to inject the disk drivers before converting.
Was this post helpful? thumb_up thumb_down
It sounds like a lot of conversion going on there.
On a side note, aren't blue screens usually "hardware" based, meaning the machine is finding something wrong with the hardware it thinks it should have but is being emulated?
Keep in mind, I'm just spit-balling here...
Was this post helpful? thumb_up thumb_down
Gabriell.L
Unfortunately the machine doesn't exist anymore. I do have the original VHD.
Looking into the VMWare link you posted.
Kaato
Yes your right with that one. It is a hardware issue.
Was this post helpful? thumb_up thumb_down
Try putting it on an IDE controller in vmware. Sounds like it's trying to boot off a SCSI controller and it's not liking it.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. 
What OS is it? XP and 2003 didn't really play nice with drastic changes to the hardware (especially CPU types.) You may need to do a Install over-top (dirty install) to get it to boot or you can also try one of the many how-to's to hack a different HAL into OS.)
Was this post helpful? thumb_up thumb_down
No luck with changing it to IDE...
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
FYI - I know it doesn't help you now, but there is free VMware Physical 2 Virtual converter that does a live migration into a full VMware machine - works MUCH better than just doing an image of the drive... It's aware of drivers and hardware and converts a lot of it while it is creating the image so you don't get these type of things when you get it into the VM environment.
Was this post helpful? thumb_up thumb_down
Hrmm, Which vmware product is it? Is there a setting on the storage controller for standard IDE or AHCI?
Was this post helpful? thumb_up thumb_down
DY is an IT service provider.
Can you boot a livecd over the top of it? as in point the vmware cd drive to your livecd.
For example HIRENS CD
If the livecd works - you could use that to diagnose the system.
Could be something like the MBR is messed up - a chkdsk or fixmbr might revive it.
Was the PC shutdown properly before it was converted? I had this issue once - when I went back to the physical PC and shut it down properly -> did the vm conversion and then it worked.
Download HIRENS from here:
http:/
Was this post helpful? thumb_up thumb_down
What VMware product are you using? ESXi? Workstation? You probably want to check the integrity of the vmdk; see if you can add it to an existing virtual machine, and verify that it will at least mount as a secondary drive.
In the past, I've had one or 2 successes (out of multiple attempts) at going in and editing the vmdk descriptor file and the vmx file, and making the appropriate changes there to change the disk type. Not for the faint of heart though.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
It sounds likely the disk is mounting, to get a BSOD, the MBR needs to be valid, the boot loader needs to have started and the Kernel has to be loaded.
Although it is running on VMware - treat it like you would if you took a hard drive out of one computer and put it in another.
- Try booting into safe mode
If it boots into safe mode, check for bangs and replace drivers with new/correct versions
If you can't, try and see what driver it fails on as it tries to boot
- Remove any unnecessary virtual hardware to see if it boots with just a Disk and CPU
- Try putting the disk into another VM and use a BSOD inspector to find out what it can tell you
- Parallel install same OS/new OS and import apps/data you need
- Dirty install over the old one. Not best practice, but there is a reason people do it - it works. Then build a plan to retire as soon as possible - many "repaired" installed have underlying issues that will sneak up and bite you if not resolved.
Was this post helpful? thumb_up thumb_down
Ok. To answer a few questions here.
The O/S that the machine is running is Windows 7 x64.
I am using VMWare Workstation 10.
Yes I can boot a live cd over the top.
Yes the machine was properly shutdown before converting.
Just walked into the office so will begin trying a few things. A question for those of you who mentioned this "dirty" install. Can you please elaborate on this please?
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
Windows 7 doesn't support dirty install (dirty install was the process of installing the OS overtop of a folder already containing the OS.)
Windows 7 DOES have a repair feature though - have you tried this? Also - many of the suggestions we are offering will damage the data if it doesn't go as plan - make sure you have a backup of the files before trying anything offered...
Was this post helpful? thumb_up thumb_down
Righto,
So last night before I left I converted a machine that I had just built up to test a new method of backing up file. I have booted this in Workstation and installed the VM Tools. I powered the machine down and mounted the machine I am having trouble with into the VM. I can navigate around the file system and it appears to be solid.
When booting in safe mode its gets to the CLASSPNP.sys and the BSOD comes up.
Just booted into a Windows 7 installation disc, and after clicking on "repair your computer" it tells me that the O/S is Windows Vista.... Now the machine that was there was previously built by a contractor and due to some of the software on there at the time, they just cloned two machines instead of building them separately. Theoretically if the installer thinks that it is Windows Vista, I could do a "dirty" install?
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
No - Windows 7 will only do Repair, or Parallel install. It's smarter than the old installers - in XP, it would allow you to install to the C:\Windows folder (recommend against it but allow it.) in Vista (I think) and 7 for sure, it moves the C:\Windows folder (and a bunch of others) into C:\Windows.Old before it installs to a new, empty C:\Windows folder.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
Try an SFC (system file checker.)
From recovery command prompt:
sfc /SCANNOW /OFFBOOTDIR=C:\ /OFFWINDIR=C:\Windows
Was this post helpful? thumb_up thumb_down
Thanks Eric. Running the System File Checker now. Will post back when its done.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
Just in case it doesn't resolve the issue - what was the hardware like before when it was physical? Brand/Model of PC.
Also, I do want to confirm - you don't have access to the physical computer anymore, right?
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
If you do still have access to it, here is the link to the VMWare converter I talked about:
http:/
I'm a Hyper-V guy, but one of the things that I envy about the VMWare world is this tool - it's not just a clone of the software, but inspects the hardware for a smooth transition into a VMWare box. It also can be run on another machine and capture over IP to where ever you want the files stored. This avoids the Texas 2-step you need to convert from Physical to VHD then to VMDK.
Was this post helpful? thumb_up thumb_down
It is an HP Z200 Workstation. I have since rebuilt the machine. Also as a side note I am currently testing converting Physical machines to Virtual machines for backup purposes using VMWare vCenter Converter and VMWare Workstation. So far looking good. Will be changing procedure I think.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
what type of CPU(s) does your VMware box run?
Was this post helpful? thumb_up thumb_down
Currently it is running on a laptop that we have as spare. It is an Intel i5 @ 2.40Ghz.
Oh and SFC finished and reports no problems.
Was this post helpful? thumb_up thumb_down
Eric M This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
You could try going into the VMware bios and changing the HD controller to IDE mode (instead of AHCI.) This is something that can fix this if it was a physical machine... Not sure on VMware Workstation how much control you get over your emulated hardware though... Also, try turning off any features you don't need (Com Ports, LPT Ports, etc.) Less is better.
Was this post helpful? thumb_up thumb_down
Ok so I after booting Hirens Boot CD, I managed to get the "Windows 7" logo to come up when booting. I had to choose the "Boot Windows Vista/7 (BOOTMGR) from hard drive" option but it still BSODed me.
Was this post helpful? thumb_up thumb_down
DY is an IT service provider.
Did you get the same BSOD error?
I would try the below tool - it is on the HIRENS CD
It will help you work out which driver is failing - might give you enough info to disable the driver - replace the file etc.
http:/
it will do the following (pasted from site):
This tool scans minidump files found in C:\Windows\Minidump folder for BSOD (blue screen of death) crash information and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen, and the details of the driver or module that possibly caused the crash.
You can view the details of the device drivers loaded during the crash in the lower pane. It also mark the drivers that their addresses found in the crash stack, so you can easily locate the problem drivers that may caused the crash.
(Download Size: 65 KB)
Was this post helpful? thumb_up thumb_down
Damien665: I have just solved my problem. After some looking around I found vhd2disk (http:/
Thanks to everyone for all your help!
Have a good Weekend!! (It's Friday here!)
Was this post helpful? thumb_up thumb_down
DY is an IT service provider.
Sweet - just in time for the weekend :)
Was this post helpful? thumb_up thumb_down
mcelhonedidne1993.blogspot.com
Source: https://community.spiceworks.com/topic/419873-help-need-to-boot-a-vmdk-vhd-but-it-blue-screens