W10 VM in a Server VM

Installing Server  2019 on Hyper-V  Virtual Machine.

This workshop does not require you to activate the software.
The only limitations are, that you cannot change the desktop and you cannot set the sleep mode.

Read the whole article before you begin.

Your PC must have a 64 bit Windows 10 Pro installed with 8-16gb internal memory.
You can upgrade
from Home to Pro.
See of virtualisation is present and enabled in the BIOS

For the Hyper V is a separate partition created of 50 GB
Total 3 partitions
C: O.S.
D: 50 gb with a folder called VM-1
E: for the data
We're going to install Windows 10 version 1607 and if that all works then we'll create an image of that which will then reside on E.
Should the VM upgrade to the latest version then we can restore the Windows old file, but if necessary also the image.

Run the following command in Powershell as administrator.

DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

Or type turn windows features in the searchbox.

Check Hyper-V

Go left to start and search in the list.

Pin to taskbar

Download the ISO from a server installation

Set the ISO were you want. In this case on the D.
Create a new empty folder with the name VM-1 on a partition with more than 40 gb free space.
In this case on the D.

The installation.
Start Hyper V Manager
Hyper V and that VM need to be installed on 1 location in the same network
Click on Virtual Switch manager
There may only be that default switch.

When there is allready a new switch you have to remove it.

Then click on New Virtual Switch
External network
Apply, OK

Choose new virtual machine

Chance that name New Virtual Machine in something else as VM-1
If you don't change that default name, then that seems to be the reason that the VM remains attached to the virtual default switch with the IP range 172.20... instead of 192.168... and the wrong subnet mask of

On the machine with the VM
Network IP in the right IP range  and a Default Switch with the wrong IP range.
But this is normal because the host machine with the VM shall not find the new virtual switch.

On the VM
The default switch with the wrong IP address and subnet mask.
The new switch with an IP address in the right IP range.
And also has internet.

That VM has to use the same IP range as your laptop or computer.
For that, you are also going to set up a new virtual switch that will (hopefully) be attached to your network card with the correct IP range.

Change the memory to 4500mb
Make not the mistake to choose the default switch
Then it will use the wrong IP range started with 172..

Choose for new virtual switch and then it will use the IP range from the host computer.
In this case it will be

Browse and select that empty folder
Change the size to 40 GB

Browse to that ISO

Click on Virtual Switch Manager
When you see default switch and the new switch with the name of the manufacturer from your networkcard it should be allright.


If the server  is installed in Hyper V, see if you you have internet and your IP address is in the same range as your computer.
Open CMD in the VM and type: ipconfig
In this case we have internet and the right IP range and subnetmask for that new virtual ethernet adapter.

Go to the installation
That would be for a real server. No VM
But you can follow that manual.
If you want to add clients on a laptop or regular computer then you can also follow the installation of Windows 10 with multiple remote desktop sessions.
Then you don´t need an outgoing LAN.
Read for Windows 10: Server.

If you got no internet read a few solutions first.

If it is wrong, remove the new virtual switch.
Click on new virtual switch.
External network
Yo have to see the name from the networkcard.
Restart the VM.

If it is not working then it can be quite troublesome.
Type Hyper V default switch in Google and you will see that many people struggle with that.

Is your Hyper-V not connecting to the Internet ? Try this.

If you think: I just want to start a new VM then you can delete that not working VM.
Go to users and search for VMboxes to delete.
Also delete that empty folder VM-1 and create a new folder with another name VM-2
With the creation of that VM, there still appears to be something of a link to that first folder assigned to that first VM.

If it works properly we will continue with that VM.

Type sharing in the searchbox
Manage advanced sharing settings
Network discovery has to be on.

Click on all networks. There should be the same
Network discovery should be on.Also the other options. Then you can check if network discovery has stayed on. If not, change that.If it keeps jumping back to off  Type in the search box: services.msc There must be 3 services on automatic.Probably they are on manual.1- Function Discovery resource
2- SSDP discovery
3- UpNp device hostYou have to set it to automatic and start it up.Then check whether network discovery is on or not.