No network access for one VM (6 running fine). Hyper-V

Mikael Hallen 6

I have a Hyper-v environment that have been fully functional for years.

As of yesterday my file server no longer can access our network. No network access.
I can reach it through our hyperv servers and have tried restarted it and resetting ever since.
I have 6 more VMs that connects without problem.

The VM is server 2019. Hyper-V servers are 2012.

I have one more 2019 server and the only difference in network setup is the driver of the NIC.
Microsoft Hyper-V Network Adapter - 10.0.17763.2145 (driver date 2006-06-21) not working
Microsoft Hyper-V Network Adapter - 10.0.17763.1577 (driver date 2006-06-21) which is working.

I find it hard to believe that this driver is causing the problem but it is the only difference I have noticed.

Tried both static and dynamic IP for the server, no luck.

I have deleted and added the network adapter several times.

I have deleted one of the virtual switch and added a new one. tried the new switch with other VM and it works.

but my file server still has no network access.

Any thoughts?

Brad Smith 1 Reputation point

2021-09-26T16:46:24.997+00:00

I've run into the exact problem. Installed from the Aug_2021 ISO, which comes with 10.0.17763.1879 of the Microsoft Hyper-V Network Adapter. Networking worked fine at that point. Eventually I decided to run Windows Update, which didn't offer much. But on rebook, the driver had been updated to 10.0.17763.2145, and I lost all network access. Nothing I did could get it working again. Installing all the updates I could didn't help, so I suspect one of the uninstallable updated did the deed.

I ended up reinstalling from scratch, and resisting the temptation to run Windows Update for now.

This is definitely something introduced in a recent update. Showing as available now (and I'm not taking them):
KB5005568 and KB4535680, plus one Defender AV update and an update to the Malicious Software Removal. I suspect the latter two aren't related, it's one of those other updates. I'm suspecting the first one: 2021-09 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5005568).
Jay B 6 Reputation points

2021-09-30T18:45:29.547+00:00

I'm also seeing the same behavior after installing KB5005568 on Server 2019 VMs running on a Server 2012 Hyper-V host. For me it's been very consistent across three Server 2019 VMs so far- install KB5005568 and network access stops; remove KB5005568 and it comes back. It's a Dell R910 with Broadcom/QLogic NICs, and the symptoms are the same as what's described in https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/vm-lose-network-connectivity-broadcom, although that article obviously pre-dates the Sept.2021 CU. I updated the physical NIC drivers to the QLogic 17.2 release and disabled virtual machine queuing on all of them anyway, but that hasn't changed the behavior. I hadn't checked the virtual NIC driver versions before reading this post but on a post-KB5005568 VM (non-functional network) it's 10.0.17763.2145, and on one with KB5005568 rolled back it's 10.0.17763.1 (and the network is accessible).

So the Sept. 2021 CU (KB5005568) on the VMs definitely seems to be the problem, or what triggers it anyway.
Brad Smith 1 Reputation point

2021-10-01T18:15:05.21+00:00

Since this is mostly a test VM, I decided to upgrade it to Windows Server 2022. Which upgraded the driver. Which broke networking. So it's much more than just 2019 September CU, but also the latest version of Windows 2022.

One thing I noticed with this driver update is I have a whack of "WAN Miniport" drivers that weren't there before.
Jay B 6 Reputation points

2021-10-01T22:12:46.987+00:00

I haven't installed 2022 anywhere yet but I can at least say that pre-2019 versions don't seem to have the same issue. Two Server 2016 VMs and one Server 2012 R2 on the same host still have functional networking after their respective September 2021 CUs.
JLugo-ITCS 6 Reputation points

2021-10-05T13:15:27.84+00:00

Same problem. We tried removing the KBs without luck. I guess we are waiting for a fix. I'm currently using the legacy adapter while this is resolved.
David Ortiz 1 Reputation point

2021-11-22T22:19:18.617+00:00

We encountered the same issue. Purchased new copy of Server 2019 Standard w/CALs. Setup new VM with previously used Virtual NIC Settings.
All was well until installing Windows Updates. After Windows Updates the server could not connect to any networks.
We tried different Virtual NICs and TCP reset commands. But nothing worked, until removing the windows updates. We removed the following, then we are able to connect to a network:
KB4514366, KB4512577, KB5007206.

Looks like we will also be waiting for Microsoft to correct this issue, before anymore Windows Updates.

12 answers

AussieCraig 1 Reputation point

2021-10-21T08:59:03.787+00:00

We encountered the same issue with last month's updates - both our WS2019 VMs running on 2012 Hyper-V Cluster lost networking after installing KB5005568. At the time we hadn't installed the Sep patches on our hosts, so I decided to disabled Windows Updates service on the VMs and try again in October, after patching hosts and hoping that MS will have recognised the issue and fixed it with October updates.
Alas, as others have noted above, the October KB5006672 causes the same problem. I'm about to uninstall it and disable Windows Updates again.
Moving the Hyper-V cluster upgrade up the to do list...
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
PaulEPCS 1 Reputation point

2022-05-19T08:16:32.993+00:00

Slightly old thread, but may help. We had a similar issue with Windows Server 2012 R2 Hyper-V Host (in a failover cluster). Installed a Server 2022 VM, could net get Network card to work. Re-installed VM with 2019 and worked a treat. After running windows updates, NIC had exclaimation mark and wouldnt work. Adding the Legacy Network adapter did not resolve it, and using just the legacy adapter was not an option (100MB compared to what should be 10Gbps).

No KB4514366, KB4512577, KB5007206, or KB5005568 listed in updates.

Culprit for us was to remove KB5013941 (I did remove KB5013641 prior to uninstalling that, but doubt that had an effect as NIC still failed after removing it).
All working a treat!

...Future Failover Cluster Upgrades to Server 2022 in the pinepline now.... :/
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

No network access for one VM (6 running fine). Hyper-V

12 answers

Your answer