Windows 10: Are HNS Containers and VM switches a standard installation package activated in Windows 10

As i am a Learner when it comes to the "Virtual Intergration World" i am very aware of the security issue that are also presented with new things. As i have no visibility or documentation provided i can only guess how and what these are used for. I have found my current windows 10 pro system has 24 access rules available through the firewall to what i can't confirm or access. Is this a standard practice with Windows OS given the extent of so many other services host applications running. With so much cyber security issues at the moment one can never be to careful. To air on the side of caution

:)

 

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

 

Problem activating Windows 11 after switching VMs

Hi there,

I purchased Windows 11 Home a couple of months ago and installed it on a VirtualBox VM. But VirtualBox was crashing quite a bit so I deactivated Windows 11 using the following commands:

• slmgr /upk
  
• slmgr /cpky
  

(as suggested on Redirecting ) and then installed it on a VMWare VM. Problem is, I can't activate Windows on the new VM even though it was deactivated on the old VM. I tried the recommended Troubleshooting Wizard solutions to no available and I couldn't find a Microsoft email address or support number, so I am posting here. Can anyone suggest how to contact Microsoft about this activation issue?

Thanks,

Darryl

PS: I have already deleted the old VM so I can't log back onto it.

 

When is Microsoft going to issue a fix for HNS container Networking Issue that been around now for months.

@DmitryRomanovRU that's a great script if you do it 'before' you reboot (& trust that the same error will re-create the rules you actually need upon said reboot )...

However, to those who are inclined to enable such a process, I would recommend two changes:

1. you rename one instance of each rule to:
   
   • HNS Container Networking - Manual - DNS (UDP-In)
     
   • HNS Container Networking - Manual - ICS DNS (TCP-In)
     
2. in step #3 of @DmitryRomanovRU's instructions, you put his script in the 'Startup' section instead (note : this is untested, and there may be a race condition possibility, so you may still have 'effectively' duplicate rules)
   

... if I'm going to 'override' an automated process, then I want control over it

(If I get bored, I may provided an updated script for both startup (with a delay) & shutdown, that will essentially only retain the most recent rule & delete the others; but I'm often not that bored.)