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

Erik Read 86 Reputation points
2022-06-08T16:57:25.457+00:00

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.

System Center Virtual Machine Manager
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,545 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,193 questions
Accepted answer
  1. Sarah Tennyson 131 Reputation points
    2022-06-10T20:42:35.707+00:00

    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.

    11 people found this answer helpful.

8 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Oleksander Paniuta 1 Reputation point
    2022-10-06T09:27:53.45+00:00

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

  2. Manuel 1 Reputation point
    2022-10-06T13:38:55.89+00:00

    Solution given by @Sarah Tennyson worked for me as well. Thanks a lot !

    1. on my VM settings, network adapter : changed to "not connected" in order to be able to remove the broken external switch in HyperV settings
    2. Then in HyperV virtual swith settings, removed the "external switch"
    3. Created a new external swtich (external switch #2 for example)
    4. back to my VM settings, network adapter : changed back to the connexion to external switch #2
    5. Et voilà

    It's a bit annoying that an issue reported back in June 2022 is still there 4 months later while MS is releasing Win11 22H2 globally.

    0 comments
  3. Dave Hammond 1 Reputation point
    2022-12-30T01:25:52.17+00:00

    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.

    0 comments
  4. Trinidad Cruz 0 Reputation points
    2023-12-02T13:02:45.4066667+00:00

    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.

    0 comments