I used Starwind V2V converter to convert my PC disk C:/ -uefi i think 2017 custom PC- to Vmdk file
I have Vmware Workstation pro, 15.x
What choose during create VM from existing vmdk
Uefi or bios
Convert to new format or Not convert at the end of creation
?
Please reply ASAP
I gave this cmd
bcdboot C:\Windows
when booting in VM from ISO Windows 10 2004, and went in cmd prompt
Now boots OK
UEFI or BIOS - what was the source system using?
Convert to new format - do you plan on using the VMDK on any old version of Workstation?
I HAVE COPY OF VMDK
I USED THE COPY FOR
Source system UEFI - used UEFI
I HAVE NEW WORKSTATION PRO AND NEW FUSION - used convert to newer format
CHOSE UEFI AND CONVERT VMDK
BUT getting first:
20200903_164303.jpg — Yandex.Disk
after:
20200903_165251.jpg — Yandex.Disk
Not boots the VM
in VMWARE WORKSTATION PRO 15.X
can you help???
I can Not insert a photo in here the forums so provided URLs [getting error]
and sometimes getting
No bootloader found
what to try ???
I used to boot the VM from the same machine I got the vmdk from... may have conflicts????
I just uploaded a video see here:
VM can Not boot up // SEE ERROR AT 05:27 & 06:27 in the video
2020 09 03 16 34 38 vmware open vmdk - YouTube
in the video at 01:47 UEFI / OR / BIOS ????
in the video at 04:05 CONVERT TO NEWER FORMAT ????
WELL...?
I used to boot the VM from the same machine I got the vmdk from... may have conflicts????
We dont know the content of your vmdk - so at the moment we can only guess ...
To get the required info I would suggest you attach the converted Starwing-vmdk to your Ubuntu-guest and boot into Ubuntu.
It sure has gparted .... show us a screenshot of the partitiontable in that vmdk.
It may have have an EFI-boot partition or it may not - gparted should show that.
Once we know that - next show the content ofthe efi-partition in case there is one,
If there is no efi-partition look at the flags set for the the Windows C: partition.
Is C: a primary partition and is it set active ?
you say:
"
We don't know the content of your vmdk - so at the moment we can only guess ...
"
is my C:/ drive - c:/ disk converted[with starwind v2v converter], with recovery partitions
PLEASE REPLY - ANY POSSIBILITY OF CONFLICT:
I HAVE boot the VM[VMDK - CONVERTED FROM MY C DISK], from the same machine I got the vmdk from... may have conflicts[the UEFI - same c:/ disk signature???] the actual c:/ with the vmdk/c: ????
Moderator: Please stop using ALL CAPS in your posts, there are bold underline and italic options if you need to highlight any text.
Sorry for the caps
Basically if do a vmdk of C:/ Disk and all disk C partitions - Windows 10 to external hdd
Can run as VM this vmdk in Vmware Workstation pro or player in the same PC ?
Or may VM Not boot, due to conflicts with actual Windows 10 ?
I think Windows 10 Pro in C:/ source disk was UEFI Since when enter uefi i can use mouse for operations in uefi/bios
Exist possibility for conflicts between host and guest? During creating from gile.vmdk i chose uefi... well?
I HAVE boot the VM[VMDK - CONVERTED FROM MY C DISK], from the same machine I got the vmdk from... may have conflicts[the UEFI - same c:/ disk signature???] the actual c:/ with the vmdk/c: ????
if try load vmdk file - Windows 10 Pro - in my macbookpro Catalina os, in Vmware Fusion, choose UEFI or BIOS during create from existing virtual disk?
So do you have Workstation or Fusion?
If your existing computer used EFI, then the virtual machine created from that hard disk should also use EFI.
I have both a macbookpro catalina 2016 15" with Fusion latest i think of 2019
And Windows 10 Pro desktop PC with Vmware Workstation pro 15.x
So try in macbookpro, choosing UEFI? Again choose UEFI in Fusion?
May in PC have conflicts guest boot loader with host,...?
Hi,
Or may VM Not boot, due to conflicts with actual Windows 10 ?
You keep asking that question and as nobody answers it...
There won't be a conflict with your physical host. The VM never sees the physical disk and there's no issue with disk signatures whatsoever.
There might be a Windows licensing issue, but that's another matter.
If you want to make progress here then answer Continuum's questions as without that it is all just guesswork.
--
Wil
I enter BIOS/UEFI and after used the mouse, so system UEFI... Choose UEFI or BIOS During Create VM from existing virual disk?
VM vmdk file created with Starwind v2v converter
Here says choose BIOS... What to choose?
https://forums.starwindsoftware.com/viewtopic.php?f=15&t=5632&p=31528#p31528
continuum Sep 3, 2020 5:15 PM (in response to lse123)
We dont know the content of your vmdk - so at the moment we can only guess ...
To get the required info I would suggest you attach the converted Starwing-vmdk to your Ubuntu-guest and boot into Ubuntu.
I attached vmdk (win 10 Pro) to Ubuntu VM in Vmware Workstation Pro 15.x, here is it :
It sure has gparted .... show us a screenshot of the partitiontable in that vmdk.
It may have have an EFI-boot partition or it may not - gparted should show that.
Once we know that - next show the content ofthe efi-partition in case there is one,
If there is no efi-partition look at the flags set for the the Windows C: partition.
Is C: a primary partition and is it set active ?
How to understand that c:/ is active???
I connected Windows2004.iso as DVD DRIVE Boot from DVD but
I can Not Repair getting: // the PC I did P2V [StarWind v2v converter] is problematic - can Not update Windows since Jan 2020, and also Programs Not install can nor update, says something is installing when do go to update/install any App... I did the P2V so as, having old system as VM, and after doing a RESET of Windows 10 Pro... What to do now???
Do you know what to try, getting: // ...?
diskpart screenshots see below
Any hint of what to try????
Vol 3 in my case is the efi partition? How find efi system partition
?
https://docs.microsoft.com/en-us/win...ons-techref-di
Repair the system partition
If the system partition has been corrupted, you can use BCDBoot to recreate the system partition files by using new copies of these files from the Windows partition.
Boot your PC to a command line. For example, boot to the Windows installation disk and press Shift+F10, or boot to Windows PE (WinPE: Create USB Bootable drive).
Use Diskpart to determine which drive letter contains your Windows partition and system partition (diskpart, list vol, exit).
Optional: Format your system partition: format (drive letter of your system partition) /q
Add a boot entry for your Windows partition: bcdboot D:\Windows
Reboot the PC. Windows should appear.