Install Windows 10 as Virtual Machine in VMware Player  

Thank you for the link Brink. I will try to download a new copy and I will tell you if that solves the problem.

Does not VMWare Player require to disable Windows Hypervisor? I see no mention for this in the tutorial.

VMWare Workstation requires the hypervisor in Windows to be disabled before running it or it will break the whole VMWare and has to be reinstalled. This has been the case since Hyper-V got included in Windows.

Here's how to do it:

Open Elevated Command Prompt and type in the following one line at a time:

bcdedit /copy {default} /d "Windows With Hyper-V"
bcdedit /set {default} hypervisorlaunchtype off
bcdedit /set {default} description "Windows With VMWare"
bcdedit /timeout 2

Now, when you start your computer and you need VMWare Workstation, then just let the timer run out in the boot selection screen or press Enter.

If you want to use Hyper-V, then select the second boot entry and press Enter. Now you can run Hyper-V.

WARNING! If you accidentally boot into Hyper-V mode and then start VMWare Workstation, the application will break and you have to reinstall it in order to getting it working again. This is also the reason why the VMWare boot option is set as the default one, so that you know that you are in VMWare mode in cases you missed the boot option selection screen. Hyper-V will not break if you are in VMWare mode, it will just not start any virtual machines.

Please add this info to the original tutorial in this thread as I think it is important and very relevant and saves the VMWare user from a lot of headaches.

Awesome! Much better! I love the tutorials collection found at TenForums. It's HUGE!

Excellent tutorial and video. But I just can't get to the step where the Windows logo appears for the install. Instead, a message appears "unsuccessful", "no media". No way to get out of the message, so I wait. Then the message goes away and the blue setup options appear, which is of no help. Did a google and many other users have this same problem. Their print screens are the exact same as what my display is showing.

I know I have the iso in the virtual cdrom and ticked to power on. I followed the settings exactly in both the tutorial and video. I have tried so many times to make a successful virtual machine that I have all the steps memorized. Tried using Oracle Virtual Box with the same iso files, and windows installed quickly and easily. But Vmware would be my preference if this problem could be addressed. Any suggestions? Especially as there are so many users having the same problem.

I am using VmWare Virtual Player 16 and also the Workstation 16, same results with both.

I think I discovered why I was having so much trouble getting a virtual created. My computer is older, and has "bios" rather than "uefi". The default in creating a new virtual machine is "uefi". When I started choosing "bios" then it worked everytime.

Kim Parker said:

I think I discovered why I was having so much trouble getting a virtual created. My computer is older, and has "bios" rather than "uefi". The default in creating a new virtual machine is "uefi". When I started choosing "bios" then it worked everytime.

Most VM systems have no problem creating Virtual Machines with UEFI and even secure boot on ordinary old MBR Bios machines.
You set the VM "boot mode" in the Virtual Machines configuration file = i.e the "Virtual BIOS" not in the MOBO's physical BIOS.

For example --here's an extract from a VM I'm running on VMWare WKS Running W2K22 Server as a VM.

Code:

 

!/usr/bin/vmware
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "18"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "Windows Server 2022.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
displayName = "Windows Server 2022"
firmware = "efi"                                       
uefi.secureBoot.enabled = "TRUE"        ############################################
guestOS = "windows2019srv-64"          ############################################
tools.syncTime = "FALSE"
sound.autoDetect = "TRUE"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"
sound.present = "TRUE"
numvcpus = "2"
vcpu.hotadd = "TRUE"
memsize = "2048"
mem.hotadd = "TRUE"
sata0.present = "TRUE"
nvme0.present = "TRUE"
nvme0:0.fileName = "Windows Server 2022.vmdk"
nvme0:0.present = "TRUE"
sata0:1.deviceType = "cdrom-image"
----

Cheers
jimbo

Most VM systems have no problem creating Virtual Machines with UEFI and even secure boot on ordinary old MBR Bios machines.
You set the VM "boot mode" in the Virtual Machines configuration file = i.e the "Virtual BIOS" not in the MOBO's physical BIOS.
--------------------------------------------------------------------------
I don't find it necessary to muck around in the physical motherboard to create a virtual machine.
I always select settings in the Virtual Vmware Workstation program only.

I tried going through the steps again just now using VmWare Workstation Pro. As usual, I am always successful when ticking "BIOS" in the Virtual Machine Settings.

But I tried "UEFI" just now too and it did boot up with the "press any key". But if I didn't hit any key soon enough then it thought about it for a long time then went into that set-up screen and just sat there, the same screen found on a physical install of Windows. I found that if I selected the cd/dvd option then it would boot up again with the "press any key" and as long as I hit any key in time then it would start installing windows.

The interesting thing however - selecting virtual "BIOS" in the creating a virtual machine does NOT require pressing any key when the new machine boots up.

I think the reason I was having so much trouble before, my O/S was due for a new install. Which I am running now, and no problems at all. I almost fell off the chair when the UEfI booted up successfully!

I got the hang of installing virtual machines (use both Player and Workstation). As I boot from an ISO in the CD-ROM, I would like to make this the default but so far haven't been able to. It's not that hard.

However, I think my physical went to that great computer hospital in the sky. The display wasn't what I wanted, tried to change it with Nvidia. That was a disaster, didn't know what I was doing, but I tried. After that all words were too faint to see well. Also fuzzy.

Searched a little, and a corrupted netframework could cause this. Couldn't fix that got an error "unhandled exception".

Ok then, I'll just make a virtual to put on my portable Sandisk SSD (keyhole) while I gather everything I need for a new install on the physical.

But to do this, I have to install from the virtual CD Rom with the ISO, it is powered on then I have to press enter so it goes to the boot screen. I would like to set this so it always boots from the CD, not sure how. I know to go to change boot order, but I am not sure how to make the boot order "stick".