Hyper-V Default switch IP address range change. Ver 1809 Build 17763.1

HotCakeX I'm not intending to argue with you and what I'm about to say is not directly related to the original topic of this thread, but you might be surprised at what's being done in "real-life" networking scenarios these days. The reason I switched from VMware to Hyper-V on my dev machine is because I need to work with Window Containers and Docker Desktop, which requires Hyper-V. Currently Hyper-V and VMware cannot coexist, but that is about to change. In the container world, VM's are just hosts for containers and usually many containers. For example IIS would not run directly on a server VM, but in a container. In larger scale systems like I work with, everything is redundant and disposable. For example, the web application I work on has many instances in production all sitting behind a reverse proxy (which itself is in a container). If one instance dies for some reason, no big deal, another is spun up to replace it. The containers are all behind a Hyper-V internal switch with NAT. Anyway, it you want to learn more about containers in the Windows world, here's a good place to start: About Windows containers