Windows 10: When is Microsoft going to issue a fix for HNS container Networking Issue that been around...

This has been reported repeatly for months now nothing has been addressed but Microsoft has real issue with HNS Container Networking in the Windows firewall policy every time you restart the computer HNS Container Networking multiples and creates a new enter in both TCP and DNS UDP-in and ICS DNS TCP- in i found it on 6 computers i ran multiple virus scans, trojans, spyware from all different venders and other checks no computer virus, no trojan worms, no spyware, no indication of hacking or someone accessing my computer did a port check port scan looking for anything that out of the ordinary

:)

 

What is "HNS Container Networking" and why is it....

Do you have Pro and have you just turned on Hyper-V?

HNS is part of this and requires those rules to be added....

https://docs.microsoft.com/en-us/vir...etwork-service

 

What is "HNS Container Networking" and why is it....

I've never seen this before. I try to do a search and I find tons of techinbabel on how it works but nothing telling me "why".

Windows is trying to add an allow rule to my firewall for "HNS Container Networking - DNS (UDP-In)".

Can anyone give me a simple reason "why" my os is trying to use this?

 

HNS is unresponding on Windows Server 2019

Hi,

We are using HNS to support container Networking. The vSwitch Extension is Open vSwitch Extension. When I invoke HNS.psm1 to attach an existing HNS Endpoint to a container, the request doesn't return. The process never stops, even if I input ctrl+Z or ctrl+C,
no response returns. The issue also happens in deleting HNS Endpoint or deleting HNS Network.

It is found in Windows Server 2019, and all possible KBs are updated on March 16th.

Please help give some guidance on such issue.

Thanks,

Wenying