VMware Communities
EVPSupport
Contributor
Contributor

Blue screen after conversion with VM converter stand alone 6.3

Hi,

I converted a windows 10 physical PC using converter 6.3 (latest as of today). 

The conversion went successfully to 100%, w/o any problems.

Howerver, the vm does not boot. It stops quickly with Blue Screen System Thread Exception not handled.

EVPSupport_0-1673000917708.png

 

In the repair environment, I first tried to boot into safe bode (with console only) - blue screen

However, I could select the repair console - it accepted my vm windows credentials.

Here are my findings :

EVPSupport_1-1673001188153.png

 

(It boots from volume 0, Windows is installed on volume 1)

EVPSupport_2-1673001211245.png

EVPSupport_3-1673001218923.png

EVPSupport_4-1673001235355.png

 

I was wondering why the converted volumes both had a letter assigned (c and d).

Here is the original BCD from the physical PC. It looks like this:

EVPSupport_5-1673001329562.png

 

I tried to boot on 2 different machines with 2 different BIOS and CPUs - no change.

I then used DISKPART to remove the letter from the system volume and assigned a "c:" letter to the Windows volume.

BCD looked now excatly like the original from the physical PC.

However, after the boot crashed again, I checked with BCDedit and the C,D letters were set again as it was at the beginning.

I also tried chkdisk on c: and d: - no errors were found.

In vm settings there is only 1 CPU selected. I tried with 1,2,3,4 cores - no change.

 

Now I have no more ideas why this vm will not boot.

I ran out of ideas - Please help!

 

 

 

 

 

 

 

 

 

0 Kudos
9 Replies
Yttrium
Contributor
Contributor

Hallo, 

possibly you shoul try the Neustart with 'drivers only'.

Next thing you could check the BIOS settings of the converted machine. If the start sequence is too fast, enter bios.bootdelay = "5000" in the vmx file (backup it first!) to have enough time to access.

MfG!

0 Kudos
EVPSupport
Contributor
Contributor

Thanks for your answer. 
unfortunately, no change.

0 Kudos
RDPetruska
Leadership
Leadership

Did you run the second step of the Converter?  The first step/stage is creating a virtual machine and imaging the existing disk into the virtual environment.  The second step is reconfiguration of the disk for the boot drivers, etc.

0 Kudos
EVPSupport
Contributor
Contributor

Yes I did. Out of the four checkboxes the last two were selected:

 

Install VMware Tools on the destination virtual machine

Customize guest preferences for the virtual machine

X Remove System Restore checkpoints on destination

X Reconfigure destination virtual machine

0 Kudos
Yttrium
Contributor
Contributor

Have you started the converted VM on the same PC?

0 Kudos
EVPSupport
Contributor
Contributor

Yes, I tried the same PC and also another, completely different PC. No change - same blue screen error.

0 Kudos
Yttrium
Contributor
Contributor

Some settings possibly to be checked at the setup before start conversion:

- post conversion and 

- selection of virtual disk 1

 

0 Kudos
EVPSupport
Contributor
Contributor

hi,

virtual disk has converted well - no error, everything is there. A bit strange are  just the drive letters. Originally Windows is on C: and the System/Boot partition has no letter (see above). 

As mentioned  I ran the post configuration with the last 2 checkboxes set. The convert and post configuration jobs went well, no errors.

I hope that some guru from vmware can jump in and help us out here as this is very strange.

 

thanks!

 

 

0 Kudos
EVPSupport
Contributor
Contributor

I ran the conversion again, tried all the options, but still the same blue screen arrow. This is really frustrating.

No one able to help? 

0 Kudos