So, you chose to poke around in the VMWare Bios (by pressing F2 during boot), but there is nothing that looks like it could help. A bad patch? This error is documented quite a bit, but most people seem to have had problems with a Windows update, not VMWare Converter. If you poke around in the problem details, you will find something like this: Bad patch error The next time you boot, you are still stuck in the Startup Repair console. You can select to view the advanced options for system reovery and support, start a command shell, access the file system on the disk, run chkdsk, fixboot, and fixmbr, all with the correct parameters, but it will not change anything. Alas, after some churning it throws an error: Startup Repair fails You are still optimistic that Startup Repair will fix it An invitation to launch the Startup Repair console appears. When you boot the VM, a blue screen is briefly visible, but too short to actually read what it says. You get booted into Windows Startup Repair, and after some churning it tells you that it cannot repair the problem? And no amount of Googling for any of the error messages that you see in the process brought up a solution? There may be a really simple one, if your issue is the same as the one that I just solved.īut before I get to this, I will describe the symptoms that you have likely observed. Now you want to start the VM, but it throws a blue screen with a cryptic error. So I added the disk image to an other Windows Seven virtual machine, let’s say as the G:\ drive.Symptoms: You used VMWare converter to create a VM from a physical Windows machine. Although I’m sure it’s possible, I’ve not been able to do it from the recovery console. If, as I did, you forgot to enable those drivers before creating the disk image, it’s possible to do it after. I don’t know which one of ControlSet001 or ControlSet002 so I edited both. I’m almost sure that intelide is not required if you setup the virtual disk as a SATA device. I guess that 0 mean enabled and 3 mean disabled.
It’s easier to enable the drivers from the physical system, before creating the disk image. The created image can be used in Virtualbox, but before doing so some disk drivers may need to be enabled else you’ll get a BSOD with: STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE)
Save the image of a disk, on the disk it self.Create a unencryped VM of a Bitlocker encrypted physical machine.
It’s a great piece of software because it work at file system level so it can: I’ve just converted a Windows Seven physical desktop to a virtual machine using VMware converter.
0 kommentar(er)
