Windows 10: Install Windows 10 as Virtual Machine in VMware Player

It never hurts to pay more attention to details when going to look over any support information! *Thumbs

So you tried DOSBox on a VM and got results? That shouldn't come as any big surprise since DOSBox is a relatively basic form of emulator in comparison to other programs. It works on the sand box idea of isolating the old dos app from the NTFS platform in order to provide the Fat8, Fat16, Fat32 type environment.. I couldn't say if you would see the same with another vm program however as you saw with VM ware's latest Workstation Player.

 

Yeah, I frequently amaze myself with a new discovery then find out that other people consider it old news.*Smile

 

Well the field of virtualization isn't exactly anything new. MS had developed the Virtual PC 2007 with Vista in mind after VM ware got it's own early start. Oracle's VirtualBox also made it's own first appearance soon after.

I first ran the VMs back while 7 was still in beta form and MS had come out with the XP Mode in hopes of seeing more businesses make the upgrade move at the time since that would allow them to keep running all the old XP apps. VM ware's goal was to cover all OSs being a virtualization software company to begin with and with the Fruit company coming out with the Wine app MS had to make another move bringing in Hyper-V first with 8.

Competition does tend to see some better ideas put to use! What VM ware apparently did here was replace the free with free with option to buy to allow an improvement for the program the home user as well as commercial user would see. When you see the Pro designation then you know the edition is the full featured that includes support for things like virtual servers and the more involved type of project type supports the commercial end user sees.

And yet with all that Virtualization is still only a relatively recent field opened up. So when first taking a look at this time things will look new. Recent as in the last 15yrs. that is. The cpu support took a bit longer now only about 6-7yrs. approximately when both Intel and AMD were coming out with new model series.

 

Hello. I am stuck on step 17. When I open the DVD Drive: VMware Tools all I have is folder Program Files without the rest including setup.exe file that I need to choose. Please help.

 

Hello Monca, and welcome to Ten Forums. *Smile

Where did you get the Windows 10 ISO file from? You may need to download a new copy to use in the VM.

https://www.tenforums.com/tutorials/9...-download.html

 

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

 

A bad download or of more often simply seeing bad installs for just about any software are not uncommon with the second fresh install usually being the solution. Sometimes it takes a few additional install attempts to see a stubborn program actually go on however.

One thing you will want to do is disable your av program and any other protections temporarily disabled when going for the second install in case one of those was the reason it didn't go on the first time. That will also prevent any disruptions even if that wasn't seen at all but to be on the safe side.

 

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.

 

Hello @slicendice, *Smile

I added a warning at the top of the tutorial for this below to help with this. Thank you.

https://kb.vmware.com/selfservice/mi...rnalId=2146361

 

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