DemonDante's Posts

A bug that had previously been corrected has once again been introduced into workstation, but it is now much worse.  The bug is related to the fact that the number of virtual network adapters that workstation installs on the host device is greater than the number of virtual nics that appear in workstation's virtual network editor.  However, the bug has now gotten even worse than it was previously because workstation will continuously install additional virtual network adapters to the host whenever the user attempts to "restore defaults" in the virtual network editor.  The below video demonstrates the bug in action: Gotta say, Vmware.  You guys are slipping.  Between the bug reports that you choose to ignore and the re-introduction of old bugs into your software, the quality of the product is worse than some of the free/open-source alternatives available.  Makes me regret purchasing your crap software.  But purchase it I did, unfortunately, so you best believe that I will continue making these bug posts until you [bleep unprofessional language] and fix the issues with your increasingly low-quality product  Moderator edit by wila, please don't discredit your report like that.

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: 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.  

I noticed that an update for vmware workstation was recently released, so I had gotten my hopes that, maybe, just maybe the bug (until proven otherwise) that I had reported had been fixed. Beyond disappointed to find that it has not been resolved. So, I guess I need to create another making VMware aware of the issue.  Which I am more than willing and able to do as many times as needed until this is addressed. 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:   Some progress, however miniscule and insignificant to the problem, seems to have occurred with the latest version of vmware workstation, as the number of listed networks in virtual network editor now correctly matches the number of virtual network adapters configured on the host, unlike before where two adapters were configured on the host for every network in the virtual network editor. 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 of 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 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?

Hello VMware community.  Like the title states, I think I may have found a small, non-critical bug in vmware workstation 15.  The official version is 15.0.0 build-10134415, which is the latest available.  In regards to what the bug is, I created a video which shows the problem, which you can find at the below link.  In short, the bug occurs when attempting to configure the amount of memory available to the virtual machine during the initial setup.  When attempting to set the amount of memory by dragging the slider control, the amount of memory  configured for the vm remains unchanged. https://showmore.com/u/63pj4cu