Windows 11 22H2 Broke custom virtual switches in Hyper-V

Question

I upgraded my Windows 11 physical machine to 22H2 this morning. This machine hosts 4 hyper-v virtual machines using 2 different virtual switches. 1 switch is an internal NAT and the other a bridged external.
Up until the upgrade these switches performed flawlessly.
After the upgrade, no internet connectivity from either switch.

I did add a third NIC to one of the VMs and pointed it to the default switch and it works but that is not what I need, nor would I consider that a valid alternative.

Any information I can provide I will be happy to.

Answer 1

I had this same problem, with a bit of flailing around I was able to correct it... what I did:

Changed all my VMs to use another v-switch.
Deleted the v-switch that wasn't working.
Went into the properties of the external network adapter and unchecked "Hyper-V Extensible Virtual Switch"
Re-created the v-switch using the external network adapter
Changed all the VMs to point to the re-created v-switch.

Solved my problem.... hope it helps you.

Answer 2

Sometimes, also deleting the physical network card in device manager helps. Then let it search for new hardware and install the driver with default settings.
Good luck.

Answer 3

None of the solutions work. After a few minutes or hours, or reboot computer the story repeats itself =(

Answer 4

Mine is working now. As mentioned above I had to roll back the first time and none of the solutions worked for me even with a second attempt. So I reported my reason for uninstalling it, and Windows hid the update for about a month. But now that Windows offered the update again, I decided to try again. The only thing different (besides possibly newer patches in the current update) was that before I installed it, I disabled all of the filters from the virtual switch. The update added the new Azure one, but before I even tried to open a VM, I removed it as well. Everything has been working so far.

Answer 5

This is an annoying ongoing problem for which the only currently available solution is to reconfigure the virtual switchs after updating. I suggest that some PS guru come up with a commandlet that can be used to automate that process. Save that commandlet to a text file so that it can be copied and pasted into PS everytime this network wiping occurs due to updates. It's happened to me the last four regular updates and I can't get any response from MS other than to reconfigure the switches after updates which is a ridiculously tedious way to solve a problem. I don't need such GUI infantilism for an answer. Give me some PS.