Host and NAT virtual network adapters are registered on "unknown network" with public network profil

[DemonDante]

I am using the latest version of vmware workstation pro on a windows 11 pro operating system.  I have noticed that the NAT and Host virtual network adapters that are installed on the host operating system are registering to an "unidentified network" with public network profiles:

But it doesn't stop there.  Looking at all available network adapters on my machine, I see twice as many network adapters than the number that should be there:

I have attempted re-setting and re-installing the virtual network adapters numerous times using the reset settings function in the Virtual Network Editor, but that has not resolved the problem.  What exactly is going on here?

[DemonDante]

You know, even if this is a known issue, an acknowledgement that vmware is aware of the bug and is actively working on fixing it would be very much appreciated.  

[scott28tt]

VMTN is a user community forum, not an official method of support or communication channel.

[DemonDante]

REally!?  That is odd.  Well, maybe everyone else who posts on this forum looking for support should be made aware of this fact too.  Furthermore, I am not looking for support.  There is obviously an issue with your product and I, free of charge, am making you, the developers, aware of said problem to give you the opportunity to fix said problem.  I would think that, with as much as you charge for workstation, that you would want the product to be as easy to use and bug free as possible for the end users who pay so much for it.  What a massive disappointment this purchase was.  If that is going to be your ungrateful attitude, then I will be requesting a refund.  Great customer service skills there, buddy.  Truly a star vmware employee, losing the company customers.

[DemonDante]

Maybe it would help if I explain exactly why this is a problem, as I have seen other posts questioning if this is even an issue.  Allow me to explain why it very much is, as the presence of these public network adapters prevents the configuration of windows remote management on the host machine.  while the virtual network adapters do what they are supposed to as far as the virtual guests are concerned, it presents a challenge when trying to configure windows remote management on the host, running "winrm quickconfig" to attempt to quickly setup and configure windows remote management results in the below errors:

So this isn't some irrelevant issue without consequence.  This is resulting in legitimate issues with the host machine.  Now, if it is not a vmware problem, but a windows problem, then say that, then I know I need to go bother someone else.  But this seems very much like a vmware problem, and, as such, deserves to be resolved.  And I will not stop posting about it until it does get resolved.  You have my word on that.

[CarltonR]

You may have already reviewed these articles from Microsoft community forums . . .

excerpt from one such entry, giving a number of solutions, but perhaps the second one in the list might be worth further attention.

This error is expected since you have Public network.  There are some workarounds:

1. Set all network to "private";

2. Skip checking: Enable-PSRemoting -SkipNetworkProfileCheck;

3. Change the network location.

[https://social.technet.microsoft.com/Forums/en-US/a41ae1e4-17e1-4466-bf54-3a72d0d61db9/windows-10-wi...

Other reference (with mention to other virtualization software):

Bug in Windows networking - Private connection is reported to WinRM as - Microsoft Community

[klepp0906]

did you ever sort this out?  same issue.  its causing problems for me as at startup of the host it first connects to the unidentifed network which prompts the creation of a bunch of public windows firewall rules.  beyond that it also breaks sending wake on lan packets until they are disabled irrespective of interface metric setting.

forcing them to private in powershell simply reverts on restart. 

worked fine on 10.  Now it’s wreaking all sorts of havoc.  Have already restored a system image several times trying to get the functionality I need while leaving them alone.  So far the only solution is disconnecting them from the host in VMware network config which also removes them from windows adapters interface.