VMware Communities
DemonDante
Contributor
Contributor

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

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.  This issue appears to be unique to the windows 11 operating system:

image.png

image.png

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. The virtual network adapters appear to still function as intended as far as the guests configured to use those network adapters are concerned, but this issue (which only occurs in windows 11) creates issues on the host, specifically due to the presence of the two public network adapters. A good example is when trying to configure windows remote management on the host. It is not possible to configure windows remote management on a machine with public network adapters present. This appears to be a bug with vmware workstation. If it is not, advice on how to fix would be awesome. If it is not, then it would be very much appreciated if you would fix your product, an opportunity that this is post is meant to provide VMware.  I will continue to make these posts for as long as the issue remains unresolved, and I am about to the point where a continuous automated process for submitting the posts is warranted.  Please do not provoke me to do so.  Nobody wins then.

 

Labels (2)
0 Kudos
4 Replies
klepp0906
Contributor
Contributor

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.
0 Kudos
k-bull
Contributor
Contributor

I too am having this problem. But for me, it started with the 22H2 Windows 11 update. What I have realized is that the virtual adapter is not being generated in the registry. Can someone please chime in on this.

0 Kudos
k-bull
Contributor
Contributor

I've also realized that the virtual ethernet adapters does not have a profile. I've done everything that I can do when it comes to troubleshooting. How can I make Windows generate a profile for the virtual adapters? I believe that's the problem. Can someone please help.

0 Kudos
k-bull
Contributor
Contributor

Well, Just an update, vmware.

I ended up reinstalling Windows 11 21H2.  I did everything i could dig up from the internet to try and fix this whole virtual ethernet adapter profile problem that vmware has with 22H2. 

I do hope vmware is working together with Microsoft to try and solve this problem. (That's my wishful thinking and I'm sticking with it)

0 Kudos