Forum Discussion
Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1
This has been the case for quite some time - and is not isolated to 17763, and stretches to 10240.
(Though earlier issues weren't this exact problem)
The "Hyper-V Virtual Ethernet Adapter" that appears in device manager that appears as "vEthernet (Default Switch)" in Network and Sharing Centre is being deleted and reinstalled each time you shutdown and boot.
You can also check the registry to see the abundant keys that are created and never removed and just linger in HKLM\System\CurrentControl\Services\
If you're suffering from this issue - you should see a ton of {GUID} just under .NETFramework, and a whole bunch more in the VM services section... vmsmp, vmsp, vmsfsf, etc.
VMSMP\parameters\SwitchList contains the current 'Default Switch'
Those GUID under the .NETFramework Key, when expanded will have Tcpip keys for previous switches...
Do you have any idea how to get this ip fixed ? Maybe we can run powershell script to change it after reboot ?
---------------------
Just tried to update IP on reboot with powershell script, it's ok to keep same IP , but the network doesn't
work for VMs.This is not way.
I haven't actually played around with all of my VM's yet. However - 1903 has fixed one of the Hyper-V Default Switch problems:
The Default Switch would always be set as a public network - this can be disruptive to other connected networks - as I don't trust that the MS Engineers did a good job with how Domain/Private/Public interact.
With 1903 - the Default Switch is not assigned a Network Category. Which is how it should have been to begin with.
It is always going to be a private network - as VM's can only use it to interact with other VM's on the Host and to the Host itself.. an Internal Network. Like I said... I don't trust the engineers to have done the network categories correctly, until now. Took 4 years.
Anyhow, I'm in the middle of updating the VM's on my laptop to 1903 and see what I can do in the Guest Machine.Not at the moment - because there may be changes upcoming to Hyper-V for 1903 - so anything we do now will be made redundant for the next upgrade.... which is very similar to what has been happening since 1511.
The Virtual Machine connected to the Default Switch will also be connecting to 'New' networks for the first time, each time both the Host and Virtual machine boots... changing to a static IP only solves the problem temporarily - as changes to the default switch IP will result in the VM losing connectivity.
The work around I had where I created a new 'custom default switch' and keeping the original default switch along side it worked best, as I just told all the Virtual Machines to ignore the original default switch and just use the custom switch that I configured.The only thing that breaks this is major build upgrades - example: 1511 - 1607 - 1703 - 1803
As well as anything relating to having to reset your network configuration using the Settings UI aka ImmersiveShell.