VMware Cloud Community
johnnymordoc
Contributor
Contributor

Need to P2V Windows 10 Surface Book Pro - Keeps attempting startup repair

Folks,

We have a Windows 10 Surface Book Pro that we are attempting to P2V.

We are using the stand-alone client and after the process completes we go to startup the machine it keeps looping on the Automatic Repair with no resolution.

Please advise.

Thanks.

-JJ

Reply
0 Kudos
12 Replies
POCEH
VMware Employee
VMware Employee

Converter doesn't support Surface Book and never tested with.

The problem should be with some kind of hardware/drivers, could you upload log bundle for check?

Reply
0 Kudos
johnnymordoc
Contributor
Contributor

In reviewing the logs it appears to be that the ntoskrnl.exe is corrupt.

I have attached the error.

Any  thoughts?

Please advise.

Thanks.

John

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

I've meant converter logs. Smiley Happy

Reply
0 Kudos
johnnymordoc
Contributor
Contributor

Where can I find the converter logs?

Please advise.

Thanks.

John

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

Export log bundle from Converter UI or %ProgramData%\VMware\VMware vCenter Converter Standalone\logs folder.

Reply
0 Kudos
raghushetty
Enthusiast
Enthusiast

I'm not sure but.. try to disable secure boot control from the bios and try once ..

Reply
0 Kudos
johnnymordoc
Contributor
Contributor

I was able to find the bundles folder.

What log do you need - they all seem to be zipped.

Please advise.

Thanks.

John

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

Whole log bundle?

Reply
0 Kudos
johnnymordoc
Contributor
Contributor

Hopefully these will help.

Thanks.

-John

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

In the first place I'll try to skip recovery partition. In the second place try to remove hardware like Wifi, Nvidia, Cisco, and any other specific for your device. Try to remove anti-virus etc too.

HTH

Reply
0 Kudos
aadi369
Enthusiast
Enthusiast

Before converting the machine using P2V, try to run sysprep on your surface device and try again. If possible, run the chkdsk utility on the source server before attempting to convert again.

However, this issue can occur if there are bad blocks on the drive or corrupted files on the source system.

----------------------------------------------------------------

If it is useful, plz mark answer as correct or helpful.

----------------------------------------------------------------

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

This is not the problem here!

Reply
0 Kudos