KB5014692 (Jun 22 update) and network failure

Ross Hemingway 91 Reputation points

Server 2019 std desktop, using hyper v.

It seems (for me anyway) that the KB5014692 monthly update causes a network stack failure. After an install / reboot, it runs and serves OK for 5 mins, and then the network response quits. Uninstalled and reinstalled the update twice to confirm this.

From a console via iDrac, Watching wireshark, the server (host OS) receives the initial SYN, issues an ACK, the client sends back the next ACK and the next packet.... (sofar all normal)... but the server goes deaf at this point and issues nothing more. Then sometime later both ends re-transmit, but nobody is listening at the server end.

Affects all traffic, all ports but only after 5 mins of normal running. Feels like some buffer or counter not correctly coded.

Anyone else?

Update June 28th, 2022.

Microsoft now acknowledges this (RRAS / NAT) issue in known issues :


... and repaired it with "out of band" fix in KB5014669 :


Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
2,663 questions
Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
366 questions
{count} votes

10 answers

Sort by: Most helpful
  1. Ross Hemingway 91 Reputation points

    Well if we users knew where to make official reports to MS about a defective monthly update... there would be two valid reports. So your answer is not acceptable.

    We do we report problems that actually get anywhere?

    2 people found this answer helpful.
    0 comments No comments

  2. Fulco Stiva 11 Reputation points

    Similar problems after june update. Server 2019 fully patched.
    HyperV exchange 2019 also fails. RDP fails: so I need to work on the server hardware it self. Clients can’t logon.

    2 people found this answer helpful.
    0 comments No comments

  3. Ross Hemingway 91 Reputation points

    Good... I mean we are building some evidence here. Obviously its limited to a subset of servers... I wonder if its related to the installed roles? On mine I have the following installed:

    DNS, File & Storage, Hyper-V, Remote access, IIS.

    After 5 mins, all those things quit working, including RDP. But I think I was still able to use RRAS via L2TP/IPsec, but unable to tunnel anything TCP.

    How do we report this properly to MS, where they actually listen?


    There is a known issue that affects Win10 1809 using the same update, with similar problems as ours here. "After installing KB5014692, Windows devices might be unable use the Wi-Fi hotspot feature. When attempting to use the hotspot feature, the host device might lose the connection to the internet after a client device connects."


    1 person found this answer helpful.

  4. Marcel van Groenigen 6 Reputation points

    Same issue here on 2 servers with NAT enabled
    3th server without NAT is unaffected

    Symptoms. The internal (not natted) network behaves weird.
    Pinging works
    DNS resolve works
    http, rdp or ssh times out..

    no issues on the Natted internet connection.

    Stop the RRAS service and everyting works fine again
    Start the RRAS service and everyting works fine until the second VPN connection comes in... and all goes south again.

    Kill all VPN connections / keep them down.. and after a while it works again..

    1 person found this answer helpful.

  5. Ross Hemingway 91 Reputation points

    A new "out of band" update is available now. For server 2019 its KB5014669

    It looks to have repaired the issue. While our fault with RRAS NAT is not listed in the repaired issues, the new KB says it fixed the Win10 ICS error that was also present. Given that ICS is all about NAT, I'm sure its the same cause and solution.

    I see they replaced ipnat.sys with a newer version than last weeks one. Now using v10.0.17763.3113 of this driver.



    1 person found this answer helpful.